Is there some way to receive normal zaps to a cashu wallet?
Sirius
sirius@iris.to
npub1g53m...drvk
developing iris.to
When ZapGuy fake zap spam? I don't think many clients filter zappers.
This weird song got stuck in my head
"Warm Leatherette" live 6.23.06. Trent Reznor, Peter Murphy, Atticus Ross, Jeordie White.
Check out https://new.iris.to for a ReplyGuy-free Nostr experience. When logged in, it hides replies from people who are not in your social graph. You can display the hidden messages by clicking on the button underneath.
There's also "Adventure" feed for showing all notes from your social graph:
I have worked on it together with the Nestr "decentralized GitHub" team. Nestr frontend and Iris are built from the same codebase using build configuration options for different branding and features. You can easily extend the configuration to make your own branded version. Source code to be released soon™.
The client is based on NDK. Full SocialGraph up to 2nd degree is downloaded on first login, and thereon only missing follow lists are queried. I'll be experimenting with options to go beyond 2nd degree.
The graph is serialized and saved locally in a compressed format, which is much faster to load than it is to reconstruct the graph from Nostr events. My graph consisting of 260 follow lists and 23000 users is 3 MB on disk.
It's still very much work-in-progress and mostly tested on desktop Brave, but it's already my favorite way to browse Nostr.
I have worked on it together with the Nestr "decentralized GitHub" team. Nestr frontend and Iris are built from the same codebase using build configuration options for different branding and features. You can easily extend the configuration to make your own branded version. Source code to be released soon™.
The client is based on NDK. Full SocialGraph up to 2nd degree is downloaded on first login, and thereon only missing follow lists are queried. I'll be experimenting with options to go beyond 2nd degree.
The graph is serialized and saved locally in a compressed format, which is much faster to load than it is to reconstruct the graph from Nostr events. My graph consisting of 260 follow lists and 23000 users is 3 MB on disk.
It's still very much work-in-progress and mostly tested on desktop Brave, but it's already my favorite way to browse Nostr.
I wrote this in junior high school. The teacher didn't appreciate it, and I had to write a new one. 
For custom apps on nostr, instead of random event kinds like 33442, let's use descriptive and human-readable "f" tags (for "folder") such as "apps/market/item" and corresponding "d" tag "apps/market/item/[uuid]".
IrisDB uses tag-replaceable events of kind 30078.
"d" tag is the "file path", for example "groups/follows/somePublicKey" or "user/profile/name". You can update the content of the "file" with a new event that has the same tag.
"f" tag is the "directory path". "groups/follows" in this case. You can list all the "files" in the directory by querying relays with the "#f" tag filter. Strfry doesn't index this field, but some relays do.
Content field is the file content, can be any JSON serialized data.
If we did profile fields and follow lists this way, there would be no overwrite problem when you sign in to a new device that doesn't have your previous profile or follow list. If we did likes that way, unliking would be trivial.
When we create new Nostr apps or features, we don't need to come up with new obscure event kinds. D tag "apps/events/some-event-name/participants/some-public-key" is more descriptive than some random number that might still conflict with someone else's application.
I wanted to name it "treelike" instead of IrisDB in order to not sound overly complicated, but the npm package name was already taken.
- react app starter template: npm create iris@latest
GitHub
GitHub - irislib/treelike
Contribute to irislib/treelike development by creating an account on GitHub.
GitHub
GitHub - irislib/iris-docs
Contribute to irislib/iris-docs development by creating an account on GitHub.
Winter came back yesterday
