Spammers can just create a GitHub project, put the nip05 verification there as a GitHub Page and be valid for free. So, I don't really thing this does much.
All they need is a free hosting service. They can even use their own personal computer at home behind a Tor connection to serve as the NIP05 address.
They can even use Orbot and get their phones to reply to the nip05 verification.
Posts don't have a language code in them so we need to download everything, process all of them of language code (which fails in 10% of the time) and then delete everything that doesn't match the user language. It's a lot of data usage.
But the main issue is that it creates local bubbles. If you use Twitter for instance, you rarely see Arabic or Mandarin posts, even though there is as many of them as in portuguese. The client just hides all external viewpoints from you. Making users a slave of their own linguistic cultures.
Ou continuar avançando as traduções automáticas de forma que vc consiga entender o que acontece em qualquer língua. Temos o básico hoje, mas pode ser muito melhor.
Has any client tried it? People have been talking about this language tag for more than a year now. I'd love to get some data to see if it actually works or if it's going to be more messy than a local relay.
I don't think it will work because nothing that requires the writing client to change works in Nostr. But I am open to the idea.
Nothing that requires the writing client and writing user to change works in nostr. You might as well just run a content tagger using NIP32 and make a client that filters by language code from the tagger.
I am just trying to get a test out and the only way to test it is to have sufficient tags in all posts with all clients. One client doing this won't work because the user will miss a lot of posts that are not tagged.
A service can test the idea ery quickly without modifying any client. If no one is willing to run the service, then I trully question if this feature is actually needed or if it is just a hollow feature that nobody actually cares.
Not really. I would do a service that creates 1985 tags with the language code using the same created_at the tagged post has.
Then a client can just do a REQ for the latest 1985 tags and load all the event ids individually. A webpage could easily do that and I think it would work on Coracle right now, without any changes.
This is dumb. You should almost never ask the notes I have reacted to. And if you do, you should be ready to receive LOTS of negative stuff. You should also check for reports and act accordingly.
Reactions of a person are not always positive and will always include posts they didn't like.
Sim, Web of Trust é uma opção, mas essa proposta mais raza de olhar só seguidor de seguidor e não seguidor de seguidor de seguidor de seguidor de seguidor é altamente centralizadora. Ela favorece contas maiores e faz com que elas cresceram ainda mais e bloqueia os usuários sem muitos seguidores ainda.
Hum... If the user is on the blocked users it should already be hidden. 🤔 Can you check if the user is there? You can always mute the person again to re add it.
It could be that you reported his person but the subsequent hide list never got updated or got deleted 🫤
But they did stop it. At least in the user's own space. Mute words just make sense to a whole lot of people. Sure, there are way better options, but the simplest that gets the job done to that specific user always wins.
It worked as the thing it was. If the reply guy gets smarter, we can also get smarter. But it definitely worked against all the 50 or so replies that I got.
I agree with you. I just don't think this particular instance is representative of an actual attack. Whatever we code for it can be circumvented by a smarter player. Not that we shouldn't code it, but let's be mindful of what we are solving for.
Real bots with WoT (because people will gladly sell their nsec to a bot maker and restart their accounts) will be much more demanding than this simple attack. They are going to look, act and work as a real human.
Every message in Nostr with immediately get 200 replies with products and opinions from people that are paying for it by nsecs of previous real users with WoT and so on. Any serious defense on this will need to include a complete understanding of the entire network or it will be something selected by the user, like just people that I follow.
I did see it and I do agree its a massive problem and small relays are the solution. But small relays is just decentralized moderation. The moderation is still there, just run by thousands of relay runners instead of an organized central point. Which is better, but the infra to moderate in a decentralized way needs to be there.
That's why you me relay ops interfaces are so crucial to the future of nostr.
We need to code a sync button that connects to all 3000 relays, sends posts authored by the account to the public and private home/outbox, p tagged posts to the public inbox and DM inbox, depending on the type, and everything to the local relay.
Humm.. you need the Play version of amethyst, not the FDroid version. If zap.store doesn't show, try Obtainium. You can get it straight from the GitHub releases.
Only use Citrine as public inbox/outbox if through Tor.
nostr:nevent1qqs0dkrlqa9z9ad96n7d55df7s59gmpcxtrllv80cjaq5txfgl2zx9spzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtczyrkmgup8z2t6cknp7fml8ng5me2vvl44enfqauxemu5muxrgtwcqgqcyqqqqqqg9cs43c
Inbox must allow other people to access it to send you notes or DMs. If Citrine is only running on your phone, no one will be able to access it. Tor opens it up to the world. If you are not using something it open it up, you will never receive a DM.
Only use Citrine as public inbox/outbox if through Tor.
nostr:nevent1qqs0dkrlqa9z9ad96n7d55df7s59gmpcxtrllv80cjaq5txfgl2zx9spzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtczyrkmgup8z2t6cknp7fml8ng5me2vvl44enfqauxemu5muxrgtwcqgqcyqqqqqqg9cs43c
Notes by Vitor Pamplona | export