

How much RAM does something like that need?


Fun fact, Igalia is a worker co-op that does open source development for hire.


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!
Thank you for your service @Track_Shovel
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.


Isn’t flushing bad for the microbiome?
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.


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.


Never had it. Z-Wave needs a differrnt antenna and since they’re using full-size antennas for these devices, the Z-Wave one is significantly larger so it’s a separate device.
Got the module some years ago when there were massive shortages. I found a couple CM4s and bought them at the time.
What are you comparing it to?
You’re supposed to set SQM lower than the WAN throughput. I think you’re right that by default it limits it by about 10%. There was some study over a decade ago on this that showed 20-25% limit is best for maximizing responsiveness under load. It’s not possible to effectively schedule packets if there’s no headroom.
I have a few Pi 4 + UE300 routers in operation that work just as well but this is a nice alternative if you have a CM4 lying around.
So not an AMD AM5 dual-channel system. 😅