jeremie

I picked XML for Jabber in 1998, and at that time I think it was the best choice :)

I’m one of the (independent) board members of Bluesky and I can say with confidence that I don’t have any of these concerns, everyone involved is deeply aligned to the PBC’s purpose of “To develop and drive large-scale adoption of technologies for open and decentralized public conversation.”

I am also on the Bluesky board, and while the original funding did come from Twitter (at Jack’s direction), the company has no control over Bluesky and it is 100% independent.

> I do deny it; or to be clear, I think it is a story that we've been conditioned to prefer over the others

Speaking personally, and perhaps it is indeed my conditioning, but at 25+ years of marriage I am living that beauty in 1 every day and I know without a doubt it has led me to my best possible life.

This should be v0.1 based on the actual utility of the spec, just because it's been incubated for so long doesn't magically make it useful.

DIDs are fundamentally antithetical to privacy and will only enable a deeper and more obscure level of tracking to all applications that use them. They were originally inspired for mapping public blockchain use-cases, but IMO personal identity and related keys should _never_ be put on a public chain, who thinks this could ever be a good idea or architecture?

All of the suggested "workarounds" to layer on privacy to DIDs are just lip service in the spec, there's zero technical requirements for an implementation.

I worry that DIDs based on this spec will be deeply harmful if widely deployed with the multiple layers of abstraction, required dependencies on massively complex things like JSON-LD, and abundance of implementation-time choices. It's such an easy "spec" to embrace and extend by big tech, it has no teeth to prevent tracking abuse and it should develop those as hard normative implementation MUSTs before v1.0 versus the non-normative "Privacy _Considerations_" it has now.

Identity is too important to have it done wrong.

I’d say that it feels like just yesterday, but it totally feels like decades ago :)

I’m very lucky to still be close with so may of the truly amazing individuals that helped build Jabber, and over the years deeply honored by all those that spoke to me about how it inspired them.

While at the surface it may seem like all of our efforts had little impact on the big “messaging silos”, I am most proud of how much Jabber/XMPP has made it easy for anyone to build/host/extend a messaging and presence service. Twenty years ago the concepts and architectures were opaque, now they’re commonplace.

Happy Birthday!

I'm a big believer in a (local/p2p) transport encryption mechanism /in addition to/ one for auth, and for it to be transparent to any UX... that's very much our goals for telehash v3 :)

I've been on both sides of dizzyd's interview process and highly respect it, he should be a mentor to other software engineering managers on how to improve their hiring practices.