Right, the flexibility angle makes sense if using a typical root fs like Ext4 with or without LVM. That’s a reason I’ve always kept the OS separate. But with ZFS there’s unlimited flexibility. Separate datasets or volumes within the same storage pool are trivial. I could do root on ZFS on separate SSDs and get those benefits but it’s more complicated that slapping it all in a single pool. Then maybe use the SSDs for cache. :D

The Israelis have no idea what’s coming for them. They’ve gotten themselves into this right wing stasis and they seem to have become oblivious to the domestic dangers posed by the tools and tactics they’ve developed for “external use.” This shit is coming home and I’m guessing any dissent over expansionist policy will be the first to get repressed.

That’s odd because the clients are just web apps I think. That should work without crashing on a stable OS. I use them on Android mobile and Android TV with extensive subtitle usage and haven’t seen instability.

A funny thing I noticed is that the client distributed in F-Droid is extremely old even though it says it’s updated recently.

I switched from a heavily used Plex server with about 10 users to Jellyfin with the samw usage patterns abour half a year ago. So far it’s been pretty smooth sailing. A better world is possible!

Yes baby.

Thank you for your service @Track_Shovel

Hm, I thought Chromecast needs HTTPS and internet-visible endpoint.

Oh? I haven’t upgraded yet. 😄

That’s how it works with Tailscale as well. Tailscale creates Wireguard tunnels underneath between the different devices. There’s also an open-source self-hostable Tailscale control plane.

I do use both a reverse proxy and Tailscale. All services are proxied. All services except for Jellyfin are accessed only via Tailscale. Jellyfin is publicly available. I’ve obscured it a bit by setting up long, randomly generated DNS name. The proxy would only forward traffic to Jellyfin if the request comes from that exact DNS name. Bots would have to know this name for the proxy to entertain their attempts at all. Then every user has long, randomly-generated password. I prefer to only use it behind Tailscale but some of my family needs direct access. Also Chromecast.

I do. No issues.

Switched to Jellyfin after more than a decade with Plex. Prettey… prettey… pretty good.

That’s the issue. It’s why I’ve learned that when I can afford it and I reasonably believe this firm or project should exist, and it has a decent chance not to fall flat, I end up buying in. It’s literally upfront investment in the thing. I’m still salty for not backing the Ubuntu Phone back in 2012 or so. I looked at it as another phone compared to what’s available on the market and how the price stacks up for the features. That’s very much the wrong way to do it. A part of the value it provides is the existence of the project and the labour dedicated to it. In the case of the new Pebble, I’m backing it despite Eric, and because it’s fully open source and that’s something I want to exist. A fully open alternative in the sea of proprietary wearable crap.

Same guy. This time the whole thing is open source though, even the hardware. So that’s insurance for what it’s worth.

This is not the final design, it might gain a connector in the final. It might not. But even if it doesn’t, splicing the wires shouldn’t be too difficult for most who’d dare open their watch. I’m pretty confident I can do it.

True, but it shouldn’t be a huge deal to clean them up once every few years.

Hitler

If you feel that Wiki has savings and therefore doesn’t need your money today, that’s fine.

But other than that WTF is this nonsense? None of it follows. Says Wiki keeps increasing spending while not noting the obvious - that its savings are growing too. Worse, without noting that a big chunk of the expenses are going towards savings. From the report below, out of the 111M spent, 51M went to savings. His expenditure graph includes savings yet he thinks that’s all spending. 😄

Anyone curious what Wiki spends on: https://wikimediafoundation.org/who-we-are/annualreport/2021-annual-report/financials/#section-2.

Can confirm it’s the truth.

It’ll probably be great. That’s pretty much giaranteed based on the physics. That said, if you already have a mesh that has good connectivity, an antenna like this would probably just reduce the latency a bit. If you have latency-sensitive applications. I use an HA Yellow with its built-in Zigbee radio. It only reaches 5-10m. Everything after that is connected through the mesh.