I saw this on HN and though “great I was just about to write this but now I don’t need to” - I have a legacy blog, a link blog and another thing I update which all produce RSS and I want to create one big feed of stuff I write, regardless of which platform I chose to put it on. Seems like I can use this for that.
The reader has to add every RSS feed. What if I as the producer of those feeds want to ship a combined feed so they don't have to do that extra work? Or what if I'm a curator of RSS feeds and want to release one combined "low-tech computer news" feed sourced from 100 smaller low-tech computer news feeds?
Shopify only went remote in March 2020, after being strongly anti-remote for a long time. You're right that they have leaned into 100% remote since the pandemic, however.
There were remote employees before (especially in Production Engineering and much of Support), but R&D was almost all in person.
(Source: I miss the productivity of the Elgin Street office ...)
Glad to see someone already posted this. I don't know how anyone writes something like "this is what Slovaks are like" and doesn't stop to think about their biases.
I originally thought maybe he was from Slovakia (I have occasionally made jokes or generalisations about Irish people, as I am one) -- but then the footnotes make it clear it's not self deprecation. It's just prejudice.
When I started on twitter, it had no hashtags, replies were public (because they weren't initially part of the protocol), no t.co, no embedded photo sharing, no geotagging. All of these features were added, and made popular, in third party clients before being added to Twitter. It was like a giant lab where the features could be tried by smaller groups who shared certain clients or norms and the popular ones wrapped into the "official" API eventually.
If the passwords were POSTed over and left on the heap, then they were vulnerable to being scooped up via Heartbleed, even if they are stored hashed in the database.
The protocol is, while the domain system isn't. But then, you could say that about IPv4 and IPv6 - you have to get your allocation from somewhere, and your LIR gets it from its RIR and your RIR gets it from IANA. As long as you're using publicaly addressable computers, the system is in some way centralised. (And that's probably okay).
Fedora are making a push along these lines, not so much pushing the need to go and do anything extra, but making it so that using modern Internet protocols like SIP and XMPP is as easy as running your own mail server (that is; not brain dead simple, but not particularly challenging).
Work in Fedora 19 has gone into making federation work out of the box - it's always existed for SIP and XMPP but generally required extra configuration because it was possible to run your own server yet still basically be beholden to a provider, which is very much not the default with SMTP.
(Of course, that's why SMTP is so horribly broken with regard to spam, so the pendulum swings both ways)
