😂🤣☠️L
We should start charging for those error responses. Right nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft
Must read. Libbitcoin recent CVE. https://milksad.info/disclosure.html#libbitcoin-vendor-response
The most normal thing is for people to fight over preferences on open protocols.
Create clear and fair standard of conduct and procedures for people to contribute to the NIPs and a lot of drama will be reduced.
But, don't kid yourselves as it will always be contentious and uncomfortable.
Take a hint form bitcoin, it's not perfect but it's still working.
Scramble Keypad menu fixes this ;)
Much before AI key listening there was just key listening. And also hidden cameras and tempest attacks.
That's why key scrambling for PINs is so important.
Don't use general purpose computers for bitcoin security. https://airgapcomputer.com
It's not thaaat inefficient.
Paid relays with more complete sets 😉
Just thinking out loud, what if normalized data, like time-series entries were notes. It's inefficient but extremely powerful.
Each note would have to reference the table name, and any other meta information. But then each data point is now a signed entry available to anyone for filtering/sorting.
Anyone could provide their own data to compete for that data point.
Consumers of that data set could then choose their sources, average their sources, etc...
This would changed the way data science, finance, etc... is done.
Think crowd sourced excel.
It's raining, extra sauna today.
nostr:npub1z8gdrdvdvd5y3ex3np3ewrfklf44da0pes8nwmafhgzfafv3yhhq5rju0y nostr:npub1chakany8dcz93clv4xgcudcvhnfhdyqutprq2yh72daydevv8zasmuhf02 you two should just report very HN article on your sites 😂 https://damus.io/note1s0tjtuvccvkr47nddsmhl4rg374mka8f9730pdnq6sfrmdvwe6aswwe968
No one ever asked permission to revolutionize.
#[3]
I think the way this bounty is stated is put is not the ideal. I think most people will read this and think we need a big website that is just like GitHub but using Nostr somehow. I think that is not what we should see (and hopefully that's not what #[1] wants either).
What I would want to see are multiple apps that can interoperate and are able to perform separate functions:
- browse code
- comment on code (referenced by a commit)
- create issues and comment on issues
- send patches
- comment on patches
And how these should be done? I am not sure, but here's what I have in mind:
- most of the comment things should probably be kind:1 events, I don't know, with some extra tags (so they could be interacted with from the normal "social" Nostr clients? or not?)
- code should probably be hosted by standalone dedicated git servers -- and there could be centralized providers offering these services but they should interoperate seamlessly between themselves and with standalone personal servers
- sending patches should probably be done using something like this approach by #[0]: http://git.jb55.com/git-nostr-tools/file/README.txt.html
#[2] has opened a discussion on this topic on the NIPs repository that could possibly be used to coordinate the efforts: https://github.com/nostr-protocol/nips/pull/223
I think we could have multiple different smallish webapps, native apps and specially command-line tools that implement one or multiple of the separate functions described above, and with that we can achieve a much better result both in terms of quality and of decentralization than if someone or some big team decides to tackle the entire cake and come up with some centralizing architecture on their own.
#[3], I know you may not pigeonhole the offer. But you might want to spec it out a bit, ppl get scared of very open ended projects.
Feel free to make PR or reply here and we can update the site https://github.com/coinkite/bountsr.org.pub/blob/main/2023-01-19-nostr-based-github.md