3316e3696de74d39...

On the first, you mean like personalized graphs? Graphs need to be hosted, could be a compelling premium option. On the second, Sanctum policy engine integration in the works, with self hosted signer.

A system that allows bots to DoS or drown out users with noise is censorship by other means Transparent WoT removes the developer skew, gives users the upper hand over bots Bxrd flock is ascendant

ELI5 / TLDR: CLINK gives you a permanent Lightning payment code (noffer1...) that works like a Bitcoin address, but smarter. Old way (LNURL, Lightning Addresses): Requires a web server, domain, SSL, public IP — very complicated setup. CLINK way: Everything happens over normal Nostr DMs. Just share one static string. Wallets and websites use that to fetch invoices. It also sends a payment receipt back so the website can react (success animation, unlock content, etc.) and you can attach extra data (SKU, order info, etc.). Try it by pasting this: noffer1qvqsyqjqvcurjdm9x5uxydrzvcer2wrp8q6x2ef58pnryv3c893ngen98qerwvmrxuunqde5vgcnvc35vg6nydpnxfjrgetzv4snwd3exsungwgprfmhxue69uhhxarjvee8jtnndphkx6ewdejhgam0wf4sqgrka4zlqr820wk9nkxsklfqfpy02vva0wtvzs8lkm7t424s5y75fc4vx4hj ... into https://pay.shockwallet.app As a receiver, you can include that string in a web link: https://pay.shockwallet.app/?noffer=noffer1qvqsyqjqvcurjdm9x5uxydrzvcer2wrp8q6x2ef58pnryv3c893ngen98qerwvmrxuunqde5vgcnvc35vg6nydpnxfjrgetzv4snwd3exsungwgprfmhxue69uhhxarjvee8jtnndphkx6ewdejhgam0wf4sqgrka4zlqr820wk9nkxsklfqfpy02vva0wtvzs8lkm7t424s5y75fc4vx4hj That's a fully static web site, and you'll get a success animation once paying the invoice. The node you're paying doesn't need any fancy networking setup. Bolt12 achieves some of this static payment code stuff through Tor-like onion messages, which are therefore slow and unreliable. It's also not web friendly, making its utility limited. Some might even say that it's retarded.

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 https://cdn.lightning.video/eb5b0f038fba733b50cec1c8b48eda08e3038365757841055bb0370f915e2e39/Y9JONozVR6.jpeg 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 https://cdn.lightning.video/eb5b0f038fba733b50cec1c8b48eda08e3038365757841055bb0370f915e2e39/nrpu2Yw4lg.jpeg **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. 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