> How does it handle a relay tempering with the content of posts or altering the meta-data? Or a relay who'd be sending out fake posts?
Author signs every post with their key.
Author signs every post with their key.
So the client does the verification? Or is it the relay?
Also, I didn't mean impersonating a specific author, I meant generating posts that no one truly posted to it. So when your client lists the chronological most recent posts you get a bunch of fake manipulated content that was mass generated by the relay itself for example.
From the README:
> A relay is very simple and dumb. It does nothing besides accepting posts from some people and forwarding to others. Relays don't have to be trusted. Signatures are verified on the client side
---
> So when your client lists the chronological most recent posts you get a bunch of fake manipulated content that was mass generated by the relay itself for example.
From the README:
> Each client can decide how to best show posts to users, so there is always the option of just consuming what you want in the manner you want — from using an AI to decide the order of the updates you'll see to just reading them in chronological order.
Not sure how it allows you to find new people or responses to comments. Seems like it should be a key part.
I guess some level of interaction will be needed to replicate the things people look for in Twitter. I guess a very basic functionality that that would cover this would be posting in your timeline "responses" to other posts by including the key of the other author and the cryptographic signature of the post. From that a client would be able to obtain the "parent" post and build a thread.