Both sides are the same
Both sides are the same

Both sides are the same

You're viewing a single thread.
Is this referring to authoritarians on the left & right?
... what.
Edit: Wait, why are you spamming the same broken markdown? Is it seriously just because you think you're trolling people by pretending to be AI? That's... really dumb.
Horseshoe theory: far left & right look similar if far means authoritarian. Is OOP referring to that or a different kind of far?
If your client is broken, that's on you: it renders fine as <details> & <summary> elements on standard web browsers with the standard theme.
Follow the fediverse link in a web browser & weep at your broken client.
The heck does that have to do with web connectivity?
… what.
is vague & no one's a mindreader. Use better software.
and weep
My choice of client not fixing your off-spec markdown has nothing to do with... whatever the heck is going on there. Could you try maybe rewriting your copypasta to be slightly more intelligible?
Losses due to image of text lacking alternative such as link:
Maybe try something a little bit less "All your text is belong to us"? Because this just doesn't make sense. I genuinely do not understand what you are trying to say.
Nor does it address why you're spamming posts with it.
Accessibility, and no, your client is broken: it renders fine in the standard web browser indicating your client violates spec. 🤷
You can just go look up the spec, what you're posting doesn't adhere to that. That the web pages correct for it isn't the issue here, that's just someone correcting for user behavior with the parser, it's fairly common to do that. I don't actually care that much about it though, because mainly I'm trying to figure out how to batter and deep fry your word salad into something to do with "accessibility" and the irony is just painful.
Are you trying to say that... this should've been OCR'd automatically then linked to? That seems like serious overhead when we have such an awesome community of transcribers ( ❤️ u guys)
Why would some random post be the spec?
Rewriting :::spoiler to ::: spoiler doesn't seem to make a difference.
Are you... serious? It's not, it's just a reporting of it, If you would prefer this version of the same information, here you go. Go nuts, it's all the same thing. Why are you so hung up on this? Was your whole message really so meaningless to you that you're willing to abandon it in favor of being sidetracked about this formal grammar bs?
(rewriting ::: spoiler does make a difference to those of us with less user-proof clients, thank you for that!)
You seem hung up: as stated earlier, this renders correctly in standard web browser & clients following standards. If that markdown should work, then accommodating broken clients doesn't help pressure fixing them.