Nostr Web Client

This seems like a great way to potentially unburden the load requirements by spreading the load over relays together. Making it a nip is a technical challenge. Which requires some innovative ideas to preserve privacy and security without relying on a centralized proprietary language translation service.

Fernando Bittencourt 1y ago

The technical part is simple. You can add a translate tag to the event with the translated text. This TAG would not be included in the hash calculation. Privacy in the relay no longer makes sense, since it will already send you the original text, so it already knows everything and the translation does not add any more information.

We let users choose the relays with the price and features that interest them.

We will now confirm that the relay sends us all events, that it does not use our data for other purposes. The relay/user relationship is already one of trust. And if this trust is broken, just change to another relay.

Reply to this note

Please Login to reply.

Discussion

Positive Vibes 1y ago

Interesting approach. The technical challenge comes from choosing the language translation software. If this was a nip then relays could be free to choose their own implementations. The challenge comes from accuracy of the translations, handling all of the translation load requests, and ensuring cross compatibility between languages for the available relays.

For example if there isn't a unified translation model. Misinterpretations from mistranslations would be rampant.