https://fba.ryona.agency/ is one website that can help, top search box searches for instances that have defederated from the one you entered, the bottom one lists the instances the one you entered defederated from.

It only shows full instance level defederation, not blocked communities though

In the meantime, if you want both reddit like and twitter like functionality, checkout kbin. Kbin federates with both lemmy and mastodon and has both magazines (their version of communities) and microblogging (like twitter/mastodon)

mind replying to the OP since most of us are on instances hes (likely accidentally) blocked?

By setting an allow list hes blocked every other instance not in his list

https://join-lemmy.org/docs/administration/federation_getting_started.html

Allowlist: Explicitly list instances to connect to. BlockList: Explicitly list instances to not connect to. Federation is open to all other instances. Open: Federate with all potential instances.

Federation is enabled by default. You can add allowed and blocked instances, by adding a comma-delimited list in your instance admin panel. IE to only federate with these instances, add: enterprise.lemmy.ml,lemmy.ml to the allowed instances section.

0.18.3 is bringing in more sanitization, probably got missed.

I poked them and they’re working on a fix

Update: fix is in and should be in the next rc. It does work ( built my personal backend from source)

if no one on your home instance was subscribed to the community, it wont get posts or comments. the first time someone on an instance searches the community it seems to just get a few of the old posts but it doesnt get their comments; if you or someone else on your instance subscribes then the instance will get new posts and new comments

it runs fine if you don’t cross-compile and build it on the pi itself ( or emulate an arm system using qemu or similar)

They fixed it ( the 2fa bypass; now resetting password won’t log you in) looks like it’l be in 0.18.3 ( not out yet, but its up to release candidate 3, so soon)

some communities themselves are tagged nsfw. That might cause what you’re seeing.

Just make sure any nsfw stuff you do post you manually check the box as well.

no man, that “shorthand” is exactly how you’re supposed to search for new communities. Its exactly how I’ve added every community to my personal instance

just hang out on the search results for a moment and itl get pulled in and show up.

note that doing this it only pulls in a few previous posts, someone on your instance (you) needs to subscribe to the community for your instance to get new posts and comments.

apparently lemmy.world had some issues part of saturday so that may be why you had issues with your search, but they setup cloudflare so they’ll have less in the future.

if you want specific old posts search for the post’s original url on your instance, same with comments.

if you’re impatient like me you could just grab the latest code from git; there’s another change in there that dramatically reduces the database size: my one person instance went from having a database dump taking 1.3 Gb to 250Mb.

it does the hot update every 15 minutes now and it pretty much instantly nuked the ancient posts when I started running with it.

a bug that was/will be fixed that mostly stoped posts from aging properly. it and some other nice things should be in the next release.

Something with how the ui handles ban lengths that arn’t permanent but are still far far in the future.

If you’re an instance owner you can fix it by making those bans permanent by editing the database

to underline getting those records setup, without them others can send emails pretending to be from you. They set who is allowed to send emails as you and how to check.

one of my first dmarc reports showed some russian ip address trying to send a few from my domain.

you tell it what you mean by lemmy and lemmy-ui earlier in the config file outside of the server {} block

upstream lemmy {
# this needs to map to the lemmy (server) docker service hostname
server “127.0.0.1:8536”;
}
upstream lemmy-ui {
# this needs to map to the lemmy-ui docker service hostname
server “127.0.0.1:1234”;
}