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!
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.
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.
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. 😄
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.
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 don't think so, not by DFRobot at least. That said, I think 2.5G is only useful for >1G internet connections. On the LAN side, the switch is what matters for LAN throughput.
I saw a short interview with him by France 24 and he mainy said he thinks the current direction of the research teams at Meta is wrong. He made a contrast between top-down push to deliver org as opposed to long leash, leave the researches to experiment with things. He said Meta shifted from the latter to the former and he doesn't agree with the approach.
The organization has already transitioned to a nonprofit in the U.S. but is still working to set up a nonprofit in Belgium, or an AISBL, to replace the German entity, which lost its nonprofit status last year. Once established, the Belgian nonprofit will be the future home of the organization. In the meantime, the U.S.-based 501(c)(3) c nonprofit will own the trademark and other assets.
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!