I'm not entirely sure I believe that isn't what "talking with each other" is. How are those two fundamentally different things?
Because when I talk in person with friends and family, it's mostly just us sharing our opinions and observations back and forth.
I'm only peripherally aware of the SCP community, but I really enjoy browsing the stories... what's fallen apart about it?
I've noticed that almost everyone has missed the most "cloud-native" aspect of the Universal Blue project: The build process.
What's really cool about this is that the images are built in a "cloud-native" way. Right now, they're just using Github's actions pipeline to push images. This does a couple of very cool things.
First: It means that any image that gets sent to your device was already built on a system and checked as OK. It's still technically possible that a bad image could get pushed, but the likelihood is extremely low because they are tested as a single cohesive unit before being sent to anyone else's device.
With traditional distros packages are built on a system and tested, but they're not necessarily tested in a single common environment that is significantly similar between everyone's device. This largely deals with dependency hell, and weirder configurations that cause hard-to-diagnose problems.
Second: It also simplifies the build process for the Universal Blue team because they are able to take the existing cloud native images from fedora and just apply some simple patches on top of that. While doing this in a traditional distro way as I understand it would be far more complicated. This is why Universal Blue was able to update their images to Fedora 41 like... 24 hours after release? It was crazy fast.
The creator of Universal Blue is also on the fediverse! I don't know if this will actually ping them, but it's worth a try.
I can't not notice it. It jumps out at me, the exact same as when someone does a non-three-dot ellipse.
I feel like the Monty Python priest with the Holy Hand Grenade of Antioch
"Three shall be the number thou shalt count, and the number of the counting shall be three. Four shalt thou not count, neither count thou two, excepting that thou then proceed to three. Five is right out."
I don't mean to be rude, but why didn't you just reply to the comment that you're directly talking about? That's pretty much what the reply feature exists for... that, and replies.
She should be aware that likely almost 100% of those returned clothes are going to the dump. Unless this is a very reputable seller, with a trustworthy supply line, even if they say they recycle or resell, they likely don't.
https://github.com/bottlesdevs/Bottles/issues/2345#issuecomment-1733132198
To me it looks like the devs of Bottles said that they'd be patching Bottles to remove support links in non-flatpak versions.
So... isn't what openSUSE did in the spirit of that? Obviously, them packaging it at all is against the devs' wishes, but... I dunno, this whole thing is a mess.
Edit: I may have confused "support links" with the "donate button". However, I am still confused, and this situation is a mess. I sympathize with the bottles devs, because it's good software, and they are largely volunteer developers. Beyond that? *exaggerated shrug*
Whoa whoa whoa! No need to be so hostile with each other, why can't we just get along?
Most activity
[email protected]
Pretty active
[email protected]
Very little activity
[email protected]
Also a reddit repost bot instance
[email protected]
Thanks for pointing that out! I was looking for an original source, but the articles Wikipedia uses as sources are from a defunct journaling site. However, you can see at least one of the original articles through the wayback machine.
Yes, Grim Dawn is fantastic, especially if you enjoyed Titan Quest and want more. HOWEVER I don't believe that it's from the same devs. Where did you hear this?
I can see that Crate Entertainment licensed the engine from the original Titan Quest team/publishers, but I see no evidence that this was developed by the same people as Titan Quest.
If we're asking what people mean when they use those descriptors, then you're correct.
However, literally speaking, in this context, immutable only means read-only, and atomic only means that updates are applied all-at-once or not at all (no weird in-between state if your update crashes halfway through).
The rest of the features (rollbacks, containerization, and immutable meaning full system image updates) are typically implied, but not explicitly part of the definition.