Föderation EN Do 24.10.2024 15:36:30 When will Mastodon support some basic html in posts? I really want to be to use strikethrough text sometimes. |
Föderation EN Do 24.10.2024 15:45:43 @artcollisions SERIOUSLY |
Föderation EN Do 24.10.2024 15:51:59 @artcollisions mainline stopped stripping rich formatting from toots for a while, but i'm afraid that to support entering it on mastodon is still going to mean running βglitch-socβ for the foreseeable future β because the lovely people of mastodon like @renchap or @trwnh are closing all requests of implementation of markdown or other rich formatting as duplicates of the github issue no. 23981 and mark thenβ¦ βnot plannedβ. perhaps if bluesky threatened to implement it like they implemented qts, we'd get some traction driven by FOMO. |
Föderation EN Do 24.10.2024 15:57:04 @mawhrin lol! The thing driving this engine is FOMO? This instance is hosted not by the admin (which I totally respect that decision), so we are at the whims of Big Mastodon lolsob |
Föderation EN Do 24.10.2024 16:02:05 @artcollisions i'm a bit sarcastic, but yes, i believe that FOMO is certainly one of the driving forces behind the feature set β it's obvious that years of users asking for things to be implemented, or even providing their own implementation to be included, was not enough. and don't get me wrong, i'm all for it β if i can't get something implemented for the right reason, i'm perfectly fine with it being implemented for fear of users moving to other services. whatever gets the job done. |
Föderation EN Do 24.10.2024 16:06:33 @mawhrin *sigh* Yeah. It just feels kind of backwards. |
Föderation EN Do 24.10.2024 17:04:54 @mawhrin @artcollisions @renchap "not planned" is github's flavour text for all manner of dispositions, including duplicates, which any issue other than 23981 would be. the only alternative is closing them as "completed", which is also misleading. it doesn't help anyone to have multiple issues open for the same thing. if you have something to discuss or suggest about rich text formatting then do it in that issue, instead of scattering the discussion in multiple places. also, not a chap, thanks |
Föderation EN Do 24.10.2024 21:20:52 @trwnh @artcollisions @renchap apologies, corrected. (still, just marking them duplicate would've been less misleading β no updates on the single open ticket, closing others as not planned, plus history of ignoring rich text for years including dropping a working pr, is bad optics.) |
Föderation EN Do 24.10.2024 22:15:53 @mawhrin @trwnh @artcollisions There might not have been good communication in the past on this topic, but this is still on the todolist. We merge more than 300 PRs every month with a very small team and cant be everywhere. |
Föderation EN Do 24.10.2024 22:16:48 @mawhrin @trwnh @artcollisions But as indicated in our latest dev update this is a topic that we have been investigating on and off for the last weeks/months, without a good way forward so far |
Föderation EN Do 24.10.2024 18:28:37 @artcollisions I second this emotion! |