Yes, all internet dead. No escape from dead internet. I’m a bot. You’re a bot. We’re all bots here.

The short answer: For a router, either find an off-the-shelf Wifi router that is supported by OpenWRT (very nice and very easy), or (and this is my personal preference) build your own firewall mini PC which will be much more complex and powerful to the point of complete overkill but also fully controllable right down to the network stack (and what’s the point of a homelab if not fiddling around with such things?).

You can run OpenWRT directly on full AMD64 PC if you want, or even just a Raspberry Pi (some people appear to have had good luck with the 4B and 5, though I don’t know the specifics of that approach) The famous PfSense would be another option, based on BSD. I used to use that, but I really wanted something directly Linux-based.

Which brings us to the fact that you can also even use a standard Linux distro like Debian and install all the tools you want on top of that and set up all the firewall yourself from scratch. That is actually what I do, using Linux kernel’s nftables for NAT Masquerading/IP forwarding and managing it currently with foomuuri which is essentially just a very lightweight nftables configuration manager. It doesn’t do anything you can’t do directly with nftables, but even though it’s perfect for me but I’m not sure I would recommend it in general. They have some very simple examples, but the documentation is pretty sparse, you need to either understand nftables under the hood or infer what you can by reading between the lines of the few examples you can find. A more mature and traditional Linux firewall like firewalld might be preferable if you want. Either way, this is definitely a much more complex route though, and fighting with firewall rules to get things to work is not everybody’s idea of “fun”. It is powerful though, and infinitely flexible. If you want it to “just work” without hassle, stick to the single-purpose devices and use OpenWRT as the OS designed to do this. It’s way simpler.

If you do decide do go the DIY firewall route though, all you really need for a firewall PC is at least a second NIC (some motherboards have two wired NIC onboard already, you can use one for WAN and the other + WiFi for LAN) or you can a PCIe network card that has multiple ports. I wouldn’t really recommend using one of your existing Mini PCs for this, as it’s really not a good idea to share the firewall/network appliance functionality shared with other services, both for security and for configuration complexity reasons. The firewall really works best and is easiest to configure when it is truly just a gateway for the network, putting traffic from one side out the other side, plus whatever fundamental network/firewall services you need to accomplish that. When you start also trying to selectively route some of that traffic to actual services on the firewall itself, it gets really complex and ugly really fast, and even if you can get it working which is often very nontrivial, it’s also very fragile and it’s easy to blow open holes in your security this way.

I’ve actually now got a pair of mini-PC firewalls, both set up using foomuuri, uCARP and Kea to do failover with each other so if one goes offline the other takes over its IP and starts routing traffic until it comes back. It’s not perfect or completely bulletproof but it’s pretty good for an amateur! In a pinch (when my previous, non-redundant firewall died) I’ve also used an GL.iNet travel router as my network’s primary router temporarily and their routers support an expansion board with 5G/SIM support so that could be an option too. I have to say it worked perfectly and was actually pretty nice, my only hesitation is that the travel router (at least the one I have, Beryl AX) seems to run a bit hot and I’m not sure it’s really intended for 24/7/365 operation (plus I need it for when I travel). They do make home routers too though, so maybe worth looking into, they’re really nice hardware running their own fork of OpenWRT out of the box.

They don’t really understand anything because they don’t really think. They just repeat what they’re told while convincing themselves its an independent thought that appeared in their head as if by magic. These are the people outsourcing most of their thinking these days to ChatGPT, because it’s not something they’ve ever really valued or been interested in doing themselves. Life’s a lot easier when you don’t have to think about much. They’re “doers” not “thinkers”. And frankly, it shows. We see an awful lot of stuff getting done right now, and very little thinking.

It’s much different because you can fire your salespeople for failing to consult with the engineering team, promising shit that is impossible, going to damage your brand and reputation, and provide little-to-no return on investment.

The biggest difference is that you can’t fire ChatGPT (as much as I desperately wish we could)

It will be hardly any work once a law passes, because they’ll make sure it is. Everyone knows where the proprietary code is. It doesn’t just get merged in “by accident” unless you are a really shit developer (and to be fair some are).

Besides, no one is saying they have to open source it. To be honest, the outcome from this petition that I would most like to see is simply a blanket indemnity to the community attempting to revive, continue and improve the software from that point forward. If the law says that it’s legal once a software is shut down, for the community to figure out a way to make it work again and make it their own, and puts no further responsibilities on the “rights holder” at all, I think that honestly solves the problem in 99% of cases. It would be nice if they gave the community a hand, released what they could, and tried not to be shit about it, (and I know some of them will be shit about it, but we’re pretty resourceful), as long as they’re not trying to sue every attempt into oblivion I think we’ll make a lot of progress on game preservation and make the gaming world a much better place.

The rules will be the same as they always are: First Come First Served, and Might Makes Right.

You will likely have to use a temporary alternative until the name is removed so you can reclaim it. No idea how long that takes, it might not even happen automatically at all. It seems like there is a forum thread for it

Aha I see you did the text-based install then? I’ve never done that myself but I just tried it now and it worked fine for me with the default password it mentions. Make sure caps lock is off. You will not be able to see the password when you type it, so be extra careful you are typing it correctly.

Most of the same cautions about internet access still apply, if your networking is active on this VM there’s a non-zero chance you can get hacked right away when you’re in default passwords/initial setup mode. If you continue to have trouble getting in, you should reinstall it once again onto a fresh VM with network mode set to NAT if possible, or even disabled completely, and see if it works in that configuration. It really is critical to get the password set up before opening up the internet.

Not sure what you mean by “what was provided”… who is providing a username and password for your yunohost?

You are supposed to create your own username and password during the “Begin” setup process after it first installs. “root” and “yunohost” are very insecure and if you use passwords that are copy/pasted from somewhere else on a machine connected to the internet it will be hacked, potentially almost immediately. People have bots that literally just try to connect using these common default passwords all day every day to every site on the internet. I have literally had machines with such crappy passwords hacked within minutes of spinning them up. The same thing can happen even when you are first doing the setup process. If somebody else can get in, they can (most likely with a bot) do the setup process themselves and set up their OWN username/password, and now it will ask you for that password that THEY set, which you have no way of knowing. The instance belongs to the first person to claim it, and if that’s not you, you have to wipe it and start over.

Your yunohost VM interface should not be exposed to the internet during setup. Even briefly, or someone else can immediately compromise it like this. The only way to ensure you are the first person to access it is to make sure you are the ONLY person who can access it, until it is properly set up and secured. Bots are WAY faster than you can be.

Use localhost console, VM port forwarding or some other secure method of making sure nobody but your own host computer can access the IP of the server where you are setting things up, until it has a strong, secure password (not “yunohost”) and make sure you have all its security features configured and working before you even think about making it accessible to the internet.

AI slop games for everyone! We can use the entire power of a remote datacenter surrounded by natural gas burning turbines to simulate what each button press you make does. It will be frighteningly accurate and will offer new and unique gameplay features like nonsensical hallucinations of constantly changing non-euclidean geometry you must attempt to navigate, and the risk of real wildfire smoke making you struggle to breathe while you play for added challenge!

But if someone can’t be bothered to even use a throaway protonmail address to file a bug report or feature request? Quite frankly, what they have to say wouldn’t have been worth our limited time anyway.

You don’t know that, because you’ve never once heard what someone didn’t say. Their time is limited too.

I guess they are about to make John Romero their bitch now.

Jokes aside, it is sad to see all the cuts going on right now, especially since I think they’re stupid, shortsighted and misguided.

I think I’ll stick to AMD from now on, thanks.

Absolutely true, but the point isn’t whataboutism (well, sometimes it is, but it shouldn’t be). The point should be admitting and owning our mistakes and doing what we reasonably can to:

a) admit that we did and validate the experience of the people who suffered from it
b) make sure we’re not still doing it (way too often we still are, just through subtler means)
c) try to make reparations if we can

Even getting to step ‘a’ is a big fucking step. Nobody’s innocent, but honesty is the foundation on which improvements can be made.

Oh good now maybe the Subnautica developers can go independent to make a spiritual successor that isn’t called Subnautica and isn’t garbage.

Fuck Canada in particular, as usual. It’s starting to feel a bit personal.

They are freely expressing their fear of dangerous western ideas which must be censored to protect the motherland /s

You need to work on your reading comprehension then, because as I said:

OP’s comment is clearly saying they currently won’t go there because of the political situation. That’s why they said “BUT I’m not stupid”. They are agreeing that it would be stupid to go there now, that’s why their statement of wanting to go there is made conditional on a “but” that is false.

Like saying, “I love spicy food and I wish I could eat a whole ghost pepper at once, BUT I’m not stupid [implied: so I WON’T eat a whole ghost pepper at once]”

KSP1 is the bees knees and the modding community is still going as strong as ever. Still worthwhile even at full price.

That’s why we call them flavors. People like certain flavors. It doesn’t mean the nutrition is any different or that you need to always use only whatever flavor is somebody else’s favourite. The lovely thing about Linux is the freedom to choose and to try different things to find what works best for you personally. There’s no organization trying to shove certain tools and principles down your throat for profit. It’s literally just personal preferences and they’re all equally valid choices. We try to make recommendations on things that might be easier to grasp or might suit a person’s situation better but really they’re all just flavors and they’re all good for the people who like those flavors.