nostr needs:
- better login and key management for normies
- better data querying and aggregation for devs
working on it.
Discussion
π«‘
What is a better login ?
username and password for example, or login with other services (oauth)
I guess username and password is doable with the nip-49.
Signup: generate a private key, encrypt it with nip-49 and send it in an event with a d tag as your username.
Signin: query event with d tag as your username and decrypt the ncryptsec with your password.
This is how I would implement username + password login.
nice. that means you can't forget your password though, which is very unintuitive for many users.
In that case, the user can set up a backup. By example seed phrase, recovery question or nsec. Itβs no longer unintuitive because we already use this kind of recovery methods.
Bluesky fixes this π€π»
π₯π₯π₯
Also non bitcoin communities and content. Currently most apps have leaky experiences that nudge you into bitcoin content.
Anybody here wants to work on the data querying together?
I have a few things built using DBT(data build tool) for nostr analytics.
could you share your progress?
Sure, I'm gonna write a lengthier post later but essentially I have the following:
1- I vibe coded an event listener client that stores all events from a relay into a data warehouse. It needs some work still as I suspect it is dropping part of the events.
2 - using the data from the above I started a DBT project (which can become a community template) for getting basic analytics from nostr events in the warehouse. I.e. the follow list of an account, top reacted posts and other aggregations.
The idea was to use the data also to create an open source a few models. Such as: how to flag an account as a bot, or to build a social graph of an account.
This is the same data just plotted on my metabase instance. Just connecting all the dots.
Could you share what use cases you are thinking of when you mention "quering data"?
Could you share the use cases you have in mind for nostr querying?
many use cases:
- pagination
- aggregation (how many likes does this post have?)
- better filtering (show me all replies to me)
- trending posts
- web of trust stuff
querying nostr events feels like working with stone age technology and nobody seems to care enough to improve the relays. people have gotten used to painful development, wasted bandwidth, and client-side filtering. it's not normal.
What I'm working on addresses aggregation directly.
It's still a bit messy but I'm sure we can build an api layer on top of it and leverage bigquery for a lot of this.
https://github.com/FKrauss/dbt_nostream
What about better / smarter remote signers (aka bunkers)?
username & password or oauth, with password reset.
so whatβs the difference between a passkey and a code in my passwords app.
Your passkey is tied to a hardware property
I kinda built that:
https://github.com/coracle-social/burrow
Bad idea unless you're souping it up with enclaves or multisig bunkers.
nostr:nprofile1qqs8d3c64cayj8canmky0jap0c3fekjpzwsthdhx4cthd4my8c5u47spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhs3w8c9w
I would love to be able to have a way to create an account and keep my keys in an existing wallet I have on my phone anyway.
I concur. I figured it out after reading through the guides and attempted to make a guide for normies, but I must admit it's a bit too daunting for normies and boomers alike. If you want expansion, need a different option for them.
I will be the first to implement login with username/password once we have a proper solution.
Would 2fa of some sort make it any better
