Conversation

Notices

1. Embed this notice
   Polychrome :blabcat: (polychrome@poly.cybre.city)'s status on Wednesday, 29-Nov-2023 23:04:24 JST Polychrome :blabcat:
   @matthieu_xyz Bluesky and Threads are an incompatible example because they are a monolithic system, something the fediverse is not.
   
   The crux of my argument was that the network cannot be expected to fully support the feature that would only exist in one server software, especially given how there is no formal standard past ActivityPub to follow on these things to be considered "well behaved".
   
   Since you've mentioned that you do not mind having only a small part of the network supporting this feature then opening a feature request at your relevant software provider - in your case, Mastodon - is the way to go: https://github.com/mastodon/mastodon/issues
   
   Unfortunately with over 3.6k open issues I wouldn't hold my breath so I'd look into one of the faster moving server options, e.g. Firefish, as they are more open to feature suggestions at the moment.
   • Embed this notice
     Polychrome :blabcat: (polychrome@poly.cybre.city)'s status on Thursday, 30-Nov-2023 00:18:14 JST Polychrome :blabcat:

     in reply to

     • schultzter :mstdnca:
     @schultzter @matthieu_xyz that's not really an option for most people, so.
   • Embed this notice
     schultzter :mstdnca: (schultzter@mstdn.ca)'s status on Thursday, 30-Nov-2023 00:18:18 JST schultzter :mstdnca:

     in reply to

     @Polychrome @matthieu_xyz or you know, code it yourself and submit a pull request! Something you can't do with either #Threads or #Bluesky (in full transparency I'm going to add #hypocrit because the only PRs I've ever submitted are for documentation - though I'm pretty sure #Lovelace would personally break my fingers if I ever attempted to unleash any of my code on the internet)