I'm thinking about extraction of relay data into different databases for different purposes.

I'm not a DBA. I'd love to hear what smarter folks think.

I can see use for -

Some sql for some basic storage and caching and BI/data vis.

Some graph db for some lookups or graph vis on social networks or on tags posts.

Some vector db to train some AIs on the network.

I have the feeling that basic relay dbs today are not useful for these purposes as their focus is relaying.

But I wonder if that is just a totally acceptable separation of concerns.

E.g. let relays focus on relaying and add whatever other db you need for whatever other purposes you have.

Then I wonder how to make existing relays interop with other dbs for other purposes. Some kind of standard? IDK.

What do our smart scaling heads think? Am I right or wrong track?

Trying to understand the why and wiifm of running, and querying only your own personal relay.

How many of these are real?

1. Save/backup your own posts

2. Cut spam (WoT protection)

3. Save bandwidth in your client device (fewer concurrent connections)

4. Protect privacy (not leak IP address to untrusted public relays, not leak NIP-04 messages)

5. ...

What have I missed?

Spent some happy scrolling time here just now. Seems to be picking up a little.

Very nice, esp vs Twitter

GM coffee. Very interested in your NFC card + nsecbunker login that you mentioned.

Applause 👏 nostr:nprofile1qqsw9n8heusyq0el9f99tveg7r0rhcu9tznatuekxt764m78ymqu36cpz4mhxue69uhhyetvv9ujuat50phjummwv5hszymhwden5te0wahhgtn4w3ux7tn0dejj7qg4waehxw309an8yetwwvh82arcduhx7mn99uuwx66a

Posted only to my own outbox. Relays blasted it to many other relays. CTO of project likes post immediately and I see the logs in VS even before I get a ping.

I may have just fixed the web of trust in my Haven relay... Just a test.

Will the design system be a public release? I've loved every bit of it so far.

I would love to learn more

I'm not forgetting, I'm just ignorant!

Backlog and batch sign?

Doing signing on the card was the first place I looked. I found secp256k1 seemed poorly supported on yubi and other platforms. Maybe wrong.

Also, NFC cards are very cheap.

Thinking of ways to get 100's and 1,000's of users onboarded cheaply without them being able to stuff up and leak their keys.

If I am a user who want to access a team or community relay (e.g. Team Relay or Ditto), that relay is going to look for my npub to be defined in the domain's well-known, but I don't think they also need to find a corroborating event on the network. And if not, then that's interesting and is slightly different from the way NIP-05 seems to be assumed to work.

I think I just worked out a new signing workflow.

We can approximate an offline signer using an NFC card that holds an nsec.

Design a nsecbunker, and delegate signing to the bunker, but populate the bunker with a transient nsec, similar to Amethyst transient login.

Client asks bunker for signature. Bunker requests NFC tap in order to get the nsec. On tap, bunker applies the password, signs the event, and then forgets the nsec.

Required to trust the bunker software, but if the bunker gets hacked, or device gets compromised, it does not possess the key.

Thoughts?

Multiple NIP-05s. Inevitable? Valuable? But not part of the standard at present?

My Nostr profile discloses that my NIP-05 is rb@rodbishop.nz.

rodbishop.nz/.well-known/nostr.json agrees with this, and says that my npub is associated with my username.

But many other domains may also make alike claims, and may give certain accesses to me if I am defined in their domain's well-known (whether or not my profile discloses it).

e.g. Ditto will give me access to the community, Teams Relay will give me access to the relay.

I may need all of these (to be me as an individual and also a community member and also a team member).

Is this a desirable use of well-known?

It seems needed for a user to be able to understand and manage where well-known associations exist, beyond just displaying a single NIP-05 field in the profile.

I feel like Nostr would benefit from a simple account management UX. Perhaps an "account manager app".

Amber, nsecapp, nsecbunker, browser plugins etc works from a tech pov, but I am less sure about a user POV (sample of one).

Testing Amber

I got this set up! Log into Amethyst with an encrypted nsec saved on an NFC card. Very future, much wow!

nostr:nevent1qqstx0jy5jvzgh7wr6entjuw7h58d7mapupfdpt9hkf7s4gze34a0vspypmhxue69uhhyetvv9ujuun0v33xjumgdaczumn69ac8y6tkv96x2q3q6lrdq99ng2q4hg5ufre5f8j0qpealp8544vq4ctn2wqyrf4tk6uqxpqqqqqqzur0pr0

Who is building this?

Have you tried the Phoenixd backend? Auto liquidity is a huge time saver

If I can talk to AIs now, then I should be able to shop for things by simply stating what I want. The AI should find it for me, charge me for it, ship it to me.

Typing details into forms is going to feel very dated.

Does anyone know of a social platform which supports AIs, and also knows all my details, and also supports rich media content, classifieds, marketplaces, and also has integrated payments rails?

Oh, hi #nostr

Half completed this form thinking you meant Nostr signer, but from the content of the form you may mean Bitcoin signer. Perhaps both?