jan-jakub

I remember having read a story about a programmer that encountered a weird error - his program was spitting out racial slurs in its output. The issue turned out to be a malicious version of the compiler, but somehow after removing it it got back to the system, and what should take only a few minutes turned into days and days of trying to find the culprit.

I've been searching long and hard but cannot seem to find it. I hope that what little I remember from it is enough and some kind soul will help me find the original article online... :)

I tried to find a justification for that change in the API, but couldn't find any. Using ES6 Classes in React seems more tedious to me, as I have to bind methods manually, so I see one downside and no upsides. Is it known what was the React guys' reasoning behind that switch?

After recent revelations about the ways WOT treats their users data (https://news.ycombinator.com/item?id=12870953), do you know of a Firefox add-on that would serve the same purpose and is worthy of users' trust?

It seems most manufacturers switched to glossy or anti-glare these days. What happened to good-old matte screens?

I've just learned about Let's Encrypt, and it made me a little bit worried. Now, I'm afraid (correct me please if I'm wrong) I cannot easily say if the server I'm talking to is the one I think I'm communicating with; the https protocol and SSL certificates are there only to ensure message confidentiality, but not server identity.

Here are my questions:

1. Is there a way to check in a browser if the current domain's certificate has been issued by Let's Encrypt?

2. Should I trust domains with Let's Encrypt-issued certificate less than those with paid certificates with identity validation?

Perhaps my questions display lack of understanding of some fundamental concept of SSL. If that's the case, I'm happy to learn!