 You know, I'm kinda surprised that Mastodon doesn't employ a media storage structure like @pixelfed What I mean is that in Pixelfed, we store media in per-user buckets/directories, allowing for easy mass deletion with a single request. I wonder if they will update this to make it easier to mass purge account media 3 comments
@thisismissem @hongminhee Ah I see, I’m glad I had the foresight to handle this properly when designing this back in 2018. Also thankful for not depending on a 3rd party lib for such an essential feature, I don’t blame Mastodon for this though, being that Pixelfed is media focused, it was a higher priority design constraint in my mind.  |
Gregory's Server
@dansup @hongminhee
Long complicated reason: mastodon currently uses a legacy attachment manager package for Rails and it's ridiculously complex to upgrade to ActiveStorage or something else without needing to reupload all media (which would potentially be prohibitively expensive for server operators & require publishing update to all existing notes & actors containing media)
- https://github.com/mastodon/mastodon/issues/5729
- https://github.com/mastodon/mastodon/issues/7414
- https://github.com/mastodon/mastodon/issues/30352
@dansup @hongminhee
Long complicated reason: mastodon currently uses a legacy attachment manager package for Rails and it's ridiculously complex to upgrade to ActiveStorage or something else without needing to reupload all media (which would potentially be prohibitively expensive for server operators & require publishing update to all existing notes & actors containing media)