Currently burggit is using lemmynsfw.com's lemmy-ui changes. Besides displaying NSFW posts to logged out users, they also auto-expand content and unblur nsfw thumbnails.
There's no major problem with that for lemmynsfw (and they tell in the sidebar you can block communities you don't like), but i can see why this would irk some people on this instance.

I think the latter 2 changes can be reversed at a stylesheet level, which AFAIK burggit already did previously when spacing items. would non-autoexpanded content and blurred NSFW thumbnails be a good compromise?

I would bet with the way modern Google works, nobody is coming here from a google search either lol.

burggit.moe/robots.txt pre-empted that out.

/u/The_Entire_Circus has been linking to burggit as a way to mirror reddit posts more likely to get moderated/AEO'd, but i haven't seen this convert into more sign-ups.

Maybe part of it could be the "ghost town" appearance the feed shows when logged out - NSFW content isn't displayed to logged-out users, so scrolling out of the first page is enough to show week-old post dates.

Scanning through the logs, in the fallout of this they also banned @InternetTubes@kbin.social for "ban evasion", FinalBoy1975, HardlightCereal, as well as butts@ani.social(for commenting about this in an entirely different instance) and AMillionNames@sh.itjust.works(assumed to be an alt of an user who hasn't posted on lemmy.world but also criticized it).

Just wow.

How was this decensored? other than some very slight discoloration i can't see significant changes compared to the censored version posted on the artist's fanbox.
Decensoring neural nets like DeepMindBreak/DeepCreamPy would show more visible artifacts.

no, they defederated early on.

pro-contact.

The community was originally created in reaction to /c/cunny deciding against allowing oppai loli. Restricting it to sholicon only would result in no communities for that kind of content.

manually checking the list, there are some communities that defederated but remain in the list:

• social.cyb3r.dog
• f.jbradaric.me
• bookwormstory.social
• lemmy.vinodjam.com
• ka.tet42.org
• dubvee.org
• lemmy.kensand.net
• moot.place
• lemmy.phoenix591.com
• lemmyland.com
• lemmy.buzz
• lemmy.pe1uca.dev

as well as some communities with policies that would clearly defederate burggit:

• lemmy.serverfail.party
• civilloquy.com (defederated lemmy.burger.rodeo)
• discuss.tchncs.de

The list also includes plenty of single-user instances without any posts, as well as instances using whitelists not including burggit.moe and a few local-only instances, though i didn't bother making lists for them.

You should be able to fetch instance block lists from other instances (which on most lemmy web UIs is exposed in /instances) - but even that isn't a requirement AFAIK :-/

Doing a quick check on changes from 0.17.4 to 0.18, seems like the most probable culpirit are these lines from this commit.

It doesn't look like these changes were intentional either. Seems like the intent was on making deleted/removed posts not visible to non-mods/admins/creators on community post listings, rather than not visible at all.

I've got zero experience with asynchronous rust (or rust, for that matter), but this doesn't seem too hard to change (other than a potential distinction between removed and deleted posts). i'll still need to figure out how to make sure the changes don't break something else in the process, though.