This is now part of NIP-21:

GitHub

nips/21.md at master · nostr-protocol/nips

Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.

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 →

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:

GitWorkshop.dev

Decentralized github alternative over Nostr

Original repo here:

Gitea

nostr-links

A web extension to discover Nostr links

Just a note on CI solutions: For

Gitea

Gitea

Gitea (Git with a cup of tea) is a painless self-hosted Git service written in Go

we use Gitea Actions, which is compatible with GitHub Actions, like you describe.

Overview | Gitea Documentation

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.

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 →

Here's the bash script I created for publishing NIP-23 content. Maybe it's useful to someone else: View article → I'm only aware of a single issue right now, which is that nak doesn't seem to like commas in tag content. Other than that, it works just fine for me.

This is a small thing, and the demo case is kind of silly (because there's an open-with-nostr button under the articles it's currently working for). Nevertheless, if you publish articles on the Web as well as on Nostr, would you consider adding this HTML element to your pages?

Linking to Nostr versions of Web content in a machine-readable way

A modest proposal for Web publishers and Nostr developers

Also, if you're working a Nostr client that renders previews for linked content of any kind, you might want to parse that element and adapt your UI for Web pages that tell you about Nostr versions of their content. Also please do let me know if you think I'm doing things wrong, or if you have any other kind of feedback. Thanks!