In case you were wondering what the point of https://VerifiedHuman.net is… After Nostrica I’ll be spinning up a Nostream relay and attempting to modify it to only accept Verified Humans.
It’ll be an invite only, spam free relay where the only barrier to entry is being a human and not a spam bot.
Humans FTW!
I’m excited to play with this at Nostrica!
Wow that’s cool. Do you add anything to the jar or is it self contained?
Did I see there was a Nostrica relay somewhere?
I'm getting an error from some relays: "Subscription rejected: asf". Does anyone know what this means? I was getting some rate limited for sending too many requests before this. Did I get blocked somehow?
If you’re okay with staying custodial and it’s for relatively small funds https://ln.tips is pretty good. By default you operate though a telegram chat but you can link it to blue wallet or Zeus as well. Muun is a good non-custodial option for larger funds, but isn’t a true lightning wallet and can resort in higher fees for small transactions sometimes. I use these both of these in combo and it’s pretty seamless.
Thanks, it was almost scary how easy ln.tips was to set up.
I still think Nostr is not particularly good at censorship resistance. From that perspective it is pretty similar to that of RSS, or ActivityPub which have been around for a while. At the end of the day if most companies don’t want to host your stuff then it will be hard to keep it visible. Nostr isn’t peer to peer (yet, anyway).
What’s special isn’t that there are no rules, it’s that you get to choose which rules you want to play by. You choose this in your clients and choice of relays. Most people will want their relay owners to respond to reports, support deletes and blocks, etc. But rather than it being some small group at a big American tech company doing the censoring it can be your friend or your peers or money or some other method you choose.
Yeah I think we will eventually allow exporting all your posts in Nos. Some people also choose to run their own personal relay that only they can write to. That acts as a backup as well. I hadn’t thought about backing up to iCloud, but it wouldn’t be too hard.
It's a tricky question in Nostr. The answer is: no one really knows. Scattered across the relays. Most clients don't upload all your events when you add a new relay. I have seen this backup service but haven't tried it myself: https://nostryfied.online/ by #[2]
Huh?? If I'm unhappy with what Twitter client A is blocking I can't move to Twitter client B which runs using different rules. Yes it's inconvenient to switch Nostr clients, but it's not worthless to give people the choice. It's actually a tremendous power that we gave up in Web 2.0 apps.
I'll add gossip model https://bountsr.org/gossip-model/
Nip65 is a bit weird, I don't understand the rationale of not using kind 0 events. https://github.com/nostr-protocol/nips/blob/master/65.md#why-not-in-kind-0-metadata
But might still add support for it
I would also like to see NIP-65 support in Iris. I'll be adding it to Nos along with the gossip model. It could definitely work in kind 0, although most apps are currently using kind 3, and the kind 3s can get kind of large with all the pubkeys, so the rational break it out and keep it lightweight makes sense. The cheaper it is for relay owners to host relay lists the better greased the wheels of Nostr will be I think.
Many people go ahead and open a proposed NIP as a pull request to get feedback before implementing. That's still a good idea I think. But the NIP readme says they won't be merged until they're being used for real.
Sorry for anyone getting notified for all these. I’m using this thread to test Nos 😬
Hah, I think my client was just broken. Fixed now?
Also same question for #[2]
Hey #[3], what client did you post this reply from? It's using the old "e" tag format and I'm trying to figure out if I need to support it in Nos.
Oops, I meant to reply to your message here. Replied to root instead.
It’s really a shoot first, make NIP later system, since NIPs are encouraged/required to be implemented somewhere in production before they are approved.