I store my pictures on a NAS jail. That directory is mounted read-only on another jail with NC and Memories. I like the guarantee that my gallery app cannot alter my files.
Also, many gallery apps don't allow browsing a directory tree. You have one level of "albums" and that's it. Memories support it. I have pictures 5-6 directories deep, following a system that makes sense to me.
I use wireguard as my main VPN to connect to my homelab from my phone and my laptops.
I also have an OpenVPN as a backup option, running behind sslh.
My same port on my router (443) serves both a webserver hosting photos, and that OpenVPN instance. This allows me to VPN into my home in most firewalled office networks.
My requirements were:
- ability to sync the TODO lists between devices (web and android).
- ability to have sub-items, so that I can organise my complex lists into magnificent trees of tasks. I sometimes have 5 levels of details on some travel checklists.
- ability to handle periodic tasks, and ability to create a task and hide it until a specific date (topics for my future self)
- ability to be self-hosted.
I'm now using Vikunja, and Tasks.org for the Android side. That setup has worked for me wonderfully for a couple years now. Vikunja has a ton of features I don't use, and that's fine. They don't get in the way.
I document technical things on my blog and hardly anyone reads it.
But later on when I need that thing again, I just go there and I have the perfect documentation available for the topic (it's perfect since I wrote it hahaha).
The way I've seen OKRs work so far was always the same:
Top management defines a strategy for the company.
Each department (commercial, marketing, product, etc.) create department OKRs from the company OKRs.
The year/term starts.
Each department comes to the implementation teams (product, IT, BI, support, etc.) with a HUGE list of poorly defined objectives or tasks.
The implementation teams only have limited capacity and can only deliver maybe 15-20% of what everyone wants. No one actually thought of checking if the objectives have any reasonable possibility of being delivered at all during the term.
Optional drama to decide what's going to be actually worked on might happen.
When the term ends, and if communication isn't a disaster between the departments, some MVPs are delivered.
A new term starts, and either the previous objectives are continued, or they're simply forgotten in favor of new ones.
I host 25-30 people on my couch each year, and I've had wonderful times with so many different people from different backgrounds.
Some of my surfers had some weird stories about weird hosts, but I've never had anyone tell me anything about drugs, rape, or anything violent.
In my opinion, latency is a super important concept that got forgotten once we moved every application to web interfaces.
I remember the 90s and the 20s, when everything happened locally on the local hardware. It was quite easy to type fast, move the focus around in the various forms using tab and shift-tab, move from tabs and windows with ctrl/alt-tab; and there was keyboard shortcuts for most things.
I remember being able to execute complex operations between multiple applications using only my keyboard and without having to use any brain power between each step.
Now most things are moved to cloud applications and we interact with them with web browsers. Keyboard shortcuts are (mostly) gone, and each click or operation triggers a request on the other side of the world with a high HTTP latency, and that prevents the brain from chaining them for free.
I remember being able to do almost everything using my keyboard. Now good luck interacting with a web console without switching back and forth from keyboard to mouse for 50% of the steps.
I guess that's also why many developers (including myself) still love the CLI environments.
> The main positive that I see is that typing no longer requires thought.
This is why I've been using keyboards with nothing written on the keys since 2004.
At the time, I was in high school and had no money to buy a professional keyboard, so I spray painted my cheap keyboard with black paint (fun fact: I'm still using that very keyboard to type this).
I've never looked at my keyboards ever since. I can type all letters and all symbols without thinking about it. As an IT person, I couldn't imagine how much brain energy I would waste if I were to look down and search for anything.
I've accepted this a decade ago.
I put my ego on the side, and now I don't care if my git history doesn't look like "beautiful" when looking at the commit graph.
I've been working on dozens of projects since, and probably did thousands of commits. Some of the teams of those projects included dozens of developers working concurrently on the same codebases. We always merged the upstream branches into our development branches and never did any rebases.
I have NEVER ended up in a situation where I thought rebases would have been better.
The git tools and IDE integrations of our current age allow me to find any information I need from the history without pain.
I have a private PKI I use to connect to my self-hosted software: email server, calendar provider, notes server, photo sync tool, etc.
I NEED to be able to add my root cert to the list of certified authorities.
I don't need to change anything to the system provided list. I just need to add mine.
It's my device, I'd like to be able to change anything if I want to.
I don't need to backup my boot sectors or root partitions since all my systems are provisioned. I can always re-create them with scripts, should any of them fail.
I'm only replicating the data filesystems.
From what I see, sanoid looks quite similar to zrepl. Both tools are probably able to achieve similar results.
I do feel that zrepl has more features so far, though. But hey, if your setup is working and your data is secure, that's the most important.
I'm using zrepl to sync ZFS filesystems incrementally between servers.
I like the ability to incrementally send only the changes of an encrypted filesystem to a target server that never had the encryption key at anytime.
I'm using this to share backup space with my friends. We both push/pull our encrypted snapshot diffs every hour. I don't have my friends' keys so I can't read their data, and they can't read mine. In case of emergency, I can go to their place with my key, and recover my data from their systems.
I 100% agree that the move to etcupdate should have been documented better. I also ended up in situations when I had to manually fix systems after upgrading.
Applications each have their own FreeBSD jails, so they're isolated.
ZFS incremental replication on top of regular app backups provide a quick recovery process should the hardware of that machine fail.
Moving those apps to the cloud would cost orders of magnitude more, for benefits I don't need.