lostcause

lostcause's avatar
lostcause
npub1khf5...md3q
I'm a tech enthusiast exploring the intersection of Nostr, AI, privacy, and crypto. Big on Linux, obsessed with open systems. In my downtime, I’m into photography, music making, and riding motorcycles — anything that gets me thinking or moving.
I’ve published a proposal for Nostr Community Conventions (NCCs). The idea is simple: NCCs are lightweight, Nostr-native conventions for client and ecosystem behaviour. Not protocol rules, not enforced standards. Just documented patterns that emerge, get copied, and evolve. Key points: - NCCs live on Nostr, not GitHub - Numbered like NIPs, but optional and non-authoritative - Authority comes from timestamps, signatures, and adoption - Anyone can propose improvements - Stewardship can be acknowledged, but community adoption still wins The first paper, NCC-00, defines how NCCs themselves are published, revised, and evolved using Nostr events. This is about making emerging norms legible, not creating a new gatekeeper. Feedback, forks, and competing approaches are expected. Will probably try to make a proof of concept client at some point.... Python maybe?? View Article →
image This started yesterday as a “could this even work?” idea. By today, it’s a running PeerTube → Nostr bridge. It pulls videos via the PeerTube API, falls back to RSS if needed, posts cleanly to Nostr, credits the original creator, and actually plays properly in most clients. It’s Dockerised, rate-limited, and just ticking along. AI didn’t magically build it for me. I still had to make the calls and change my mind a few times. But it absolutely collapsed the time between “rough idea” and “working thing”. Curious?
GitHub
GitHub - imattau/PeerTube2Nostr: PeerTube2Nostr publishes videos from PeerTube channels to Nostr. It pulls videos via the PeerTube API first, falls back to RSS if needed, and posts Nostr notes that credit the original creator and include MP4-first playback links with HLS fallback.
PeerTube2Nostr publishes videos from PeerTube channels to Nostr. It pulls videos via the PeerTube API first, falls back to RSS if needed, and posts...
 #nostr #peertube #buildinpublic #foss
Example JSON with PR-shaped tags { "kind": 30078, "created_at": 1734585600, "pubkey": "YOUR_PUBKEY_HERE", "tags": [ ["d", "nostr-proposal-kind"], ["title", "Nostr Proposal Kind: protocol-native proposal objects"], ["summary", "Introduce a replaceable, addressable kind to publish and revise protocol proposals on Nostr, enabling coherent indexing and discussion without implying authority."], ["status", "draft"], ["t", "proposal"], ["t", "governance"], ["t", "kind"], ["r", " https://github.com/nostr-protocol/nips"], ["relates-to", "kind:30000-39999"], ["client", "proposal-cli"] ], "content": "## Problem\n\nProtocol proposals are fragmented across repos and chats with no canonical on-protocol artefact.\n\n## Proposal\n\nDefine a replaceable, addressable proposal kind with explicit lifecycle metadata.\n\n## Scope\n\nCoordination artefact only. No approval or enforcement semantics.\n\n## Feedback requested\n\nLifecycle states, minimal tag set, and whether a dedicated kind is warranted." }
Who owns your followers? On most platforms, you don’t. You’re allowed to access them as long as the platform permits it. If your account is limited, removed, or the rules change, the relationship disappears overnight. On Nostr, followers are tied to your key, not an app. Change clients. Change relays. The social graph stays. That difference isn’t philosophical. It determines whether you’re building a relationship or renting one.
New from @0xxLostCausexx0 "不必说再见 (No Need to Say Goodbye)" Melancholy AI-made Mandopop. A digital love letter you were never meant to read. 🎵 💜 Zaps always welcome #suno #nostrmusic #aiartist #mandopop #0xxLostCausexx