HN user

ttybird

46 karma
Posts0
Comments52
View on HN
No posts found.

I thought that the first amendment was about people rather than companies. In addition to that there are many products where companies have to display certain information, such as age rating for games, health warrnings on cigaretts, food content, allergy warning, nutrition labels, medicine side-effects, etc

It is hard to classify censorship as speech for a site that it is all about user-content.

One of the "open source" licenses that it is under is LGPL, you can do whatever you want with your code. (Although this does not mean that you should, please avoid publishing closed source software)

I hate this. If I know the password I should be able to log in to my account no matter what (unless if I have 2fa enabled). Sadly companies like Google and MS do not like this idea, they also often use the excuse that they can't verify you in order to mine your phone number.

"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.

"Note that any data can be transferred over HTTP(S), including, on occasion, either compiled or uncompiled LaTeX."

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.

To respond to your question: no. Not sure why you linked me the PDF 2 specification. PDF/UA is from 2012, and the ability to tag PDF files for accessibility is a thing since 2001 (with PDF 1.4).

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".

Is this why after all these years there is STILL no sane way to make accessible pdfs from LaTeX?

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.

I talked about the compilation aspect at https://news.ycombinator.com/item?id=29372937 In addition to that there are various checkers for html.

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...

Username checks out? Are people who compile markdown, org (or even LaTeX) via pandoc into html somehow "garbage coders"?

Don't make assumptions about me. A LaTeX document is also virtually never directly consumed by web browsers. In addition to that we are considering LaTeX for the web, not DVI, not PDF, not something else that you compile LaTeX into.

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)

"must"? A web4 browser would probably use a "runtime compiled" implementation.

"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 honestly don't see any advantage to LaTeX over html+svg+css+mathml+??? for any usecase. Everything that LaTeX does the things that I mentioned do better.

I don't really see the issue. It's not like some sort of deadly sin. If the users re-use passwords then that's on them.

Notes on Web3 5 years ago

Web 3.0 refers to the semantic web specifically, nothing to do with crypto. You are confusing it with "web3". And no, web 2.0 is not the semantic web.

"Okay, glad we agree on reality."

We don't.

Notes on Web3 5 years ago

The accessibility of public web is what web 3.0 is about however. With semantic web and stuff.

Twitter is accessible except "this nitter instance has been rate limited", and don't forget instagram...

"Master of none" includes crashing every few minutes, dropping messages, lacking critical features, etc.

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?

Solution: use a library for the e2ee, multiple clients and even the group that makes the standard could contribute. This is what matrix did. On the other hand Dino (xmpp) uses vala bindings for the official "libsignal-protocol-c".

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.

I responded to that in another message but yes, many people do. Either via direct messages or small private channels.

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.

I uninstalled irssi once my friends moved to newer and better protocols, so yeah, I will need to.