Looks like I’m attending Adopting Bitcoin Arnhem after all. Big thanks to nostr:npub1d0csynrrxcynkcedktdzrdj6gnras2psg48mf46kxjazs8skrjgq9uzhlq for the ticket! See you tomorrow frens.
Have a great time!
We still have one more ticket up for grabs.
We have 2 tickets to Adopting Bitcoin available (tomorrow in Arnhem)
Free to anyone building on Nostr - just share your project below
We won't support signing in with npubs, to protect user privacy
We're adding a create account feature though
Issue closed. FYI, this signature flow will change in the coming days, but we will continue the use of npubs.
great feedback, thanks! issue raised: https://git.sigit.io/sig/it/issues/40
a machine could be hosting multiple relays, switching according to hostname
in general though the approach sounds good
Depends, the IP could just be a reverse proxy
With Nostr, thanks to projects like this, YOU can control your keys!
https://github.com/blackcoffeexbt/hardware-nostr-connect-device
Hi Karnage!
We would really love your advice / input
Could we send you the poc link at the end of the week, once we smooth the rough edges?
Actually we're not fedi-ready (yet) but when fedi (the app) is ready we'd like to include SIGit as a homescreen Mod
Be great to discuss how our client-centric design prevents anyone (including us) from spying on users
We'd love to!
See you there
Working on a free and open source document signing tool (PWA)
Nostr for network and identity, Blossom for storage (encrypted content)
Self hostable / fedi-ready
We have a functional PoC, but it needs a little design love..
Anyone available for a conversation?
#nostrdesign #soveng
nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc - should it be the created_at of the earliest found event, or should one instead scan only for NIP-03 timestamped events?
it wouldn't be available for "all profiles" if the latter.
Maybe a two pronged approach..
"First seen: "
"Confirmed:"
nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc - should it be the created_at of the earliest found event, or should one instead scan only for NIP-03 timestamped events?
#comingsoon