pixelfed.social's statuses table is 30G
I really need to ship a command to purge remote posts older than X without any interactions (they can be re-fetched via search)
I'm going to drop the `entities` column since we don't use it and it takes up a lot of space
Also considering dropping the `rendered` column, storing two copies of the same post caption (one with html markup) isn't efficient, we can autolink on demand.
😅
Regarding the `entities`, we transform posts based on a defined schema, then cache it (and remove/add attributes depending on if client is mastodon compatible) and finally hydrate state (liked,bookmarked,shared).
By moving the autolinking (converting plain text to html with hashtag/mention links) to the cache step we can eliminate storing it in the database, and also better handle autolink changes (mentioned user deletes account)
