ok

It's time to admit it.

https://bitcoinmagazine.com/takes/bip-21qonly-2-1-quadrillion-bitcoins

Pubky Public Dev Call

Wednesday (tomorrow)

1pm EST / 10am PT / 7pm CET

LIVE DEMOS!

1. Pubky TLS Support, with Ar

2. Public Key Domains (PKDNS), with Sev

3. Pubky Ring auth app, with Corey

…And more!

Google Meeting:

https://meet.google.com/xrv-ormm-kmt

Zzz

bitcoinerrorlog on telegram

Synonym his hiring.

If you're an exceptional senior developer or senior professional with directly relevant experience in Bitcoin, P2P web tech, or the success of related applications & products, contact me directly.

Otherwise, we'll be posting a new specific role each month!

https://music.youtube.com/watch?v=F3BH51jpBUs&si=XBxHgBTgk70RUyOp

nostr:npub1p23eukh0nxsqpfaakz6fj9vvj27y4gs0kevnrffdq4d4adkl7uuq7crnl6 here's more of that DHT info I promised.

nostr:npub185h9z5yxn8uc7retm0n6gkm88358lejzparxms5kmy9epr236k2qcswrdp some counters to your DHT concerns from our conversation last Spring.

They cover this a bit in the interview, but generally Nostr devs don't like PKARR/Mainline because you can't use secp keys to do this.

Since we have to bootstrap it ourselves, it gives us the freedom to design things in a more elegant way, so we have our own homerservers (instead of relays), our own separated indexer and graph concepts, and soon, our own app to demonstrate most popular publishing and social use cases.

You need to fall in love with Mainline DHT and Synonym is going to show you why & how.

Start with this article/research by Severin on DHT censorship-resistance and numbers.

https://medium.com/pubky/mainline-dht-censorship-explained-b62763db39cb/

Check out this new interview with nostr:npub1jvxvaufrwtwj79s90n79fuxmm9pntk94rd8zwderdvqv4dcclnvs9s7yqz, a dedicated Synonym engineer responsible for Pubky Core.

He goes into lots of detail about the pragmatic thinking behind Pubky's design, and of course, Nostr comparisons.

I'm also very proud to see more of the team branching out and doing interviews.

The Synonym team is going to be turning heads in 2025!

https://fountain.fm/episode/HXQpcOdQU9Tnxa9BQO2v

So far, Nostr elders do not seem interested in bridging or breaking the key model, but yes, any platform or protocol could use the pkarr method, and it would almost certainly improve censorship resistance.

My guess is that, once you do something like that, people will just find it easier to use Pubky keys/apps/servers, as they will have all the tools needed to make it easy to maintain your dht records, swap servers when needed, etc, and bridging doesnt seem to usually be a popular feature to maintain.

This image depicts sample distribution of the millions of Mainline DHT nodes that are Pubky-compatible.

What do you think this map would look like for Nostr relays? What do you think it will look like in 5 years?

In the end, I recommend you to use the best tool for whatever problems you are trying to solve, and that can be different for everyone.

There is no Pubky social app (yet).

You are not a trader, you are a fool.

I hope it was informative, let us know any feedback!

Tomorrow:

The 1st Pubky Community Call

- Architecture Overview & Updates

- Q1 Roadmap

- Feedback / Q&A

Contact me or nostr:npub17lgcwcpjax0mqnk85e6tcgnn4ae95t6uvg80wuvjg9qhtzwu4uxqcap267 for an invite.

Let's build the next web.

Synonym was founded roughly 4.5 years ago, before Nostr existed, with a vision & designs for a (bitcoin) key-based identity solution, which we openly shared with many (some nostr) people, including interesting ways you could make use & make something like (nostr) this way. (Keybase was also before many of us fwiw)

Decentralized, key-based web & identity solutions have always been part of Synonym's "atomic economy" ecosystem vision.

(...Side note: some aspects of the upcoming Pubky App, related to Semantic Social Graphs, social tagging, being your own algorithm, etc, come from designs I have had for more than 12(?) years...)

At first, we attempted to map this vision & requirements onto the Hypercore(Holepunch/Pear) system. Synonym had just become part of the Tether & Bitfinex family, and the hyper features and demos were amazing. That project was called Slashtags, and while we demonstrated more interesting use cases, people were already opting to make similar features within Nostr apps, which had some nice attention-grabbing events and gaining big momentum, while we were still doing R&D and realizing that Hypercore was overkill for our actual requirements, and this was also when Synonym started enforcing a policy of not having experimental (non-production-ready) dependencies from external teams.

If it is risky and novel, we need to be the ones building it. Nothing else is good enough... (until it is obviously good enough, in production.)

We eventually clarified our identity & web requirements and began new research on the simplest way to achieve our goals and design.

We entirely archived Slashtags as a project, which had trademark issues anyway, and began specifying, and building what is now Pubky Core, along with the upcoming Pubky App.

This work includes PKARR and the concept of using Mainline DHT as the primary routing network for self-sovereign keys as domains.

This work was also shared openly and directly with Nostr people roughly a year ago, but was rejected then, and also newly rejected directly when we formally released everything in Pubky Core recently.

These releases and plans represent major milestones in a long-term vision and plan for Synonym to create our vision for a minimum set of software and services for people to opt out of dependency on Big Banks, Big Tech, and Big States.

The Atomic Economy is an actual vision and plan for a functional independent digital ecosystem, economy, and society. Yeah, it's crazy, overly ambitious, naive, etc, but we have been given this opportunity and you can be damned sure I will make the most of it.

Sometimes we have had to mutate and discard our research, but it has made our team and public releases much better for having the experience.

So, we offer Pubky as the next major puzzle piece in our vision, and really the most important part, but we have so much more work to do, and so many more ways we intend to demonstrate the elegance and power of being so selective with our designs.

Stay tuned to see how well we do, or enjoy ignore us and enjoy Nostr and its current path! Or, get your hands dirty and consider trying getting your own key domain working, and consider what you can build from there! ;)

nostr:note1qx5uqnzz7l0pdaprpxsvqw4t4ssqkjwcs3nwmpm95jmm0rxtpv9qjac4fs

Everything that is usable so far is here: github.com/pubky/

All MIT licensed, yes.