elon will ban you for it
then you can have multiple sources so redundancy, you can even use p2p
no its more than that the media in notes needs to be addressed as hash ids and then relays or clients can decide the source
the centralized media is a big weak point on nostr currently
nostr runs by the rules of math not gov
hi
if you are looking in the code just search for where it uses reports
real censorship is nearly impossible on nostr
your follows reports, 5 equals hidden but it seems very buggy
the follows are a list, but yes we need more
Iris now supports secret chats that don't leak metadata, implementing the https://hrfbounties.org/ bounty #3. It works also for group messaging.
It's a quick & dirty solution, but works. A shared nostr account is created for the secret chat / group. Its nsec can be shared via link, qr code or invite message from a single-use anonymous account.
Users can then communicate using the shared account's messages-to-self. Iris signs the inner messages with your own key, but the arrangement could be used for anonymous group messaging as well.
I'll also add inner message encryption at some point, so you can ensure that only certain group participants can read the message.
This arrangement doesn't introduce any new event kinds and works also in clients that haven't implemented a special UX for it. You can just log in with the nsec and message yourself.
I had to disable the Iris social graph filter to let invites through, so now Iris DMs are open to spam again, but I'll try to figure out a better solution.
As always, the UX needs a lot of attention, but I believe here's an MVP.
Screenshots:
Alice wants to message Bob:
Alice sends a secret chat invite to Bob:
Bob automatically follows the invite from Alice. They can now message each other in the secret chat:
Here's how the invite looks in another client. I will add an "nostr:ninvite" URI in addition to the nsec.
why not adopt simplex or their methods for dms?
I don't like new event kinds. They make building a nostr client more difficult.
I'd like to build a gundb-like universal database on Nostr where you write to filesystem-like paths such as group/[id]/messages or group/[id]/name instead of defining new event kinds for everything that could expressed as a path. https://github.com/gundb/gun
Nostr is not going to be an "everything app" if you need new event kinds for everything.
I'm quite busy improving the very basic features of Iris, but I'll try to find time for it at some point.
i think thru adoption new event kinds evolve the protocol allowing it to potentially always change
so communities cant pickup content from notes not posted in it? seems siloed
nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 goes to show that if you want fame, a wife, money and hit pieces, all you have to be is a straight, White fediverse developer.
My deep and humble congratulations on finally making enough money to live on, in the fediverse, Alex!
NOW HOW ABOUT GETTING ON TO MAKING YOUR OWN BACKEND SO YOU CAN GET AWAY FROM TRANNY TECHNICAL DEBT ALEX
please. I'll even help where I can. You know I can, you watched me do it lol
he needs to stick the knife deep in the fedi and make it bleed purple
nostr solves all this