Iris subscriptions live. You get relay and file hosting (blossom), but most of all you get to support open source Nostr development.
The line to nostr:npub1gdu7w6l6w65qhrdeaf6eyywepwe7v7ezqtugsrxy7hl7ypjsvxksd76nak book signing
Vegas people. Let's go shoot exploding zombies with a Barrett rifle? https://progunvegas.com/experiences/ #newvegas
A Bitcoin conference in the mountains. #proofofwork
Are there other open source blossom servers than https://github.com/hzrd149/blossom-server ?
Not active anymore nostr:npub1qg8j6gdwpxlntlxlkew7eu283wzx7hmj32esch42hntdpqdgrslqv024kw
Hi nostr:npub1h0uj825jgcr9lzxyp37ehasuenq070707pj63je07n8mkcsg3u0qnsrwx8 I'm not able to login on nostr:npub1wnwwcv0a8wx0m9stck34ajlwhzuua68ts8mw3kjvspn42dcfyjxs4n95l8 using Keychat Browser. The menu doesn't open and the sign up button doesn't open too. Do you reproduce this?
Sorry, it was an Iris bug
This is annoying. Got a CSAM report for user-generated content that I'm not even hosting. There's nothing I can delete. Apparently Cloudflare wants me to implement censorship lists.
Nostr clients are not legally required to maintain censorship lists any more so than web browsers like Chrome or Firefox are. There's just Cloudflare policy and guilt by association. Understandably, it's easy to confuse a web application url like iris.to/npub1... for a content host.
Should I implement ever-growing censorship lists, at least for visitors who are not logged in? The problem is, someone can just create a new Nostr account and re-post the links to illegal content ad infinitum. When this happens, maybe Cloudflare will get the point. Or more likely, they'll just delete my account.
Maybe there's some other ISP that allows hosting of applications that don't ship with extralegal censorship lists?
Iris native app via Tauri could be a resilient direction, but it kind of defeats the purpose of having a web app in the first place: ease of access, sharing by url and mobile PWAs that bypass app stores.. If you're going to have a native app, actually native-built will probably have better UX.
How are other web clients dealing with this? nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn
I have temporarily "solved" the problem by displaying this passive-aggressive notification when the hash of the public key you're trying to view is on the CLOUDFLARE_CSAM_BANNED list.
The hash list itself is here: https://github.com/irislib/iris-client/blob/main/src/utils/cloudflare_banned_users.ts
This is annoying. Got a CSAM report for user-generated content that I'm not even hosting. There's nothing I can delete. Apparently Cloudflare wants me to implement censorship lists.
Nostr clients are not legally required to maintain censorship lists any more so than web browsers like Chrome or Firefox are. There's just Cloudflare policy and guilt by association. Understandably, it's easy to confuse a web application url like iris.to/npub1... for a content host.
Should I implement ever-growing censorship lists, at least for visitors who are not logged in? The problem is, someone can just create a new Nostr account and re-post the links to illegal content ad infinitum. When this happens, maybe Cloudflare will get the point. Or more likely, they'll just delete my account.
Maybe there's some other ISP that allows hosting of applications that don't ship with extralegal censorship lists?
Iris native app via Tauri could be a resilient direction, but it kind of defeats the purpose of having a web app in the first place: ease of access, sharing by url and mobile PWAs that bypass app stores.. If you're going to have a native app, actually native-built will probably have better UX.
How are other web clients dealing with this? nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn
Hiring: Full-time dev for Iris & secure DMs on Nostr
Nostr should be the simplest, most sovereign way to run an online store: just a phone, no server, no payment processor, no 3rd party accounts. With Cashu, even checkout works offline. No dependency chains, no failure cascades, no loading spinners.
But for e-commerce to be safe, we need encrypted DMs with forward secrecy. Without double ratchet or MLS, a compromised Nostr key leaks all past / future customer messages: orders, addresses, identities.
Secure DMs and groups don’t need network effects. Push notifications keep users coming back. Great way to grow Nostr.
Nostr can be like Signal, but better: No phone number or 3rd party account needed. Communicate over any relays, any clients, even offline over wifi or bluetooth. No central gatekeepers. Just keys.
Iris is the only client with double ratchet today, but any client handling sensitive data needs forward secrecy.
Want to help build that? DM me securely at https://iris.to/sirius.
We've filled the position. Appreciate all the applications!
We've filled the position. Appreciate all the applications!
OpenRouter.ai "pay with crypto" 💩 Is there any similar service that takes lightning or even on-chain bitcoin?
Merged some Iris pull requests made by https://devin.ai/ agent and it was great. I like that it runs on a cloud VM, not on my laptop filesystem and cli. I want to try the new Cursor agents and Cline as well. What are your favorites?
Can you update it to add Iris? Merged PR on GitHub some time ago https://github.com/fiatjaf/njump/pull/100
vibe coded this. nostr firehose stream, media only, scroll to pause, tap media to get to profile
https://nostrstream.replit.app
nice in full screen.
(you may see things you don't want to see)
I have a dev position open btw
Who maintains njump.me?
The graph was crawled using https://github.com/mmalmi/nostr-social-graph . I used a node.js script from the repo, but the same stuff can be generated in Iris on the social graph settings page.
The repo has a Dockerfile for a server which keeps an up-to-date version of the graph, runs here https://graph-api.iris.to/ . On Iris build time, a 2 MB social graph dataset is requested from there. Should probably refresh on 1st iris.to open as well.
The graph up to approximately 3+ degrees is currently 200K users, 6M follows, 80K mutes. ~50MB. My macbook can easily handle it, but mobile phone will crash. Native apps on mobile should easily handle it.
The exported file contains uniqueIds: public keys mapped to integers for shorter representation. Then follow lists which are encoded using these integers. I want to do a binary export format: it would cut the file size approximately in half.
With a fresh 2MB graph, new user who follows 1 user from the graph gets this
If you crawl up to infinite distance from entry point, you might get lots of spam accounts that follow each other. Interesting topic for research and visualisation.