While this is necessary to prevent spiraling storage costs, it will also remove images from old posts when users prune their media collection. The impact of this will vary depending on the image - was the image the sole purpose of the post or just so that the post would get more attention?
I don’t have a solution right now, but I’ll put my thoughts here and hopefully someone else can think of a solution.
Some suggestions that have worked for me for keeping a code base consistent with multiple developers working on it, and avoiding the technical debt of different styles:
ruff is quick enough to use pre-commit.
It also give helpful hints when linting, like app/utils.py:924:16: E712 Avoid equality comparisons to False; use if not Community.banned: for false checks
Formatting the codebase is probably best done in a single merge commit. Fixing linter issues can be done whenever a file is worked on.
I’ve worked on Flask projects and switching to Poetry helped us with Flask plugin incompatibilities. At least it was detected by Poetry when adding them, not at runtime (that was what happened when Pip was used). Today I’d pick UV för dependency management.
Very interesting read, don’t miss the follow-up: https://dustycloud.org/blog/re-re-bluesky-decentralization/