46 karma · joined November 2, 2021
It is hard to classify censorship as speech for a site that it is all about user-content.
"Edit: Account recovered. I used chromium to login (which I never do) and then back to Firefox"
How can google keep getting away with this? MS got into trouble with IE with much less.
Sure, but I don't see what this has to do with anything.
As for your perception, I don't care :) Keep it to yourself next time please. You too are being perceived in a certain way as well but telling you how would likely be against this site's rules.
Various tools and packages that attempted to generate accessible pdfs from LaTeX have existed for aeons, all of they had a common characteristic: they sucked. I am convinced that by this point everyone who cares about accessibility has moved to other formats (like HTML).
"HTML does not"
<aside> is "first class".
Not India?
So, at the end you are going to serve html at the browser.
You can do that with web1
LaTeX is almost never semantic. People are encountered to think only about the document presentation (mostly due to LaTeX's own failures).
As for footnotes being "first class". It's just a macro, nothing first-class about that when compared to HTML's solution.
There is lua-based LaTeX and js-based pdf. Just use html without JS.
"The fact that it's often preferable to rerender an HTML document as PDF, simply for readability, let alone archival, should speak volumes."
The fact that it's always preferable to export a LaTeX document as pdf...
And well, given the amount of people that use overleaf I would say that a lot of people (although writers instead of readers) consume LaTeX.
(Btw, you can compile html too, try printing it as ps/pdf document)
"Whilst that may still pass poorly-structured documents and result in poorly-formed output" - this by the way happens much more often with LaTeX compared to html in my experience.
I think that as long as they skip site-supplied css it should be kinda fine.
"Okay, glad we agree on reality."
We don't.
Twitter is accessible except "this nitter instance has been rate limited", and don't forget instagram...
As for beeper it seems to lack xmpp support (despite some of the services that they support using it internally). Although I will say that it looks cool.
"Yeah, because everyone moved to closed networks."
This is not how I remember it but let's agree to disagree :p
The main question remains though, what does irc3 offers over xmpp and matrix?
Your favorite curve is suddenly vulnerable? Use a library like libsodium which has a solid track record and will be updated to replace the default algorithm if there is a need.
I will take signal's "hacked together" e2ee implementation over openssl.
As for clients without omemo support, I did not have any issue so far.
But even if they didn't, there would be no reason not to move their public conversations to the protocol that they use for direct messages.