When you delete something, your instance sends it the instance of the community. The community is suppose to process that and then forward that delete to every instance where a subscriber of that community resides. In this case, either zip failed to send the delete to world or something went wrong on world.
Or for the new crosspost display to be collpased by default.
That’s what Photon and Thunder do and imo, it works pretty well. Especially for posts with like a 10 crossposts, example.
If a post contains content that is not allowed, the post should be deleted, that’s it.
OK, but what about content that is allowed, but has certain restrictions, like needs to be tagged NSFW. The current workflow to get this changed is: A mod comments under a pot telling the creator to tag it NSFW -> Remove the post -> wait for the creator to edit the post -> restore the post. This seems needlessly complicated and labour intensive, no?
.ml is running the beta branch that actually started to apply image size limits to thumbnails, your app is probably using the thumbnail URL instead of the main URL and thus getting the compressed image.
This has been fixed https://github.com/LemmyNet/lemmy/pull/4937
Lemmy’s upvotes are same thing as likes, and downvotes are dislikes. This is kinda hard to tell because Mastodon doesn’t federate likes, so Lemmy posts will always show up as having no favourites.
No, the devs have explicitly stated they don’t want to add following users to Lemmy.
Interesting project, I hope it takes off. Definitely a problem I’ve run into.
website may be grammatically incorrect
I only noticed three small mistakes.
Communities in Lemmy are only federated if a user is subscribes to them from external instance.
This should be ‘subscribed’ and ‘an external instance’.
I think mods (including me) wouldn’t to put effort into a new community
Should be ‘wouldn’t want to’.
Build communities without the middle men.