BearOfaTime

The contacts were surprisingly robust. Mine just died, sadly.

New ones are crappy knockoffs, but they're cheap enough.

LaCie IAmAKey. No longer made. Current ones are made from aluminum and bend easily. Originals were stainless and rigid.

My 2006 one just died, and I'm so frustrated with the new ones. Fortunately they're pretty cheap, so who cares.

Here here!

Best mouse I've ever had. Lasted 10+ years. Just can't justify $100 for a new one

It still exists! (Or did about a year ago).

When I got my first Android (2009 ish), I searched high and low for a way to run Hamachi on it. There have been solutions, but always clumsy and difficult to implement.

I miss Hamachi, it was so simple to use.

Tailscale is wireguard (it uses the wireguard protocols, even says so on the box), just with a centralized resolver to make things easier to setup and manage.

I'm not sure what you're saying with the rest of your comment, as Tailscale is a mesh network, not a VPN as most people think of it.

It encrypts your traffic, but only into the network of which your device is a member. You can't even see any devices, or networking, outside the Tailscale network, unless a device is configured as a Subnet router. Then you can see devices in the network which the Subnet Router links together.

For example, you have 3 machines, a laptop on mobile data, and 2 desktops on your home LAN. One desktop and the laptop have Tailscale, they can communicate over Tailscale to each other, but the laptop cannot connect to the second desktop because it's on a different network, since there's no routing between Tailscale and your home LAN.

You then configure Subnet Routing on the desktop that has Tailscale, now your laptop can connect o any device on the home LAN, so long as the desktop is running and Tailscale is up.

Think of mesh networks as Virtual LANs in software, configurable on each device (mostly, sort of). Twenty years ago Hamachi was the go-to for this, it was brilliant, and much easier to use than today's mesh networks, just far less capable/manageable/configurable.

I'd consider 5% to be trivial, for what it does.

My battery consumption really depends on how much traffic I send over it.

I was just thinking about this a little earlier.

People simply can't be bothered to learn how systems work (any kind, technical, financial, political), then bitch when it doesn't work the way they want or think it should.

I'm as guilty as anyone (especially finance). At least I try to not bitch about it too much, and work at keeping away from more complex stuff that I just don't understand well enough.

Thanks for the summary, it adds great clarity to seeing how it could happen

Are you going to pay for retraining 30,000 employees?

Or to make all your software work on Linux?

Autocad?

It definitely gets better once it's all caught up.

But it's still much harder on battery than ST when folders have changes.

It's kind of not Foldersync's fault, it's really because of the protocols - it's all connection-based, and FS has to compare each file at sync time.

Syncthing keeps an index so it knows what files have changed. Very different tools with different use-cases and approaches.

I used FS for years until I found ST, and had to do a lot more tweaking to get sync to work the way I wanted with FS. FS doesn't have sync conditions like ST, so I had to use Macrodroid to trigger it when on WiFi, for example.

FS can be a solution, it's just a lot more work for anything beyond basics.

It's stupid easy to setup, even has a built-in photo backup job.

I use Syncthing-Fork because it moves all the sync conditions into each job.

So my photos sync regardless of charging state or network (I'm willing to pay for the data to ensure photos are instantly synced). While other things only sync while on WiFi and charging (e.g. Neobackup).

Only one I can think of is Resilio, but it's hard on RAM and battery for large folders.