degenerate_neutron_matter

Total RAM usage is a poor benchmark. Windows (and all other major OSes) cache frequently accessed files in free memory to avoid having to read them from disk every time they're accessed. The cache is freed when the memory is needed, so it doesn't impact how much memory applications can use, and thus shouldn't be included in usage benchmarks.

However, Task Manager counts cache memory towards the total usage, which tends to confuse people who think Windows is using way more memory than it actually is. I'm sure the article's conclusions about memory usage are still mostly correct, but it's good to keep in mind.

Human heaven is also cow hell, it's a very efficient system.

Didn't see this earlier but another thread gave a good summary: https://piefed.social/comment/9505729

Cool, but this article looks like AI slop.

I pay for several domains, as well as mailbox.org for email. Aside from that, nothing.

Looks like I've been spreading misinformation, whoops. Edited my comment to clarify.

I don't think it's a good idea either, but it's less egregious than filtering specific communities.

This filter is not part of any specific instance, it's hardcoded into PieFed's code. That means it applies to every PieFed instance unless the instance admin explicitly patches the code to remove it.

Got any other specific examples?

Each instance should be free to set their own rules. Individual instances blocking those communities is fine, but the PieFed devs hardcoding a blocklist that applies to all instances (especially one as opinionated and arbitrary as this) is absolutely not.

List of blocked words in community names:

shit
piss
fuck
cunt
cocksucker
motherfucker
tits
memes
piracy
196
greentext
usauthoritarianism
enoughmuskspam
political_weirdos
4chan

Seems like one of the PieFed devs has some opinions about the kind of content they dislike, and are unilaterally forcing that on every PieFed instance. I can somewhat understand filtering out curse words, but specific communities should not blocked by default, and definitely not hidden in a hardcoded list in the source code.

Edit: Important context here: https://lemmy.world/comment/21323475 Seems this blocklist is more limited in scope; it's not blocking federation entirely, just blocking (from what I can tell) their appearance in search and automatically federating with them when adding an instance. Still problematic to exclude specific communities in a non-configurable way with little justification IMO.

I'm confused; what's the difficulty shown here?