Oddbean

> Mainline DHT + DNS Parser + HTTP Client. Yes. You told me, but I want to know EXACTLY how you integrate them all. I want to know all of the encodings so that if I code another implementation, your implementation must be able to see and parse my records. At this point, there is no value proposion. It's just a bunch of jargon that doesn't clarify why this is better than other DHT-based approaches out there. As you probably know.... Many people have offered solutions in this space and ALL of them fail to deliver an actual decentralized DNS system. In fact, all of them just pitch a re-centralization on themselves via a web of new confusing nomenclatures. Which your proposal seems to do as well. I am giving you the benefit of the doubt, but the more I hear, the more I think you don't actually have anything actually decentralized. I am also surprised to see how difficult getting information on this proposal has been. It almost looks like you don't want people using your thing.

I don't need you to give me the benefit of the doubt. You are welcome to call me full of shit. you are however just wrong on both accounts. 1. All the details of how pkarr works is documented exactly where I said they are, go to pkarr.org and open the design directory, if what is there is not enough to build your own implementation and interop, I would be surprised but happy to patch that. 2. Pkarr is decentralised, TODAY. It is not a matter of opinion, it is just a fact. There is nothing in hell anyone can do to censor you, and if I published something on a mainline, ther is nothing anyone can do to stop you from resolving my information. If synonym as a company disappeared today and all our infra died, Pkarr won't stop working. It might be hard to get enough documentation about the overall Pubky narrative and vision, but Pkarr is not only clear as hell, at least two external teams adopted it and built on top of it without much help from us and not even for the same purpose we are using it for. Pkarr works and it is censorship resistant, this is a falsifiable claim. You are free to not care to read until you are convinced, but if you want to prove that it doesn't work as claimed, go for it. The reason I am being aggressive here is because Pkarr was purposefully minimalist and I resisted so many proposals and requests to add complexity, and it has been praised by many for being so minimal and straightforward. So your claim that I am adding a web of new confusing concepts is just weird as he'll:) all due respect of course 😄

This Markdown is all you need to implement your own Pkarr client and publish or resolve any Pkarr packet https://github.com/pubky/pkarr/blob/main/design/base.md If you have a Mainline client that supports BEP0044 and this markdown didn't help you publish and resolve to and from our implementation, I will publicly apologise and fix what is missing