@feld @hj @i @lain @phnt @silverpill @sun @vii > Should it be default?
The default should maximize compatibility.
> Maybe, but it's ugly as hell
Subjective; the guts don't look ugly to some people (and, as evidenced by bopesox users' inability to realize who's tagged because that's hidden, some details are unavoidable ugliness).
But this should be something you do on the frontend, not the backend: you can hide it using CSS if the code is aware of it, and then code that isn't aware of it will see the URL instead of being randomly tagged and someone says "This is a great idea" and then you say "What is?" and they say "That thing you said!" and then if you are aware of how these things are structured, you might eventually put together that they have quoteposted. (Don't get me wrong, I don't mind the learning curve acting as a threshold and I also don't mind when Shit Gets Weird because it keeps fedi intriguing, but I think it's safe to say that your goals are mutually exclusive with those two things, like, I don't want to put words in your mouth but I think it's safe to say that most of the Pleroma devs are not trying to make fedi opaque and weird and are generally trying for the opposite.)
Like, the tag-lists being abridged can be altered in the frontend per-user, but if it were set by the originating server and the post body changed to "... +5 others" then that would be a presentation-level concern that was implemented on the backend and that you couldn't fix without rewriting messages on the backend, and that feels wrong. I don't think quote-posting is materially different: it's presentation. If it were metadata and you expected a sufficiently clever frontend to replace it inline, you could have commentary before or after or around the link(s).