kersploosh

Done. Enjoy your new community!

Offer accepted. I made you the mod of !curlyhair@lemmy.world. The old mod hasn’t been active for a long time.

I had not noticed. Glad it was sorted out. Ping me any time if you need help in the future.

Sure thing. It’s your community now. I created a test report so you can see how those look on whatever Lemmy UI you use. Feel free to resolve it.

Sure thing. It’s all yours now.

Hopefully it can be discussed a bit more calmly than the prior incident that I think you are hinting at. If there is clear data that the diet is harmful, then we could consider taking action per section 8.0 and 8.1 of the ToS.

Done. You are now the mod. Enjoy!

In case you aren’t aware, you will not receive reports from that community on your hackertalks account. There is a bug in Lemmy where community reports only federate to mods on the community’s home instance. You can work around the problem by creating a lemmy.world account for moderating lemmy.world communities.

It’s in the “Blocked Instances” section, where it should be.

sh.itjust.works explicitly blocks Threads. They held a vote among the local users: https://sh.itjust.works/post/11308397

It is odd that threads.net appears on our instances page, while the same is not true for other Lemmy instances which have not blocked Threads. Lemmy.world is federated with Threads by default simply because it is not on our instance block list. I do not believe our instance has done anything special to force a link with Threads. I mentioned it in our admin chat and will update this post if I learn anything.

However, even with threads.net listed on our instances page, Threads does not seem to work with Lemmy. I am able to search and view Mastodon user profiles from lemmy.world, but it does not work for any of the Threads test profiles.

Edit: The lemmy.world database has no records for a person on threads.net. Our best guess is that a Threads user tried to interact with lemmy.world. Perhaps the process got far enough for our instance to recognize threads.net and add it to our instances list, but not far enough to create a record of the user in our DB.