Both #Bluesky and #T2 provide users with the *option* of not including "link previews" (which may include attached images) with posts. This avoids the need to include (for example) cat photos to supersede random link target page images. (While I realize Leela is much loved, photos do use bandwidth and other resources, and link previews to a large number of followers can effectively be a denial of service attack on the target site due to so many instances trying to fetch at the same time).
While #Twitter has never provided this useful option, Google+ did.
#Mastodon should be user and site/instance friendly, and provide this option. -L
@lauren That feels straightforward to add as a feature to the reference implementation.
Ugh... I'd do it, but (a) I'm already swamped on volunteer projects and (b) I've kinda sworn off Ruby on Rails as one of those "Adding more code in this language is harming future generations" infrastructures.
@mtomczak Ruby on Rails could be an American International horror movie title -- and for good reason.
@mtomczak Why do I suspect there's going to be pushback like: "Oh it should be up to individual instances to decide if they want to do denial of service attacks and include inappropriate images on posts! This is MASTODON!"