Avatar
franzap
726a1e261cc6474674e8285e3951b3bb139be9a773d1acf49dc868db861a1c11
Building nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 and #purplestack | BA 🇦🇷

🚀 bun-relay 0.1.0 released

- Finally supports subscriptions

- Added indices

Simple relay with NIP-50 full-text search written in Bun + SQLite (also acts as a basic Blossom server)

https://github.com/zapstore/bun-relay

We need web-of-trust aware LLMs

Next zap.store release won't support logging in - but the following will.

No plans to enable log in with nsec. Amber first, bunker later.

GM!

📣 Zapthreads release 0.5.2

Smarter URL handling, relay error reporting, small bugfixes, update to latest nostr-tools

https://zapthreads.dev/

https://www.npmjs.com/package/zapthreads

Replying to Avatar franzap

nostr:npub12358n500vfnf9j522nueg05k9yvhh97936smfgat6mledzegp5yskzrjdj can you give me an example of articles that *did* have comments before? Can't seem to find any

only looking in wss://21ideas.nostr1.com/

First thing that comes to mind is the trailing slash fix. I will check the r tags of your root events

Peer review is a fiat circlejerk

Maybe censorship resistance is a major selling point for nostr after all

nostr:note14rskfu639rsup3rvd5f9s7dgxc6jwghgqsy4qf5hqtvp83xq7xvsq2m34l

Relay based communities add connection overhead and not everyone can run one, is that a fair assessment? nostr:npub1lunaq893u4hmtpvqxpk8hfmtkqmm7ggutdtnc4hyuux2skr4ttcqr827lj nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q

nostr:note1hev83dx6vrju5px8zv7886h59fgdfqxgnagqyajyts2a9g8thgyq073t9f

what's the issue with data portability in relay-based communities?

You're calling Niel and Stuart fools? Just checking