When BlueSky was being designed I was involved in the developer discussions and continually urged them to make simple RSS be the least common denominator of their entire spec, and build on top of RSS rather than trying to replace RSS. They listened to a lot of what I said, including my "Repository" concept where every user basically has a big repository of IPFS content addressable elements, and incorporated that into their design, which I was glad to see, but BlueSky failed miserably on the "KISS" principle, because they made every detail super complicated. It could've been RSS-compatible, and that would've changed the world, and revived RSS, which is badly needed, but sadly they were unable to see the wisdom in that.
EDIT: And most of them (BlueSky devs) indeed were far left-leaning progressives who were much more concerned with censorship than freedom of information (this being around 2020 to 2022 Silicon Valley mindset), so they continually wanted to impose lock-downs and controls on the flow of information, rather than fostering principles of openness and freedom like what RSS is all about.
Yeah, I've written an ActivityPub implementation of my own. Very familiar with Mastodon too of course. RSS is such low hanging fruit and so obvious a thing to use as the basis for social media posts.
It really is amazing the difference that modern AQMs like FQ-CoDel make. This is a bit of self promotion but we leverage FQ-CoDel in our product (https://www.preseem.com) to help ISPs provide a better experience to their subscribers. Our customers regularly pass along anecdotes from subscribers who are very happy that they can now do big downloads or heavy streaming without breaking interactive applications like gaming.
Linux Journal recently went digital only but the quality and range of topics has remained good. Linux Journal covers most open source topics, it's not really limited to Linux.
Great article. I've been inaccurate in the blog saying that cache coherence will or should go away. What I mean is that ugly (non-scalable) effects of cache coherence as implemented by today's vendors can be relieved by Erlang VM to some degree. In the comment above [1] I say "It can also scale well if sniffing is not a broadcast". Your article is to the point by addressing exactly this issue with tracking of sharers.
https://bsky.app/profile/coverfire.com/feed/networking