There's also a good chance that reproduction cases are more specific than they may seem, such as applying only to specific GPUs, OS versions, display resolutions, other hardware, etc., and logs provide a lot of that data without any back-and-forth or the reporter having to manually collect it.

Having an easy reproduction is great, but that still means that work has to be done to get things set up for that, potentially interrupting workflows and slowing things down a bit - while a log might contain information making the issue super obvious right off the bat, avoiding that extra effort.

Naturists (nudists) like myself often express a greater connection to nature and the environment around them, so this is 100% on track. It's in the name, after all!

This looks really dope! I'm a sucker for pretty particle effects, so I'm glad my off-handed comment resulted in them becoming even more versatile in Resonite! Haha

Thanks! <3

Soon: smelly

This is why Mastodon seems to me like the only long-term "correct" option, but it has its own set of problems that are hampering growth at the moment, and Bluesky is pretty good for the time being.

Definitely not in one single Docker image, but providing an out-of-the-box option for it as part of a Compose setup makes total sense to me. I feel like I might know what brought this question up, though. :^)

I use btrfs btw