Nutomic

To implement hardcoded edit limit needs: - Simple checks in API edit handlers - Simple checks in federation code - Same hardcoded checks in lemmy-ui and other frontends - Document...

This sounds like a very specific use case which would be rather complicated to implement. Maybe best to do it via an [extension](https://github.com/LemmyNet/lemmy/issues/3562).

Its most likely `purge_image_posts_for_person()` which loops through a potentially very large list of posts, and makes HTTP calls to pictrs for each item. Similarly it loops through all communities where...

Closing in favor of https://github.com/LemmyNet/lemmy/issues/4572

Unix timestamps dont include timezone, so this would risk reintroducing the problem which was fixed by https://github.com/LemmyNet/lemmy/pull/3496. Also API responses can be gzipped, then there should be no significant size...

Too much effort for very little benefit.

> How to handle breaking changes to GetSiteResponse? Can custom_emojis and taglines only be removed on api/v4? We can publish this in 0.19.x, and then remove the `GetSiteResponse` fields in...

Yes it would be much simpler with caching. Caching different pages would be possible with cache key `(category, page, limit)`, but an attacker could bypass it by calling with various...

Keeping pagination is also fine. In that case it makes no sense to do caching in Rust, better leave it to nginx. That is already handled by cache-control headers which...

Made a few changes: - Removed is_valid_tagline_content() because a limit of 50k is completely meaningless. Anyway taglines can only be set by admins so we dont need much verification -...