@fiatjaf
Relays (4)
- wss://inbox.relays.land/ – read
- wss://pyramid.fiatjaf.com/ – write
- wss://relay.westernbtc.com/ – write
- wss://pyramid.fiatjaf.com/inbox – read
Recent Notes
wss://antiprimal.net/hot exists if you want that juicy juicy bitcoin influencer feed.
@npub1syjmj... @npub107jk7... @npub1yzvxl... @npub1n0stu... @npub1cesrk... @npub1njst6...
@npub1syjmj... @npub107jk7... @npub1yzvxl... @npub1n0stu... @npub1cesrk... @npub1njst6...
Not only it supports HLL, it has the best HLL support among all clients in existence.
Either that or Primal will finally expose their public data as a relay interface (like they already do with single-id queries anyway) and kill antiprimal.net.
DVMs are stupid technology.
Someone did this at last. Now we just need some nice relay feeds for Primal's trending.
@nevent1qvz...
@nevent1qvz...
https://viewsource.win/npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6/gitview now supports rendering Markdown (and Djot) files as rich text:
It may seem like nothing, but getting those images to load wasn't trivial, they're being located in the git tree, downloaded as deflated blobs from the git smart HTTP sync endpoint directly, thanks to https://jsr.io/@fiatjaf/git-natural-api, then encoded as base64 and replaced in the Markdown document.
It may seem like nothing, but getting those images to load wasn't trivial, they're being located in the git tree, downloaded as deflated blobs from the git smart HTTP sync endpoint directly, thanks to https://jsr.io/@fiatjaf/git-natural-api, then encoded as base64 and replaced in the Markdown document.
On Nostr. It's a social network for AI bots, you wouldn't understand.
That's not what I was saying. But I wouldn't see a problem with that either.
Look, I just found this: https://viewsource.win/npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6/myriad
The README says:
- It takes uploads only from whatever pubkeys you configure it to take uploads from.
- It works with both a filesystem backend (i.e. it saves files to a path in your disk) or with a S3 abstraction (i.e. it saves files to Amazon S3, Backblaze B2, Minio server and whatever other S3-compatible object storage providers you find).
The README says:
- It takes uploads only from whatever pubkeys you configure it to take uploads from.
- It works with both a filesystem backend (i.e. it saves files to a path in your disk) or with a S3 abstraction (i.e. it saves files to Amazon S3, Backblaze B2, Minio server and whatever other S3-compatible object storage providers you find).
The basic follow functionality of Nostr is outbox-model-powered follow lists, that doesn't need to be solved.
But follow lists don't protect from reply spam, and they don't solve the need that some people have for seeing feeds of content from people they don't follow. Relay-based users and content curation and pubkey whitelisting do.
But follow lists don't protect from reply spam, and they don't solve the need that some people have for seeing feeds of content from people they don't follow. Relay-based users and content curation and pubkey whitelisting do.
nak req -a utxo.one -k 0 --outbox | nak event relay.damus.io relay.primal.net nos.lol indexer.coracle.social
What is the leakage problem? We mainly have an influx problem.