They wanted a standards based approach. Which has its pros and cons. While offering a lot of flexibility it can take longer to complete a specifiction. A happy middle ground would have been to include nostr in their integrations and work together, which is one of the things I designed into DID. It just became very complex to work with and some tech debt crept in. Nostr could learn a lot from DID.
Hate is a strong word. They wanted to make a standards based approach with structured data to offer devs lots of possibilities. They just couldnt get it over the line. Tons of good ideas in there. Daniel seemed like an abrasive personality online, but I suspect he had a great sense of humour if you met him, in the end I felt a bit sorry for them. They should have integrated nostr, which was something I built into DID, that said we never made our own DID or easy for external systems to integrate. The main problem with their stack is that it's 10,000 pages of reading to understand it all and figure out where the land mines are, and route round. Only about 5 people have done that reading, which makes it hard to complete anything. If it had worked it could have been huge. A brave effort imho.
Enjoying neutral bot analysis of posts on the theme of edits. One of the good things about Nostr Open API is that anyone can do this. See table below.
It seems the main issue is framing things as a binary choice. In reality editing in the public square is a nuanced thing, and probably a good thing. Even better if you keep the old version, which seems to be what the community wants. Twitter does this for pro users, but users can have it for free on nostr. Great!
https://image.nostr.build/e72eada5b81754f6563bc9d9c2ae4fcd9fc2d23fb1cb7418d7145a0ddc23d256.jpg
What is needed is a domain name resolution system based on cryptographic proof instead of trust, allowing any two parties to interact directly without the need for a central authority.
The functionality of the Internet has come to rely almost exclusively on centralized authorities acting as trusted intermediaries to manage domain name resolution. While this system operates sufficiently for most purposes, it still suffers from the inherent weaknesses of a trust-based model.
Here we go again ... stahp attacking bitcoin. Stay humble and stack sats 🫂
nostr:nevent1qvzqqqqqqypzq5xeflpdskqvdq4swxj59793uvdzqzc9pzatjk3nhmcg2h0js8trqy2hwumn8ghj7erfw36x7tnsw43z7un9d3shjqpqmdamu967mj2slxpuhswf45p8ujmaah7737vclytnydqhdctgux7q9c40ps
"Open" was a pardigm shift. It was the word of the year in 2007, with Open ID, OAuth and many other technologies challenging the bit proprietary monopolies such as Microsoft. Open source, open protocols, open applications became popular. Although it began a bit before that on the web with Apache and the LAMP stack. LAMP was used to create facebook in 2 weeks. Things like Ruby came out and I think that was used in twitter. 20 years later, many have embraced "Open", but most users still prefer to use proprietary.
The new paradigm shift is about to hit us again. The Agentic paradigm. Agents are much more than virtual assitance. You will have all the same structures grow up. Agentic Source, Agentic Protocols, Agentic applications. They will have an intersection with Open but will treat Agents and AI as first-class. Just as the LAMP stack enabled facebook. The Agentic paradigm will enable combined tools to create whole new generations of software and software stacks. The next facebooks, googles, netflixes have yet to be created. It remains to be seen whether they will serve the users or serve big corporations.
#pubky is no more a threat to nostr than #bitcoin is a threat to mastodon. Many mastodon users percieve bitcoin to be a threat because they have not read about the technology. Same with #nostr
nostr:nevent1qvzqqqqqqypzprx6rk40kt0cmt69qpfnewnfkez6lgx27ufkudqmuxmx5t57t0wcqy2hwumn8ghj7erfw36x7tnsw43z7un9d3shjqpqug4la77jdczxgnevkt7a9r443t8d7lancrt4qc22q5sdkn4fxa5qdgnlal
Strange language isnt it? The web that spies on you is NOT called the "dark" web. The regular unspied upon web is called "dark". I recommend listening to Snowden's talks. He argues convincingly that they will remove privacy from the biggest parts of the web, or add KYC. And everything else will just be marked as suspicious. They'll come after that whether you've done something wrong or not.
In thoery, yes. In practice, no.
A relay is a web server, which offers specialized services. It's harder to run a relay than it is to run a web server. It's harder to maintain too.
Some will do it, but most will not. Indieweb had a dream of everyone running their own web server. I support it in principle, and I do so myself, but it just didnt take off, because people are lazy. After decades, a handful do it, but it's never going to become significant. Even the nostr relay network is heavily dependent on damus, which I think is a company.
So while they might not get everyone, that is never the goal. The goal is to get the vast majority. They will deal with the exceptions if they become a squeaky wheel.
Fun fact. 4 years ago, everyone was betting on Trump in fiatjaf's lightning powered prediction market. Except me. I bet on Biden, and cleaned them all out! The next day (Nov 7) the first code to nostr was Rage Committed. The rest is history! :D
nostr:nevent1qvzqqqqqqypzqwus4q6g66y00ycj6s8mre0akqsfz9fegwk7nt3uufqztyyk54neqy2hwumn8ghj7erfw36x7tnsw43z7un9d3shjqpqqavwye8jff5rzrmm5a99uye3fgmqc00rx7e4kqgu5pdf8pg4qtjsmrzsy6
Its been awful for a while. Though I've never heard a complaint about damus. People cant make their frist follow on many clients, so just leave. Other clients should follow your lead.
It's still hard to make your first follow on ditto. When you create a new user and try to follow someone it often doesnt. But if you go to another client, do it, and come back, it works. That said, overall, ditto is still by far my favourite client. I am #ditto only now.
For the DNS part it reuses the bittorrent mainline network, which is very clever. In retrospect it seems obvious, but no one thought of it until now. That has 20+ million nodes and 15 year track record. It is almost impossible to censor.
Why not go a step further and run decentralized dns with #pubkey
- #nostr is tens of nodes
- #bitcoin is thousands of nodes
- #pubky is million of nodes
It's incredibly easy.
When you look up google dot com, it takes you to a web site.
With #pubky you look up, not a domain name, but your public key aka your npub on nostr
And it takes you to your own website, that you choose and control.
Best of all this is secured by millions of nodes, so that there are no take downs, no gate keepers and censoring it requires taking down millions of nodes, but 100s more pop up in a second.
#pubky offers unique new possibilities to nostr
- ecosystem gets 100s more tools
- provides verifiable censorship resistance
- decentralized dns
- scaling technology
- use features, use cases, micro apps
All hidden from the user with a beautiful UX. User just gets more choice. Some devs dont want this of course. They may be putting their own needs ahead of the needs of the users, or the project.
nostr:nevent1qvzqqqqqqypzprx6rk40kt0cmt69qpfnewnfkez6lgx27ufkudqmuxmx5t57t0wcqy2hwumn8ghj7erfw36x7tnsw43z7un9d3shjqpq8q09zjjnku60n3zsrf543jrkftf2ykrku83hvepfrzc3dfp8ce5qtwrxyt
Yes, relays are web servers, so all the risks of running a web server apply to running a relay. Unfortunately, that does include the risk of jail. Decentralizing that risk, should be something that everyone welcomes.
I used an impartial bot to analyze the contents of Bit Karrot's post for propaganda content. You can check for yourself. In response:
Looks like the main issue here is a classic "either/or" fallacy—he’s stuck in a binary mindset, pushing ICANN as the only way while ignoring how decentralized options could actually complement it. It’s a bit of a troll move, framing things to look like a choice when, in reality, both systems have strengths worth combining.
https://chatgpt.com/g/g-dNdvcTUSc-proper-ganderhttps://image.nostr.build/84531e1f5d94a46876db5537afbc63b3a645997c9907d0c4c0971bcd960b27fe.jpg
Oddbean new post about login | logout
Notes by melvincarvalho | export