this post was submitted on 21 Oct 2025
734 points (99.3% liked)

196

4668 readers
1204 users here now

Community Rules

You must post before you leave

Be nice. Assume others have good intent (within reason).

Block or ignore posts, comments, and users that irritate you in some way rather than engaging. Report if they are actually breaking community rules.

Use content warnings and/or mark as NSFW when appropriate. Most posts with content warnings likely need to be marked NSFW.

Most 196 posts are memes, shitposts, cute images, or even just recent things that happened, etc. There is no real theme, but try to avoid posts that are very inflammatory, offensive, very low quality, or very "off topic".

Bigotry is not allowed, this includes (but is not limited to): Homophobia, Transphobia, Racism, Sexism, Abelism, Classism, or discrimination based on things like Ethnicity, Nationality, Language, or Religion.

Avoid shilling for corporations, posting advertisements, or promoting exploitation of workers.

Proselytization, support, or defense of authoritarianism is not welcome. This includes but is not limited to: imperialism, nationalism, genocide denial, ethnic or racial supremacy, fascism, Nazism, Marxism-Leninism, Maoism, etc.

Avoid AI generated content.

Avoid misinformation.

Avoid incomprehensible posts.

No threats or personal attacks.

No spam.

Moderator Guidelines

Moderator Guidelines

  • Don’t be mean to users. Be gentle or neutral.
  • Most moderator actions which have a modlog message should include your username.
  • When in doubt about whether or not a user is problematic, send them a DM.
  • Don’t waste time debating/arguing with problematic users.
  • Assume the best, but don’t tolerate sealioning/just asking questions/concern trolling.
  • Ask another mod to take over cases you struggle with, if you get tired, or when things get personal.
  • Ask the other mods for advice when things get complicated.
  • Share everything you do in the mod matrix, both so several mods aren't unknowingly handling the same issues, but also so you can receive feedback on what you intend to do.
  • Don't rush mod actions. If a case doesn't need to be handled right away, consider taking a short break before getting to it. This is to say, cool down and make room for feedback.
  • Don’t perform too much moderation in the comments, except if you want a verdict to be public or to ask people to dial a convo down/stop. Single comment warnings are okay.
  • Send users concise DMs about verdicts about them, such as bans etc, except in cases where it is clear we don’t want them at all, such as obvious transphobes. No need to notify someone they haven’t been banned of course.
  • Explain to a user why their behavior is problematic and how it is distressing others rather than engage with whatever they are saying. Ask them to avoid this in the future and send them packing if they do not comply.
  • First warn users, then temp ban them, then finally perma ban them when they break the rules or act inappropriately. Skip steps if necessary.
  • Use neutral statements like “this statement can be considered transphobic” rather than “you are being transphobic”.
  • No large decisions or actions without community input (polls or meta posts f.ex.).
  • Large internal decisions (such as ousting a mod) might require a vote, needing more than 50% of the votes to pass. Also consider asking the community for feedback.
  • Remember you are a voluntary moderator. You don’t get paid. Take a break when you need one. Perhaps ask another moderator to step in if necessary.

founded 9 months ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] infinitesunrise@slrpnk.net 11 points 3 days ago* (last edited 3 days ago) (3 children)

Quick aside: Always irks me when someone says "Blockchain" singular, like it's a proper noun entity cargo cult god. "A blockchain" is a particular type of data structure akin to a decentralized linked list, or in the context of one particular cryptocurrency you'd say "the blockchain". I know that the crypto VCs use the word in that singular proper noun way, but they're doing that intentionally to cultivate a misplaced reverence and we shouldn't ape them.

Anyway bitcoin core v30, which just released, expands the maximum data size of a non-monetary transaction parameter called the "OP_RETURN" from 80B to 100kB, meaning that normal bitcoin transactions really can now store plain old jpgs with basically zero extra encoding. It was a wildly controversial change within the dev community, some people probably being paid under the table to push it through etc, but yeah it can do that now. I assume that some blackhat has already put CSAM onto the blockchain in protest.

However at this time you only have to pay < 0.2 sats/Byte to almost guarantee your transaction goes into the next block, so absent miners showing discretion and refusing to mint big OP_RETURNs, that 100kB transaction would actually only cost about 20,000 satoshi, or ~22 USD.

[–] chicken@lemmy.dbzer0.com 11 points 3 days ago* (last edited 3 days ago) (1 children)

It was a wildly controversial change within the dev community

Sounds like it would be, isn't the reason to keep storage expensive that everything included in a transaction needs to be stored forever by every single network participant running a full node?

[–] infinitesunrise@slrpnk.net 8 points 3 days ago* (last edited 3 days ago)

Yeah that's the dominant perspective, and the way I see it. The core devs seem to have the perspective that if they don't allow storage of arbitrary data, they'll only encourage the abuse of other transaction parameters to work around it, or encourage anticompetitive side channels where users pay miners directly to include their zany data. And that by opening the floodgates, they allow market competition to decide how much that data is actually worth.

The blockspace has not exploded to capacity with OP_RETURN data in the past week, so the whole controversy could just end up being what politicians these days call a "nothingburger", without even the demand to reveal who was right now that the NFT craze has mostly ended. And if that's the case, the core devs technically made the right choice. We'll see.

[–] hperrin@lemmy.ca 1 points 3 days ago* (last edited 3 days ago) (1 children)

What I was talking about is the storage requirement for holding a blockchain containing every NFT ever minted on that chain. That’s a lot of storage if it’s the actual images.

[–] infinitesunrise@slrpnk.net 1 points 3 days ago* (last edited 3 days ago)

Oh yea you'd be trying to store essentially a whole image hosting site, it'd be absurd and only data centers would do it. In the case of bitcoin the block size limit is roughly 4MB and they rarely if ever hit that. Whole chain going back to 2009 is less than 800GB.

[–] explodicle@sh.itjust.works 1 points 3 days ago (1 children)

I've heard Bitcoin on-chain CSAM allegations for years but could never verify it. It would be interesting if a pruned copy was safer than an archival copy, forcing users onto Tor if they're unwilling to trust anyone.

[–] infinitesunrise@slrpnk.net 2 points 3 days ago

Pruned copy would indeed be safe, it omits OP_RETURN data completely.