I was also intrigued by the introduction of the matter standard, but the reality is there are already a ton of low power, cheap ZigBee devices out there that can operate for years on a battery.
I think I’ve run into one thread/matter compatible device that I was considering, but found a HA forum thread saying their experience with that protocol+device+HA wasn’t as stable. So I didn’t do it. I’m not even sure how cheap and low power thread/matter devices can get.
Man, just when I think I understand home networking…
Interesting, yeah I’m not actually well versed, that’s why i began with “afaik” hah. My experience with EdgeRouter is that you basically have to enable hw offloading to get the full throughput, and my assumption was that probably all off-the-shelf routers are doing something similar for them to be usable in such a small/cheap/lower-power box.
When you say I might be thinking of “switching hardware”, I assume you’re referring to “managed switching”, and isn’t that just routing without any NAT? Like, if your pfsense router has 4 NICs, then it has to do the job of both a router and switch, no? First one, then the other for each packet?
Afaik, you’d want hardware acceleration for the actual packet routing, or it’ll be quite slow/inefficient. So any ASIC for routing packets would be considered a “router”.
I wonder if there exists an open router design based on an FPGA platform…
Doesn’t the law expect “Operating Systems” to do this? I feel like everyone should point fingers and lean on bureaucracy. Systemd should say “well don’t look at us, we’re not an operating system, we’re just an init and services system”, and Linux says “well we’re just a kernel, usermode does whatever it wants”, and Debian says “well we’re just a distro, we didn’t write any of the packages we just stick them together.”
If the tech illiterate idiots who wrote the poorly thought out law can’t figure out who to ask, maybe they’ll do their due diligence next time.
As a software engineer, I’m convinced “vibe coding” is just a meme. It’s like watching a chaotic system. You need to constantly be wrangling it back on topic, and keep it from bloating the codebase, in order to get anything done. You may be able to vibe a small mockup, but it will inevitably go off and produce garbage that doesn’t make sense.
It is useful as a glorified grep, and a sort of natural language to programming language compiler for simple descriptions. But if you don’t already understand what you expect the LLM to output, you’re gonna have a bad time.
it will not implement such measures unless legally required.
What a bold stance 🤦
It’s just another routine fascist strategy:
“All within the state, nothing outside the state, nothing against the state.”
“When goods don’t cross borders, soldiers will”
So your claim is both that the Linux kernel operates perfectly fine without systemd for certain distros, and also that the Linux kernel is heavily dependent on systemd and it would be difficult to re-engineer to work otherwise. Do I understand your argument correctly?
Gnome is not Linux.
Also very windows like, aside from Mount.
It’s already solved: FOSS means I can always fork/build my own package that does what I want. That’s why I mean it’s immune.
What concerns me is the implicit association people will make between him and FOSS, and anything they believe about one will carry to the other.
I have to assume there are already people who hear “Linux” and think “ugh, I wouldn’t touch that with a 10ft pole because I don’t want anything to do with Pewdiepie”. Similarly, if he says something dumb next week, and half his audience abandons him, they’ll likely have a negative outlook on FOSS going forward.
Either way, I don’t believe FOSS’ staying power comes from meteoric rises following a fad, it comes from a natural immunity to enshittification over time. On the scale of a few of decades, FOSS seems like it’s struggling against proprietary solutions. But just like the general concept of political democracy, I think on the scale of centuries it will become the clear, time-tested, least-bad option. But I digress.
For an actual answer, it looks like WD has something called wdckit that is available on request.
I see a corresponding AUR entry that looks like it’s grabbing some zip from a personal Russian CDN. Super sketchy looking tbh.
But it’s possible this tool has whatever functionality the windows WD Utility uses to toggle the light in the drive’s firmware.
IMO, it’s not worth it. I’d just go the electrical tape route and maybe ask WD Customer Support if there’s a way, and if not, ask that they support Linux better in the future.
I’ve run into this issue with obsidian, but for whatever reason I haven’t had any issues with keepassdx.
When opening an existing keepass vault, on the left there’s an “Open From” pullout menu. You should be able to select your nextcloud from there. Then find your keepass file and it’ll just work.
I don’t know why, but obsidian doesn’t have the same file picker. There’s no “open from” menu. So you just have to drill into the filesystem, find the folder nextcloud is using, and choose your notes vault you’ve sync’ed in there. And for whatever reason, that seems to be the method that breaks Two-Way Sync.
I use Nextcloud + KeepassDX on android and KeepassXC on PC. Have never had an issue. Changes on desktop/phone are propagated virtually immediately across devices.
Everything is always optional for power users on linux. What I’m saying is they shouldn’t have made a GUI checkbox that’s also easy enough for non power users to check.
Yeah, people keep correcting me by reiterating exactly what I’m saying lol
The difference is they test the core packages they release. That’s their selling point. Just downloading old pkgbuilds without vetting anything is called an attack vector.
If it’s just for you, then you don’t need to tackle the hardest problem of content moderation.
The second hardest problem is bandwidth. If you post something to a forum that suddenly gets a lot of traffic, without some kind of CDN intermediary, you’ll get a hug of death and/or a huge bill for all the bandwidth.
The third hardest problem is uptime. My assumption is that you want the content to remain valid forever. No one likes seeing dead links in old forum threads. So as you use it over time, anything you’ve posted over the years could get a sudden unexpected viral hug, or you have to let it die (which may not necessarily stop the hug, since everyone would still be trying to ask your server for the content).
Just making sure you appreciate how difficult solving this problem inevitably becomes. Note that discord and Lemmy Posts let you upload images, so you shouldn’t need such a service in those cases. But for random forums, it quickly becomes hard.