WoT is the real PoW
nostr:nevent1qqsyg5sskcd8jj39v33ft9g0c5ktfvredhcd7x0mj0ggfej4fvh0twqpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsqqqqqqzp8l74ff0l29zxrml8yggk8jnamje39k6e3ayzf7u5awqqrqsqqqqqpuahhq3
Do you really think new users can pay for proof of work?
This is not very different than Bitcoin itself. All the PoW is centralized on those who have the hardware.
It's because most wot in nostr is just really dumb (just follow's follow lists). We need to get better at that. The simple replies on #introductions should already kick most brand new accounts into the wor space.
Cool learning from this spammer: if the nostr client downloads and stores the spam event locally and the relay deletes later, the client doesnt get any notice it was deleted and must develop it's own ways to clear the local database out of it.
Same for local relays, like Citrine. Once it gets there, Citrine doesn't have a good way to remove it. The client will just be getting the spam event over and over again.
Yeah, anything that adds a ptag might perpetuate it. Reports, mute lists, etc.
The goal should be able to have better tools to clean up the local database as many of these events will get there no matter what.
nostr:nprofile1qqs8eseg5zxak2hal8umuaa7laxgxjyll9uhyxp86c522shn9gj8crspzemhxue69uhkyetkduhxummnw3erztnrdakj7qgwwaehxw309ahx7uewd3hkctcprfmhxue69uhkummnw3ezuargv4ekzmt9vdshgtnfduhsgjx9px any chance can you offer .onion addresses for all relays from relay.tools ? :)
We are going to be cloudflare's worst enemy :)
nostr:nevent1qqs9eq37mz0a9sk8tyddz5r5d0ywtx7e5l3kh2ft7vxw4w35v4ph9sgpzpmhxue69uhkummnw3ezumt0d5hsyg9v8a40u96e8asczpgnmty6re2yapaee6gmylfhhz8vtra64yq54gpsgqqqqqqs0uzz7j
nostr:nprofile1qqsrxra3gv0lnkxz2pcxh0xuq9k4f9dr7azwq3aypqtnay4w0mjzmtqpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqpzamhxue69uhkzarvv9ejumn0wd68ytnvv9hxgtcpzfmhxue69uhhqatjwpkx2urpvuhx2ucunm6wg does Alby accept Tor connections in the NWC service? Do you offer a .onion address? We could have a setting for NWC after this.
Tor or just base Amethyst?
It doesn't seem to use much more than other social media apps on my phone, but I can try logging into your pub key to check.
Do you have relays on the other lists? Citrine should never be a public outbox because no one can access your phone to download your events. You have to use a relay everybody can see.
Yep. Reports, mute lists, and other negative reactions also create these events that cite spam keys. So, you still need to apply the rest of the clients filters to the results as usual.
Transient NFC accounts can now be used together with a decoy account. Once the app goes to the background, the NFC account disappears from the phone and the decoy account becomes the primary.
Next version will be 🔥
1. Put the nsec in an NFC tag.
2. Hide the NFC tag in your clothing.
3. When you need to use the account, tap the tag use it.
4. When the app goes to the background, the phone deletes all traces of it.
If somebody confiscates your phone, there will be no trace of your real account.
And now they will think you operate only the decoy account.
How would you feel if Amethyst automatically created a Relationship Status event for every person you interact with (every like, zap, reply) and add them to a "Interacted with" user list.
Then you can filter your feed using that list as authors OR filter your notifications by them, getting rid of all types of spam.
I think the note will help over time. There wouldnt be a need to download the key's entire history to calculate. Clients can just download all statuses. I would work great with local relays :)
If setting up a relay is too much work, Nostr will never work. We might as well just keep using a centralized Twitter, because nostr won't be much different.
We have to figure out a way anyone can do.
We will add as well. "Interacted with" doesn't mean positive interaction. You can react with a 🤮😡 and it will still be marked as "interacted with". Then once the client tries to display, the block list, hidden words, anti-soam filters or reports will filter the list further.
The "interacted with" is just to separate known accounts from new.
Which is already implemented today: the author can report the spam and it will hide, but only if you follow the author. It's the same mechanism.
However, authors are not repointing spam anymore. There is too much of it. They can't keep up.
WoT is the real PoW
nostr:nevent1qqsyg5sskcd8jj39v33ft9g0c5ktfvredhcd7x0mj0ggfej4fvh0twqpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsqqqqqqzp8l74ff0l29zxrml8yggk8jnamje39k6e3ayzf7u5awqqrqsqqqqqpuahhq3
How winning looks like
nostr:nevent1qqsfvxp3rjvc789z8v5qnhc0v2fazwhz6d9gj7fhrr4t0ha6l6naq2spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg8zenmu7gzq8ulj5jj4kv50ph3muwz43f747vmr9ld2alrjdswgavpsgqqqqqqskr4xzd
Competition. Now 500 relays are suckers and can either step their game up or not be used at all.
But I see much more than 3 relays succeeding. I barely see spam right now, even though I am not using utxo's custom relays. The relays having trouble seem to just be the ones that can't or won't implement fixes for it.
Spam filtering has been a basic relay activity since day 1. I don't think adding spam filtering moves us to smart relays, dumb clients.
Also, the reason I don't see much spam is because Amethyst also has spam filtering. So, it's not that clients are giving up.
In the end, clients alone can't solve this. Relays alone also can't solve it. Both need to be developed to make things work.
Super basic stuff like looking for duplicated content, selecting user lists for notifications (wot), sentence hiding using post + profile info (so spam keys must not have a user metadata, otherwise it's easy to filter).
But I want to do a more traditional 5-levels deep wot DVM to add to the process.
Yeah, if DVMs are not available, I think it would be best to start marking users as "interacted with before" and then filtering by those. Meaning, you have to have liked or replied to the person before to show up on notifications.
Which is very similar to how we separate known from new people on DMs.
How winning looks like
nostr:nevent1qqsfvxp3rjvc789z8v5qnhc0v2fazwhz6d9gj7fhrr4t0ha6l6naq2spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg8zenmu7gzq8ulj5jj4kv50ph3muwz43f747vmr9ld2alrjdswgavpsgqqqqqqskr4xzd
Bloom filters are awesome! More feedback is welcome!
nostr:nevent1qqstyvmhgw7uwq6pkut7qtpc4ecawknwwcq0cu0w5la3wfa5yvepsucpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsydl97xpj74udw0qg5vkfyujyjxd3l706jd0t0w0turp93d0vvungrqsqqqqqpkyzztk
I don't know if limiting makes sense. At some point we are going to have 100 spammers for each real pubkey, so they will be a need to create more interesting relationships between keys and limits won't really be helpful.
The goal would be to start marking folks you talk to over and over again but don't necessarily follow. Interesting replies for instance, can be added so that if the person replies again the app can tell that it is the same person and not an impostor.
It's like on chats, if you reply to a DM, it marks that person down in the known tab. I am trying to envision a similar thing for the regular feed.
Picture this:
1. You type on Google "laptop won't turn on"
2. Google now knows you have a broken laptop and can estimate how desperate you are to fix it.
3. Because it knows how desperate you are, it can increase shop prices proportionally.
You are going to pay the maximum they get you to pay.
That's algorithmic pricing.
The more companies know about you, the more they can predict and sell how desperate you are to other stores out there.
An internet-connected car knows much more about you than you realize. A smart TV also knows what you like. Your Alexa knows if there is a problem in the home.
Privacy is much more than just sensitive data.
It's about not giving leverage away.
Because algorithms will use it against you.
Be safe out there.
Notes by Vitor Pamplona | export