Bluesky is getting a few things right… The compete to get accepted thing is brilliant. Clubhouse did that and it was really hot - until it wasn’t. I’ve heard no onboarding complaints. Then again it seems to be mirroring the experience of corporate social media - for both better and worse.

I woke up this morning with what I think is a good idea… I'll write something that analyzes the follower lists and recent DMs on my Nostream relay to determine who people on my relay interact with the most who don't already have write access to the relay. Then I'll white list the top X people on that list. Which raises a question - when User A responds to User B (publicly or via DM) will User A's client ever try to write to a relay it knows User B uses but which is not on User A's relay list? For example if User B's NIP-05 says their on Relay C, but User A retrieved the message from User B via Relay D, will User A's client ever try to write to both C and D even though C isn't on A's relay list? Clearly my plan will work if the unpaid user reads from my relay. But it won't be particularly effective unless clients try to respond to all the known relays for the other user.

Exactly!! Thank you for saying that! View quoted note →

How do you login to @primal? I seem to be logged into some read-only version with no way to logout. #help!

I spent the weekend rethinking "NIP-69" that @rabble and I had proposed. Based on some of the comments we had gottten I started with the idea of "labeling" and made the data needed for #ContentModeration just another type of labeling data. That required coming up with a NIP for doing labeling. I made it so you can use _any_ coding system / defined vocabulary. Do you want to tag your posts (or someone else's) with some ISO code, or a GeoNames place ID, or some code from a structured vocabulary like MeSH? Or maybe you have your own defined vocabulary (like I do)… You can do that with what I'm calling "NIP-68". You can see it here…

GitHub

nostr-nips/68.md at master · s3x-jay/nostr-nips

Nostr Implementation Possibilities. Contribute to s3x-jay/nostr-nips development by creating an account on GitHub.

I'm hoping that NIP makes Nostr interesting to the scientific community. (It would be very funny if "the gay porn guy" kicked off the process of getting scientists onto Nostr.) Then… I reworked our NIP-69 proposal so it's just a defined vocabulary for NIP-68 labeling. Actually it's two defined vocabularies. One is somewhat rigid, the other is more organic - anyone can just create a new moderation-related code and start using it. You can see my new NIP-69 here…

GitHub

nostr-nips/69.md at master · s3x-jay/nostr-nips

Nostr Implementation Possibilities. Contribute to s3x-jay/nostr-nips development by creating an account on GitHub.

It does have an impact on how things are done now. It deprecates both NIP-36 and NIP-56 and requires paid relays to accept moderation reports from unpaid users if the content being reported is on the relay. (Without that change relay owners may never know they have illegal content on their relay). Client apps can keep their current "report post" UI (or enhance it with new features), but they will need to change the event that's sent from type 1984 to type 32123. The few apps that are using the reports to filter/block what their users see (like @Vitor Pamplona's Amethyst) may need to make more more substantial changes (but they may want to wait, since this isn't the end of the suggestions regarding content moderation). I'm still discussing with Rabble the best way to present 68 & the new 69 as Nostr PRs, but that will probably get done in the next day or two.

💤 GN #nostr