Space. The 64gb micro already has little usable space for games, and hibernate requires that you write all of the contents in RAM to disk. Rather than fracture their feature set by model options, Valve instead decided not to bother with it (just guessing).

That, and as another person said, hibernate just hasn’t enjoyed great support under Linux. There are definitely other issues that need to be fixed with the Deck, like the audio bug while docked and the need to disable half the CPU cores in order to have good emulation performance.

You had me in the first half, not gonna lie

He should be fired out of a cannon and into a volcano

MBAs and VCs

Yo ho!

Well you kept apologizing for it. We Americans aren’t accustomed to that.

How is this even a response? Oh, just do what you deem appropriate and nothing else? Get outta here with that nonsense.

Hell is other people

Excellent! Thank you for doing this!

They get new knowledge placed in their heads while using the transporters.

I just had to replace the heat cartridge and thermister on my hot end. The print I had going when they failed was 35/37 hours in.

I still have massive affection for my 3D printer, but the HP inkjet printer my wife bought during the early days of Covid is my mortal enemy.

That probably is the best solution because it keeps the moderation burden off of the individual sites.

I deleted ~2300 comments and submissions… Steve’s not going to train AI off of my work while behaving the way he has. That entire company can go pound sand.

In practice this would be difficult to implement because each instance has its own take on how to shape the code for their site. There’s no obligation to create an instance so that it will be compatible with everyone else’s instance, and in fact I would guess that would be effectively impossible.

Let’s say Instance A allows porn, and a user on A wants to create an account on Instance B, but Instance B doesn’t want any porn on their server. At minimum, a way to keep any porn on that user’s account from syncing to B’s server would have to be implemented.

This is only a single case. There will be plenty more small issues like that to have to work around, so it will take a lot of time to get all that logic designed, implemented and tested.

The cloning of an account might also involve a not-insignificant amount of data being transferred. What if the receiving server wants to limit the amount of data storage for a new account so that they’re not burdened with storing tons of data for new, unknown users? How do you then determine what subset of that user’s data to import?

Maybe these things will happen with enough time, but for now I think it’s best for now at least if everyone thinks of each instance as its own separate website that can communicate with other similar sites rather than a set of cloned sites where which one you pick doesn’t matter.

Please don’t take this as argumentative, as we need people to share ideas like yours! I just keep seeing messages that give me the impression that people have expectations for the Threadiverse that aren’t currently realistic given what the state of the software is now.

They’re almost literally going to cut off their nose to spite their face. The absolute lack of understanding of the consequences of their actions is… entertaining at least.

If you tried it a few days ago during the reddit blackouts, it was getting overwhelmed with traffic. The sole owner/operator has largely improved things in short order though. It was much better today.

Could a subscription to a decent VPN solve that for you?