Did a little Nostr talk at a small bitcoin meetup with mostly non-technical users last night, as they asked for people to talk about stuff they're building with it.
The idea was for builders to talk about their projects. But instead, I had to give a general Nostr 101 talk, because only about a quarter of people had even heard about Nostr before, virtually nobody used it regularly, and there was also no other speaker present.
Observations:
* People who were aware of Nostr were also much more interested than the others. They mostly had the usual questions:
** What about spam?
** It feels like Nostr has lost all traction (following users who aren't posting anymore)
** Is it possible to get an endless stream of interesting posts? ("I'm used to doom-scrolling")
** How many relays are there?
** How difficult is it to run your own relay?
** What if one company (e.g., Primal) gets to "control Nostr" through market share?
* And a couple of new ones for me:
** Can I spam people's inboxes for profit (i.e. mine relays for user interests, then target users with DMs)?
** Has someone built a DEX order book on Nostr yet?
Generally speaking, Nostr was still perceived as social media only. Which makes sense, because the least experimental clients are focused on micro-blogging, of course. I did explain the Other Stuff, and also demo'd my blogging software, but the questions and interest were almost all about the social media use case.
Most of the evening felt a bit like talking about the fediverse in 2018 or so. Now you just point to Meta having a Fediverse timeline in Threads, and there's simply no question that the protocol is useful to enough people that a company of that size would add it to their product. It also went through the same waves of adoption, where people brought a lot of followers to the protocol, only to then stop posting and make the place feel empty for those followers. And with every wave of adoption, more people stay and make it more interesting for the next wave.
Râu Cao ⚡
raucao@kosmos.org
npub1raus...dees
Traveling full-time since 2010. Working on open-source software daily. Currently integrating Nostr features into Kosmos accounts.
@JeffG FYI:
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.
Messaging Layer Security in ActivityPub
This is now part of NIP-21:
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.)
View quoted note →
GitHub
nips/21.md at master · nostr-protocol/nips
Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.
The OP_RETURN "debate" of the bitcoin "community" is an excellent demonstration for why X is an abysmal neutral ground as a public square.
@Alex Gleason 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 

Bitcoin Is Dead
Bitcoin Is Dead - Track Every Bitcoin Obituary Since 2010
Bitcoin Is Dead tracks over 400 bitcoin obituaries since 2010. See how many times Bitcoin has been declared dead by critics and media, with the com...
Not sure if I did this right, but I'm accepting issues and PRs for the Nostr Links extension via Nostr now:
Original repo here:

GitWorkshop.dev
Decentralized github alternative over Nostr
Gitea
nostr-links
A web extension to discover Nostr links
Just a note on CI solutions:
For
we use Gitea Actions, which is compatible with GitHub Actions, like you describe.
It works nicely, and the configuration allows to configure both hosted and external runners per repo, user, or org. (Meaning you don't have to allow just any user to run arbitrary payloads on your infra, but you can allow only trusted or paying users to do it.)
Being compatible with GitHub Actions brings baggage, but also convenience and less migration work, of course.

Gitea
Gitea
Gitea (Git with a cup of tea) is a painless self-hosted Git service written in Go
Overview | Gitea Documentation
I also just added the link rel elements to my Atom feed. So if you have a feed reader with both RSS/Atom and Nostr support, and someone adds a URL for the former to your reader, it could now detect the Nostr alternative and offer the user to subscribe to that instead.
Also interesting if some of the feeds you're already subscribed to (maybe for much longer than Nostr even existed) started adding alternate Nostr links in the future, so we could slowly migrate to a more decentralized system.
Maybe something for noflux, @fiatjaf?
View quoted note →
Turns out that @fiatjaf fixed the issue with the commas a while ago. So if you just use the latest version of nak with this, then all is good. 🥳
View quoted note →