Alex Sci writes about software, web standards, and internet infrastructure, including RSS blogrolls, email security, UUID collisions, and EC2 pricing.
HN commenters engage with its RSS blogroll network and its discovery pages, and one links the aggregate feed to ask about update frequency.
Another quote from the article:
> Further, native apps can generate a unique self-signed certificate.
Just creating a certificate will not work, unless it's installed as root CA certificates in all browser trust-stores on the machine. And if the private key of the root CA is not secured correctly, one could MitM any websites. So at least you want it name constrained (https://datatracker.ietf.org/doc/html/rfc5280#section-4.2.1.10), but at least in Chrome until 2023 (v112) that did not work on root CA's (https://alexsci.com/blog/name-non-constraint/), so you had to add an intermediate CA and add the constrain there. Of course, you should also just throw away the key of the root CA.
I will admit I once added basic constrains in some project with a local root CA (2020-2022), but 'incorrectly' to the root CA, and did not test it in all browsers.
I've been doing this. Here's an example page: https://alexsci.com/rss-blogroll-network/discover/feed-41e7afd377ae70efdb4606c0d0603e6f/
I don't like counting the number of subscribers, that ends up surfacing things like major news websites, or the hacker news feed. But I've found the graph to be useful in finding recommendations.
This is cool!
Is the aggregate list supposed to update regularly?
https://alexsci.com/rss-blogroll-network/rss.xml
Just for you:
https://alexsci.com/rss-blogroll-network/blogrolls/br-8da940851a665bf7e2ba1a0682fc7fa7/