https://blossom.westernbtc.com/3f672362aadc6e0a34f9319b1a8b4eb1f6e7d750b0faf4c443e55f67f8bdc74d.mp4
This is pretty huge! Nostr + MLS w/ nostr:nprofile1qqsvh300dvquh50l5t9et2257pxrsk5ndsdgdcdmnnxl9nc0f6l2ejcpp3mhxue69uhkyunz9e5k7qgdwaehxw309ahx7uewd3hkcqgcwaehxw309aex2mrp0yh8xmn0wf6zuum0vd5kzmqduer08 and nostr:nprofile1qqst0mtgkp3du662ztj3l4fgts0purksu5fgek5n4vgmg9gt2hkn9lqpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz72agcaj on bitcoin++ Insider Edition.
Full episode:
Let's re-build Dopplr!
I hope not, because I don't want Nostr comments to look like we're on X:
nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc FYI: https://swicg.github.io/activitypub-e2ee/mls
The absolute dream would be if the early proposals could eventually become interoperable across protocols (so we can bridge users and it doesn't matter where they are), before widely deployed. Not holding my breath, but one can dream.
I'm tempted to say yes only to fix my posts not being bridged to fedi anymore and then immediately quit again. 🫣
This is now part of NIP-21: https://github.com/nostr-protocol/nips/blob/master/21.md#linking-html-pages-to-nostr-entities
So if you render Nostr content somewhere on the Web, or you just want to link your Nostr identity on your personal website in a machine-readable way, then consider adding the respective link tags to your HTML markup.
(Personally, I still prefer adding 'type="application/json+nostr"' to the elements for maximum interoperability, but it's optional.)
I just made nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6's point about not requiring the type for him, by mistyping the content type in my own post. It's "application/nostr+json", of course.
This is now part of NIP-21: https://github.com/nostr-protocol/nips/blob/master/21.md#linking-html-pages-to-nostr-entities
So if you render Nostr content somewhere on the Web, or you just want to link your Nostr identity on your personal website in a machine-readable way, then consider adding the respective link tags to your HTML markup.
(Personally, I still prefer adding 'type="application/json+nostr"' to the elements for maximum interoperability, but it's optional.)
Both Meta and Automattic (WordPress) announced ActivityPub support before Elon purchased Twitter, and the fediverse had already seen multiple big waves of user influx at that point. Not even mentioning the countless papers written about it, or the many different implementations in existence by then. I think there were about 25K active servers/instances in late 2023.
It was Bluesky that grew massively after the Elon purchase.
Either way, the important takeaway is that large-scale adoption can only happen when you already have a healthy network running, and it has enough users on it to be interesting enough for newcomers to stay for longer. Posting exclusively to the networks you want to grow, instead of cross-posting to the networks you want to shrink, is the best way of creating that sustainable base.
Please share here as well then. Thank you. 🙏
No, I think multi-sig is overkill. Relays are places, sure, like you can hand over a newspaper on a town square.
You're not alone in thinking that: nostr:nevent1qgsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gppemhxue69uhkummn9ekx7mp0qqsqqqzk6ac2vkmm6kqjpc9ea7ph5pttfuvhdjr3ky07a6sntsvmptsteez6l nostr:npub1raustrrh5gjwt03zdj8syn9vmt2dwsv9t467m8c3gua636uxu89svgdees
Turns out relays are a great abstraction, infinitely flexible and easy to use and reason about. Relay feeds and other types of custom relay usage could be the thing that differentiates Nostr from all other Twitter clones and are vastly underexplored today.
One example that does one form of "curation" today is nostr:nevent1qqsw0dtkdzl4xt9y2g7u98dr38edq5uehnrpeuu3gm6vrysm6t8p5wgzyqalp33lewf5vdq847t6te0wvnags0gs0mu72kz8938tn24wlfze6cpafg2
Try also wss://algo.utxo.one, but we need more!
This has been on my mind since I asked that question, because extending my blog software with support for publications is still my goal. However, after observing and dabbling in Nostr dev and specs for about a year now, I'm more convinced than before that relays are the wrong abstraction for publications. I haven't engaged in more discussion yet, because I was both trying to solidify my understanding of why, as well as come up with and implement what I think is a decent event-based solution.
That said, I think relays could be useful for indexing/curating publications themselves (while users should also be able to index/curate them separate from relays). Either way, demo and article incoming (soon-ish).
Because freezing funds for a single address is not possible?
Not sure about you, but I prefer the ground I'm standing on not to be at the edge of an abyss.
The OP_RETURN "debate" of the bitcoin "community" is an excellent demonstration for why X is an abysmal neutral ground as a public square.
It's the other way around. If you want txs that are being mined today to stay out of the mempool, you're making life harder for new and smaller miners, and you're incentivizing profits outside of the open fee market.
Yes! The unwritten rules for taking photos of your road bike are: cranks parallel to the ground and gears in biggie smalls. 😅
nostr:npub1q3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnws6cd26p Any chance you could have a look for why my posts don't get published by mostr on fedi anymore? I'm sure there must be more accounts if it's happening with mine. Last published one (or at least the last one ending up on my instance) was in January this year...
(I'm broadcasting all my stuff to the mostr relay, so that's not it.)
Bitcoin will definitely die, because of a change in bitcoin core that doesn't change consensus rules!
One more death for https://bitcoindeaths.com
I meant a simple solution that actually works today and just switches discovery by user address from lnurlp to bolt12.
You can chase your name service holy grail regardless of that.