ChromeOS and ChromiumOS are Linux.
The problem with ChromeOS (and Android) devices is that hardware support is usually only available in a fork of Linux which gets as little maintenance as possible for the five years. You end up with the choice of running and old kernel that supports the hardware but not some new software, a new kernel that supports new software but the hardware doesn't work right, or taking over maintenance of the fork yourself. The same problem occurs with uncommon hardware on non-ChromeOS devices.
Be careful with doing this. X-Real-IP and X-Forwarded-For are good for when the client is a trusted proxy, but can be easily faked if you don't whitelist who's allowed to use those headers. Somebody with IPv6 access could send "X-Real-IP: 127.0.0.1" or something and if the server believes it then you'll see 127.0.0.1 in logs and depending on what you're running the user may gain special permissions.
Also be careful with the opposite problem. If your server doesn't trust the proxy, it will show the VPS IP in logs, and if you're running something like fail2ban you'll end up blocking your VPS and then nobody will be able to connect over IPv4.
The five year policy is for ChromeOS, not ChromiumOS. ChromiumOS-based devices may have more or less support.
If all you want is to break out the VLANs to NICs using a Linux PC instead of a managed switch, create six bridge interfaces and put in each bridge the VLAN interface and the NIC.
There's a lot of wrong advice about this subject on this post. Forgejo, and any other Git forge server, have a completely different security model than regular SSH. All authenticated users run with the same PID and are restricted to accessing Git commands. It uses the secure shell protocol but it is not a shell. The threat model is different. Anybody can sign up for a GitHub or Codeberg account and they will be granted SSH access, but that access only allows them to push and pull Git data according to their account permissions.
The hardware seems cool but most of the software features are things I would immediately turn off. Hopefully the Clippy+ branding gets changed.
If your options are waiting at the station up to 2 hours for a pod or waiting anywhere else 3 hours for a train, are the pods better?
Would it though? It's just vans on tracks instead of roads.
It's not going to be more energy efficient with individually powered cabs. It's not going to be more convenient unless your origin and destination are near a station. It's not going to be more time efficient because of the extra distance getting to and from tracks and because you aren't going to drive highway speeds in tiny self-balancing cars on old rails, especially when passing cars going the opposite direction. It's not going to be more cost efficient because it's more total moving parts requiring maintenance per person per trip.
It sounds like they are solving the problem of turning around only for terminal stations. This might make sense for trains that carry many people, but if you're making cars on tracks there is no good solution. If you need to spend money on a system that turns the cabs around, then you either spend more money installing those systems at most stations or you spend money maintaining cabs that are driving around empty. Either way, cars on roads are cheaper.
They say it's good for people who don't want to wait for public transit, but they don't say how this solves that problem. With public transit, you know when the train will be there. With this, unless they have a way for the cabs to wait at the station without blocking other cabs going the same direction, you have to wait for a cab to come and you can't time your trip to the station around when the cab will be there. Maybe they have one? It would be a disaster if you wanted to get on from near the middle and needed to wait for either a cab that has already been vacated to come or for a cab to come all the way from the start of the track.
Isn't this just Reddit with more steps?
Linux has had LDAP and other ways to use the same credentials across multiple machines since forever ago.
That sounds like Cloudflare is giving you certificates intended only to be used for talking to Cloudflare.
You might be able to do it if Cloudflare sends a different SNI. It's probably better if you get real certificates from Let's Encrypt and just use those.
That's not what I mean. When you contribute content to Stack Exchange, it is licensed CC BY-SA. There are websites that scrape this content and rehost it, or at least there used to be. I've had a problem before where all the search results were unanswered Stack Overflow posts or copies of those posts on different sites. Maybe similar to Reddit they restricted access to the data so they could sell it to AI companies.
Why now? Other people have been profiting off of your Stack Overflow answers for years. This is nothing new.
They have been in the process of rolling it out for what must be a decade now, meaning there are still areas where they don't offer it.
They don't allocate you a prefix. The website says they give you 5 addresses.
Some bad still ISPs don't provide IPv6 connectivity. (Verizon)
Really. My start menu has been nagging me "To show your recent files and new apps, turn them on in Settings." since the day I installed Windows 11. Why would I want the start menu randomly changing? I wish you could just turn the section off completely instead of breaking it and making it smaller.
Everybody hates Windows 8 but the Windows UI peaked at 8.1.
The live streams thing is not about advertising. Problems like putting the hearts button on top of the chat instead of next to the chat or having the chat cover up the entire left side of the stream every time a single message is sent are just because they don't care.
When can I access my own financial data via a read-only API so I can track my own finances using my own services?