Been working on some graph infrastructure for Nostr to enable more features in our Lightning suite, so I slopped together a general nostr client to test its performance and comprehensiveness vs. standard bearers like primal and to use in the Nosfabrica hackathon demo
Rather than connecting directly to relays, BXRD uses a shared graph so any user activity makes it more performant for all users. This graph also comes in handy for computing web-of-trust scores.
The architecture of BXRD also makes it useful for external linking, clean namespace links based on nymrank which work for opengraph cards and server side rendering without an intermediary service like njump
Also this allowed for web-push notifications for the PWA
CLINK wallet connections sync across devices via NIP78, and use your own nostr key to pair to your shockwallet
It's in a good enough state that it's now my primary nostr client, only thing missing of note is uploading rich media (todo: with Lightning.Video's forthcoming api v2).
DM's are there, just not the nip17 giftwrap nonsense, but i'll look at that more closely eventually...
DM's from outside the WoT show in a spam folder
Caveats:
Will get better as I keep using it and finding things I need/want, or send me reports if you use it. It may get bounced frequently as I deploy changes.
Supply chain not yet audited, this has been on a back-burner off and on for months so is using some older deps that could have unpatched vulns... but also nothing so new that there's a postInstall attack that no one has caught yet.
Content is only indexed if the author passes the WoT threshold, which is currently about 200k keys... so if you don't have an established nostr presence and want to use it let me know and I'll throw you a follow
Been working on some graph infrastructure for Nostr to enable more features in our Lightning suite, so I slopped together a general nostr client to test its performance and comprehensiveness vs. standard bearers like primal and to use in the Nosfabrica hackathon demo
Rather than connecting directly to relays, BXRD uses a shared graph so any user activity makes it more performant for all users. This graph also comes in handy for computing web-of-trust scores.
The architecture of BXRD also makes it useful for external linking, clean namespace links based on nymrank which work for opengraph cards and server side rendering without an intermediary service like njump
Also this allowed for web-push notifications for the PWA
CLINK wallet connections sync across devices via NIP78, and use your own nostr key to pair to your shockwallet
It's in a good enough state that it's now my primary nostr client, only thing missing of note is uploading rich media (todo: with Lightning.Video's forthcoming api v2).
DM's are there, just not the nip17 giftwrap nonsense, but i'll look at that more closely eventually...
DM's from outside the WoT show in a spam folder
Caveats:
Will get better as I keep using it and finding things I need/want, or send me reports if you use it. It may get bounced frequently as I deploy changes.
Supply chain not yet audited, this has been on a back-burner off and on for months so is using some older deps that could have unpatched vulns... but also nothing so new that there's a postInstall attack that no one has caught yet.
Content is only indexed if the author passes the WoT threshold, which is currently about 200k keys... so if you don't have an established nostr presence and want to use it let me know and I'll throw you a follow