Do any client apps have support? Is the Bolt12 UX today still limited to the command line and QR codes?
I’m mostly interested in the UX side and progress so far.
#[3] do you think a lightning wallet UX for registering “upcoming payments” with tap to pay could work? No pull or direct debt payments.. 100% user control. Reminders to pay via notifications. Cancel by not paying.
Maybe churn would be too high.
Similar to this fiat bank.
An interesting idea could be a white label (hosted) relay service (SAAS) for businesses. Likely needs some company auth integration like oauth. Obviously backups. Likely AUTH for publishing. Can support custom relay.company.com. Maybe charge per user.
Centralising sure, but most businesses don’t suffer from censorship. Nostr could be used to host their blogs, or support docs, or semi-internal social network. Can aggregate targeted comments, reactions and whatever from the wider network for their company content.
Obviously a business would need enough value and perhaps support plans to feel comfortable to adopt.
There is a 5 missing at the end of the gist URL. Correct URL is: https://gist.github.com/blakejakopovic/f084749a912b9fcab60128ef9c6c98c5
Thanks. In Damus I still have a jumping around cursor issue when using autocomplete, adding links or splitting paragraphs.. so I delete accidentally 😄
Ok cool. I’ll gather some test cases so we can start sharing them.
Sometimes the NIPs can benefit from concrete “this should work” or “this should become that” examples.
I noticed the nostr-tools repo didn’t allow for an optional author/pubkey for nevent as an example.
Have an early rust NIP-19 TLV decoder written for rust. Needs more test cases and likely to simplify areas. Better TLV flexibility for ordering likely needed.
https://gist.github.com/blakejakopovic/f084749a912b9fcab60128ef9c6c98c
#[0] do we have more test cases somewhere I can use? How flexible should TLV order be?
https://github.com/nbd-wtf/nostr-tools/blob/24f5068fdbc2d3fce2f00af00ce2d01ea83fe40b/nip26.test.js
Anyone written a NIP-19 shareable identifier TLV parser in rust yet? I haven’t seen it in any Nostr crates yet.
May write something if nothing.
Maybe long press reaction button?
Yep. It was #[3]. He wants more dishwashers on Nostr ;)
It needs a stream processor added for inbound events, but I also added kind 10002 to the api. Most code written already, but needs review for kinds 2/3/nip05. Once data is solid for relays, it’s easier to build relay recommendation tools.
Something I did in the past, but is less clear now is a priority ranking or upgrade type when relays appear in multiple kinds. Previously I had nip05 as the highest. Now I’m unsure.
Example below.
I had time to refactor the Nostr Archive Bot to use a newer streaming event approach. Haven’t tested a lot.. but should work :)
Relays could send a DM to the pubkey with a captcha before accepting new events 🫠
Please don’t do this 😨
Yep. Nice suggestions around naming UX for newcomers.
NIP-05 -> Nostr Address
Relay -> Relay Networks
#[0] awesome live streaming work team.
PV ☀️
I mostly use it myself for looking up stuff adhoc without a SQL query. No plans to kill it, but it does rely on relay aggregation which has been a time consuming to maintain - mostly spam mitigation.
The seen by data only listens to relays and doesn’t crawl, so it’s most accurate closer to initial event broadcast time. And relay aggregation varies between 120-180 or so.
I don’t know if anyone else uses it for anything serious, but it does have rate limiting.
Otherwise I’ve seen two recent projects that do this client side and query 100+ relays to see if they have an event. I don’t have links sadly, but they exist.