https://pubky.tech/ 

 we should make a vanity pubky creator, you'll appreciate it in the long run! 

 It's very simple.  It gives you a new key pair that can also be a censorship-resistant domain.  But instead of 10s of relays, like with nostr, it reuses the 10+ million strong bittorrent network.  Obvious once you see it, but nobody saw it for a long time.  Now #pubkey has proved it's possible.   

 Click on the settings icon 

 Legend

https://www.youtube.com/watch?v=yAQq5WHVgTk 

 Deep state been doing it for ages.  It goes on on nostr too ... but can you spot it? 

 Good points, but I think you need also to SHOW that it's a open protocol.  And be transparent.  That is the only way to grow to a mid size protocol and bigger.  A new user needs to be able to come to the protocol and see in a few clicks how it's goverened, who controls it, what the licenses are and what the evolution is.  Developers will ask these questions.  Ubuntu is a good example of doing this. 

 "for me it's not what crypto is about," explained Buterin

lol 

 omg your secret is 1234 

 It's decentralized DNS that lets you use pubkeys as decentralized domains.  Should be right up your street. 

 That is quite a lot of work, but yes, it is the way to go. 

 If you build it into an open protocol and open eco system, in the same way Ubuntu did, with transparency and a good devX, developers will build things like this.  Easier said than done, but worth it in the long run. 

 It depends if you want to be able to on-board and retain developers (without paying them large sums).  This is hard, and doesnt happen by itself.  Most FOSS projects dont make it.  But put in the work and you will get results.  Quite old now, but still probably one of the best works on the subject.  Chapter 10 is on Governance.  Agree matrix is poor, there are worse.

https://www.jonobacon.com/wp-content/uploads/2019/01/jonobacon-art_of_community_second_edition.pdf 

 In its early days nostr was a simple 2 page spec that worked.  Develoeprs were attracted to it because they could go away in a weekend and build a relay or client.  It has got way more complex over time.  And what could come next (negentropy) is a complexity bomb that may shorten its runway.  Pubky talk about a "complexity budget" and they are careful to manage that.  It's a good approach, and learning lots of lessons.  I really hope there is a project where devs can build on simple concepts in a permissionless environment, and let 1000 flowers bloom.  It is much needed! 

 They looked at it, of course.  John had a pretty convincing set of reasons.  Ed25519 is far more widely deployed than taproot keypair.  And you need that interface with bittorrent mainline.  It's faster, works on low power devices, deterministic.  Schnorr nonces can be lattice attacked too, potentially.

Good news is that you can have both.  Sign a pubky field in your profile.  Then put your nostr pubkey in your DNS record and you have a two way link.  Think of it like NIP-05 for bittorrent mainline (20mm nodes).

This would give nostr clients that use this the full power of taproot and the full power of ed25519 (pubkey, git, tor, ssh, matrix, signal etc.).  It's way better.

https://github.com/melvincarvalho/noskey


https://image.nostr.build/c2ca7ae71b18b1c271a7dedd77d0f1fbc7a5120bd3594d182f9e76fb4f667763.jpg 

 Have a look at this link

https://ianix.com/pub/ed25519-deployment.html

 

 Have a look at pubky.  They do base32 encoding without the very complicated, and never used, segwit checksum.  Saves on code, bandwidth and complexity.  This would be a better npub that would be not only uniquely determined but pass the test of indepenent invention:

https://www.w3.org/DesignIssues/Evolution.html 

 I believe #pubky are working on rotation as a first-class use case.  Some good bits and some bad bits in NIP-41. I favour #subkeys right now.  Let's see how it develops, though. 

 It's dencentralized DNS using bittorrent network. 

 DB doesnt need to relay.  Relaying is expensive.  Just let a DB be a DB. 

 Yes and no.  They dont have a banking license, at least not all do. Which allows them to turn a load agreement into legal tender. 

 It's based on your pubkey.  So the owner of the pubkey sets the records.

The really smart thing is that they use 10 million bittorrent nodes to prevent any censorship.

https://app.pkarr.org/?pk=jtcseyeajzaw44txmn4ndy4hmpygzjgshucffcbsxyd9bcrmuumo 

 It's a two-step process.  You can do one without the other.  The more important part is the resolving, the less important part is the short name.

Think of it this way.  It's like building a file system.  Then adding sym links.  The file system is the more complex part, the sym link is the easier part, after we have working file system (there is a solution here but I'm stickin to a single topic here).

It's not just DHT.  DHT is for the censorship reistance.  It's a home server, which is fully powerful and scalable remote storage with micro apps.  The DNS part just does the resolving.

In fact names are easy to fix, the question is what if two keys want the same name, what tie breaker do you use.  That's a good problem to solve, and it's the next part of the two-part process. #pubky isnt confusing the first step with the second, which I think is a good approach. 

 they also use full DNS packets signed by your pubkey 

 The naming part is actually easy once everything else is there.

You just start off by using your npub as name.  The resolver is the powerful thing.  Then there are so many paths.

Nomen was going to be the great solution based in bitcoin, but fiatjaf and semisol wanted to kill it, and so it died.

What you need simply is a fair naming system that is a level playing field and with a wide eco system to ensure a small clique doesnt grab the good domains.  

namecoin got rekt and it didnt allow transfers, which was a glaring mistake.  ENS is very scammy and they raised the prices massively.  the fact that there is a "they" is also a problem.

The only solution to this is naming on bitcoin which is pretty a pretty much solved at this point, you would use an OP_RETURN UTXO runes or a soft-fork of runes with an OP_RETURN flag.  But let's see how it evolves.  Have a look at resource oriented computing on wiki for a more in-depth explanation.  But, the npub resolver alone is huge because it gives you decetralized domains and also SSH keys for free, which is a massive upgrade.

https://stacker.news/items/256435 

 forgot to say, also you could tie it into nip-05 too if you wanted 

 one last point is that it works out-of-the-box with nostr (and could/should with alby too)

click on settings -> paste seed, and it will generate you a pubky address from your nostr privkey

its actually an ed25519 key z32 encoded, which allows you to use, ssh, git, matrix, signal, gpg, hypercor, Tor, wireguard and much more, out of the box -- something we probably should have done on day 1 

 Yes, bridge to the older system.  Which isnt going away. 

 They are called home servers.  Anyone can run one.  You can run one in many mirrors.  Think of them like relays but with full storage.  In fact every relay can be a home server too. 

 relays are web servers, with the storage turned off

flick a switch and you can turn storage back on

you shouldnt store things in the RELAY, because it was just designed for text strings aka notes

but all web servers have the ability to store stuff, that is, in fact their primary purpose

a relay is a web server, with an extra function, namely realtime updates

tl;dr web servers can do many things, they can store files, they can relay notes.  But dont use the relay notes part to store files.  Use the built in file storage part to do that.  That could be a home server.  And then you can route to it via your npub.  But homeservers can live anywhere, they dont need to be a relay.  And perhaps it's too confusing for most people to run both. 

 It really is 

 I use obsidian.

#pubky adds a 10 million node censorship-resistant network 

 https://pubky.tech/ 

 I used to think so.  And I like the desktop client, though qbittorrent i prefer.  But are there any actual web clients for it, that are useful?  instant.io seemd a bit unmiantained. 

 It mostly doesnt work.  But there is one that does with a track record.  Namely bittorrent.  And #pubky worked out a way to use it for more than just torrents.  That is good thinking. 

 Use #pubky for decentralized domains 

 We are in unknown territory.  Definitely worth a try.   

 https://medium.com/@synonym_to/pkdns-a-dns-server-providing-self-sovereign-and-censorship-resistant-domain-names-4289f74bc098 

 Love nomen but unfortunately I dont think it is still developed. 

 I believe #pubky is the first solution that will work here 

 Main issue was that fiatjaf and semisol were against it.  So it had no real chance.  For a project to be successful you need everything to go right.  And with powerful people against you, it is likely to not a productive use of time.

To bring it back you would need to write and put online the indexer.  However the schema that is used to create the rules needs to be managed responsibility by someone who has the time.  That's another challenge.

What's good about #pubky is that its already a working system with millions of nodes.  So hard for it to fail.  There would need to be a tie-breaker system that ties names to pubkeys.  There's emerged new ecosystems for that now, namely runes, or my soft-fork #glyphs.  For me it just needs to be fair. 

 One thing that will always be needed is pubkey.nostr as a domain.  Because only one privkey controls, or can control, that record then getting a DNS doesnt matter too much where you get it from.  Pubky are making proper eco system for this including 10 million Mainline nodes, so it truly is censorship resistant, rather than the small nostr public relay network.  See also

https://dnstr.org/

Main problem is that it's hard to get anything at all through nostr right now.  So it's a dead end for most innovation.  Attaching names to a pubkey is a two step process because more than one one pubky can claim a short name, you need a tie-breaker.  But it's no good some small tie-breaker system that no one has heard of.  For it to be fair it has to be well publicized and a level playing field, with some cost to getting names.  Running a node and an indexer is one step (tho no one has done that right now) plus getting a good domain, then you have to publicize it, and then you need to ensure the rules are fair and stable.  It becomes such a huge task, and with people against it, very little chance of success.

As other solutions have emerged from other eco systems, it seems the path of least resistance to use them rather than to do it all yourself in an adversarial env. 

 So basically you're saying you can do 100 censorship resistant micro apps, based on off your npub?  This is next level stuff ... 

 Smart widgets still not merged! 

 I tried to do this with #songstr but needed to build other things first.   

 Take a look at #pubky it will allow (signed) git commits and remote pushes, including from the browser, when integrated with nostr. 

 It's native.  Pubky ids work with git out-of-the box. 

 Yes, me, its pretty lightweight and useful.  I give it to my bots too.