Fantasy Trailer - Sound On

Space Trailer - Sound On

Uptober is always exciting

I'm a fan of bitcoin core up to v29. Consider v30+ risky. But, whatever your disageements please dont encourage denial of service attacks on bitcoin nodes.

Theme tune from the 70s

Sound on

#mindstr what is the difference between Knots and Core?

nostr.rocks

A user-friendly Nostr client for exploring relay feeds

is now updated to the latest version of Jumble.

#mindstr explain the OP_RETURN debate. Personally I remain a fan of core (and knots) but this PR was merged too early, and is a (rare) mistake from the maintainers. Still time to target v31 and turn a lose-lose into a win-win. FOSS tends to work best when you listen to the community.

Quote Note your Monster 👹 #AIArt

"There does not have to be a “winning” protocol. We do not build a better open social web for everyone by fighting and arguing about protocol superiority. That is not how we achieve a better open social web." -- open letter to SWICG

GitHub

general/statements/2025-09-05-activitypub-and-atproto-discourse.md at master · swicg/general

General issue tracker for the group. Contribute to swicg/general development by creating an account on GitHub.

Up to 50 relays you may have missed 1. wss://relay.exit.pub/ 2. wss://a.nos.lol/ 3. wss://nostr.hifish.org/ 4. wss://relay.primal.net/ 5. wss://relay.chorus.community/ 6. wss://ftp.halifax.rwth-aachen.de/nostr 7. wss://nostr.stakey.net/ 8. wss://itanostr.space/ 9. wss://nostr.data.haus/ 10. wss://relay.primal.net/%20 11. wss://relay.degmods.com/ 12. wss://nostr.vulpem.com/ 13. wss://nos.lol/ 14. wss://relay.freeplace.nl/ 15. wss://relay.agora.social/ 16. wss://sendit.nosflare.com/ 17. wss://nostr.noones.com/ 18. wss://soloco.nl/ 19. wss://nostr.yael.at/ 20. wss://relay.nostromo.social/ 21. wss://nostr.sathoarder.com/ 22. wss://relay.orangepill.ovh/ 23. wss://45.135.180.104/ 24. wss://relay.noswhere.com/ 25. wss://nostr.oxtr.dev/ 26. wss://nostr.einundzwanzig.space/ 27. wss://relay.cypherflow.ai/ 28. wss://nostr.chaima.info/ 29. wss://relays.land/spatianostra 30. wss://relay.snort.social/ 31. wss://jskitty.cat/nostr 32. wss://relay.chakany/ 33. wss://nostr.21crypto.ch/ 34. wss://relay.letsfo.com/ 35. wss://relay.snort.social/relay.snort.social 36. wss://relay.snort.social/, 37. wss://orangepiller.org/ 38. wss://orangesync.tech/ 39. wss://nostr.azzamo.net/ 40. wss://ithurtswhenip.ee/ 41. wss://relay.fountain.fm/ 42. wss://relay.bullishbounty.com/ 43. wss://nostr.mom/ 44. wss://prl.plus/ 45. wss://nostr.petrkr.net/strfry 46. wss://relay.seq1.net/outbox 47. wss://nostr.satstralia.com/ 48. wss://multiplexer.huszonegy.world/ 49. wss://multiplexer.huszonegy.world/ 50. wss://relay.damus.io/

The Web's Missing Piece: How DID-Nostr Quietly Solves Social Portability

DEV Community

The Web's Missing Piece: How DID-Nostr Quietly Solves Social Portability

After decades of platform lock-in, the first truly portable social graph standard has arrived. It's...

FiNo – Decentralized file sharing via IPFS and Nostr https://www.reddit.com/r/nostr/comments/1muotds/fino_decentralized_file_sharing_via_ipfs_and_nostr/

GM

Study #taproot

Taproot | Technical Explanation

A technical explanation of the Bitcoin taproot upgrade and how it works.

Great presentation by Maxim at Honey Badger conference. Great to see the first 1000 smart contracts issued on bitcoin, and the first 200,000 users. Yes, it's mainly testnet, for now. But surely a bright future ahead for programmable bitcoin.

Definition: Agentic Web The Agentic Web is a distributed, interactive internet ecosystem in which autonomous software agents, often powered by large language models, act as autonomous intermediaries that persistently plan, coordinate, and execute goal-directed tasks. In this paradigm, web resources and services are agent-accessible, enabling continuous agent-to-agent interaction, dynamic information exchange, and value creation alongside traditional human-web interactions. View quoted note →

Good news! After a helpful discussion with the W3C Credentials Community Group, we’ve aligned on a verification method that works cleanly with did:nostr and the Verifiable Credentials stack: w3c-ccg/community#254 (comment) I’ve already patched the did:nostr draft to reflect this. What this unlocks 1. Production-ready reference implementations 2. Compatibility with the wider W3C Credentials ecosystem 3. A straightforward path to issuing industry-standard credentials (badges, awards, driver’s licences, etc.) over Nostr 4. The ability to sign and exchange JSON payloads between Nostr services (relays optional) It’s a nice step up in standards alignment and Nostr functionality. Many thanks to everyone who weighed in, feedback very welcome!