There is the old adage “Nobody got fired for going with Microsoft”, and it is real.

If you, as an IT guy recommend Linux, and some exec has a problem with his laptop (which they would have had no matter what OS is running on it) it WILL be your fault because you changed something.

The cost they charge for buying a new car and the cost they pay for the parts of that car are very different things.

They will charge $50k with or without AM radio and would rather do it without.

So the next solution is to let it connect to your network but then block it at the firewall. That way you have full control over what it sees.

It is a dumb arms race between consumers and the devices they purchased

My main workhorse VM is Ubuntu LTS because when I set it up I just picked it instead of spending another week researching and trying different distros. I could look into swapping it out but nothing has annoyed me about it once I figured out to disable snaps.

It feels like every time I finally have something set up and running I find some article telling me that what I chose is dumb for reason xyz and I really should be using something different, but refactoring at this point is a pita so why mess with something that isn’t broken?

I found this comment on what happened by dani-garcia, one of the main devs:

The short version is that around 8-ish years ago, Bitwarden changed the way the vault items were structured, and Vaultwarden added some backwards compatibility fields to ensure both old and new versions of the clients worked.

These backwards compatibility fields were supposed to be a temporary measure, but for at least the next three years the clients still required them, until we eventually forgot to keep track of them. At some point between 2021 and today, the clients stopped requiring these backwards compatibility fields, but Vaultwarden was still sending them.

This wasn’t a problem until Bitwarden decided to use the backwards compatibility fields in a completely different way, which caused the clients to crash.

Found here: https://github.com/dani-garcia/vaultwarden/discussions/7473

Would this make them useful to side load your own firmware to them? This “exploit” could make these into a hobbyist’s dream

I think I am using the wolf launcher? I can’t check right now, but I set it up a long time ago and then forgot about it.

I haven’t had any problems with it, I have both a tube and a shield pro and the white circle button works great on both.

There might also be a button remapper that you can get if you want the Netflix button to be a mute or something.

I have a ShieldTV plugged into mine and it has been great. You can install a new Launcher to have full control of what you see and it works great. I pretty much just use it for Jellyfin and YouTube now, but in the past have had all of the streaming services at one time or another.

I like these posts, I feel like there are many levels to any self hosted setup and getting an idea of what everyone is doing is fun.

My 2012 Toyota has an ‘app’ that I maybe tried once over ten years ago but haven’t used since. This is nothing new. It is called “Toyota Entune”

I mean, that has been Microsoft’s MO for their entire existence. With the exception of maybe some versions of Visual Studio, everything they have done was see what they can copy off their competitors.

I would say their findings would be pretty consistent no matter which DBMS you use.

This goes to show that using uuid4 is not a good thing for db tables, but that is what uuid7 was designed for. Also using ROWID or autonumber or whatever built in system the database is using is the best bet. Only use uuid7 if you need distributed inserts and you want the clients to be able to generate their own keys.

I have played with qwen3-coder:30b for my hobby stuff running on my M5 max MacBook and it does alright. It is fast enough and I used ollama tools to let it request files. I haven’t used anything like Claude code to compare it to though, only a bit of the ChatGPT free tier stuff.

I remember this happening to Linksys with the WRT-54g routers. They shipped with firmware based on open software (I don’t remember the exact license) and they were brought to court and forced to release the source code.

In the end it really helped the sales of that model because hobbyists wanted it for the freedom of running their own code on it.

Do you have an example of a project that has both free and commercial licenses? How does that work in practice?

The problem from a user interface perspective is that the search bar and the url are the same field. I don’t have edge, but what happens if they type “Google” into the url bar vs “Google.com” vs “https://google.com”/.

I have this problem at home when I try to go to a device on my lan, like how “http://jellyfin.lan”/ works but “Jellyfin.lan” takes me to a search page.

I did it, well… because I could.

That is a very valid reason. I could see setting it up to learn more about how IPv6 works. I just wanted to see if I could get any actual advantages with it.

office situation where there are a large number of devices

That would make sense as a place to have it. Having a large number of devices where each having an external IP would be handy. My environment really only needs one or two devices having direct external access.

I mean, I don’t have NAT traversal between my NAS and devices on my lan now, they are routed because they are different VLANs but that would happen anyway.

Do people have problem with ip conflicts? I guess if I wasn’t running DHCP that would be possible.

Right now NAT is my main firewall between most devices and the wider internet, but I do still run pfsense and have firewall rules in place.

Switching over to IPv6 seems like it would be extra work for very little actual benefit.

What do you get out of IPv6 for lan routing vs just sticking to IPv4 for everything?