It's built on #[5]'s library, the most used Rust library for Nostr. I borrowed the web template from a few projects I admire 😃
LND. Using caddy instead of nginx for reverse proxy made a big difference for me.
yikes... I think I will stay on the boat
Has anyone developed a bot to post Github activity to Nostr?
PV, and looking forward to seeing nostriches in Uvita next weekend.
Anyone interested in fishing? #[0]
Nostr Dev Kit
This video (from 2011) describes the Decentralized Attribute-based Encryption that we can use for targeting messages (such as BTC bounties as #[0] mentioned) to badge holder criteria.
It DOES require a public setup parameter that is created in a trustless manner.
To safely implement this, we would need to decide to use block data from a specific future Bitcoin block and then we could implement the model AFTER that block has passed, using it for the public setup parameter.
Badge issuers would then be able to issue a key (can be public) to badge holders as part of the issuance process. All badge issuers need to use the same global setup parameter when generating it.
She describes it well: https://www.microsoft.com/en-us/research/video/decentralizing-attribute-based-encryption/
The authority needs to generate a key when the badges are assigned IIUC.
Maybe it's possible that it can be derived. I need to research more I think. It also might be simpler than pure ABE because badge holding is boolean vs a specific tier or type of a given badge.
https://github.com/fentec-project/gofe/blob/master/abe/ma-abe.go#L401
That is a super cool idea. Earn badges x, y, and z (badges that are invented and authorized by separate independent parties) to earn the bitcoin.
I think we’d need the badge creators to sign the attribute keys but maybe we can add that to badge onboarding.
There is also a technique called FROSTR that allows multisignature badge assignment.
E.g. If 3 of 5 specific people agree, person can get rewarded the badge.
I think it is interesting, especially once we apply something like ABE to message badge holders that meet certain criteria.
https://damus.io/note12jtw6evzsuwtsaw7cdf7fuda8fm7j3p3qrr9quxze9n54zkmf8xq058ks6
Also made a video that demonstrates using the rust-nostr reference implementations.
Nostr Connect Technical Deep Dive
#[0] #[1] #[2]
#[3] #[4] #[5]
#[6]
Know-ster is what I use due to descendancy from notes and nus-ter sounds uncomfortable
Know-ster
Now-ster
Gnaw-ster
Nu-ster
I pronounce it Know-ster because of the descendancy from “notes”
But Nu-ster, as in “other” also seems valid but I don’t like it because it sounds like the name of a rash.
Good Article on Nostr Badges: https://thebitcoinmanual.com/articles/nostr-badges/