So you want to build a piece of high performance, deeply pipelined hardware, and write a device driver for it?
The hardest problem is usually: "How do I bring it to a clean stop?"
Get this right. Early.
I hear SW folks proposing "optimisations" to stop the pipeline 10ms faster at the expense of corrupting kernel memory when unexpected errors occur, and I hear HW folks asking "Why do you need to do that? Just reset it!"
@silverpill@steve Fair enough - but in that case I'd suggest linking to a description of the attacks, so that readers can judge the importance for themselves. It's very easy to overlook things like this if nobody's told you that they exist.
@silverpill@steve One suggestion: the content negotiation section should, IMHO, be phrased as a "MUST" level requirement, in the light of the attacks on Mastodon that were discovered at around the turn of the year. That is, senders MUST set the correct Content-Type, and receivers MUST reject any message without it set correctly.
@crepels Nice article! In particular, this is the best explanation I've seen yet of the "infinite signature recursion" problem, and the way around it.
I haven't tried to talk to Threads from my own toy implementation yet. I have a suspicion that the "instance actor" requirement is going to give me a headache.
Mid-40s techie living in #Ely, #Cambridgeshire, UK. Player of #Ingress, under the name "Wrongfellow" (and I've used this name elsewhere, too). #Dog and #cat lover. Drinker of #ale and #cider. Occasional #CAMRA and #beer #festival volunteer.This account is mainly used for random drunken wit and shitposting. If you're interested in my technical projects, you might prefer to follow my Hubzilla account: @fentiger