cmd
cmd@proof0.work
npub1gg5u...ulq3
I build cool stuff on bitcoin and nostr.
is nostr a good place to crowd-source training data for an LLM?
Amethyst is getting really, really good.
(also mid journey is amazing)
Badges are great.
Verifying my Nostr Nests identity: EGTbQaipFehwiKUtArELuI3DY-9x2puUTYY_r5otwfs
Nostr Nests
Join this audio Space
It's fun watching nostr evolve. So many cool things being built.
Paid relays are cheap enough that you could easily zap newbies the funds needed to join them.
There's a cool circular economy happening here.
I like how nostr is slowly becoming tidal tech support.
What are the tiny icons below your PFP about (in Amethyst)?
The shitcoin spam is unrelenting.
I hope that nostr figures out a solution. Because twitter /discord / telegram are losing this battle.
Zaps are pretty cool.
Amethyst seems kind of buggy with threads. When I get tabbed in a thread, I can't see the thread or any context.
Just a lonely anecdote + bug report.
Anyone else having a similar issue?
There will be a time where an existing nip will have to be patched/fixed with a new version.
How does that work exactly? Would the patch be a new nip number?
nips.be is a great resource for finding discussion on proposed changes to nostr.
If you care about the future of this protocol, please check out the proposals and weigh in on them.
What is the scalability of NIP26? There seems to be a lack of discussion on this.
Should every delegated event publish ~100 bytes of duplicated metadata?
GitHub
nips/26.md at master · nostr-protocol/nips
Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.
Damn. Worth a cross-platform link to watch the 45m video.
https://twitter.com/JamesOKeefeIII/status/1627842304374439936?t=mzLSNyEjPKG5xD2xqGuvKw&s=19
Received my first shit-coin spam solicitarion in my DMs.
What is the solution? Block? Report?
I feel like we should all have this discussion sooner rather than later.
It would be cool to add a 'publish to nostr' button to twitter. Maybe using an extention?
NIP-26 needs to be improved. Tagging every event with a fat wad of metadata is not a great solution.
NIP-26 needs to be improved. Tagging *every* event with a fat wad of metadata is not a good solution.