It’s all part of the spec that I wrote that Senya based his crowd funding on I have no knowledge what the current situation is, whether the mentioned automatic backup is even planned to be implemented, but it’s totally doable.
But this automatic backup should contain the same data as the manual backup, so it also needs the comments (and other additional metadata).
As I said, ‘Bob is happy for this to happen so clicks OK. His comments in the private conversation are then sent from his home pod to Pod Y.’ His comments are stored on his home pod, and sent direct from there.
And if the pod of this person doesn’t exist anymore (because maybe the person was on the same pod as you, when your pod disappeared?) , it is not possible to restore the data?
That’s a choice that I make when I comment on a post; I implicitly authorise it to be shared with those with whom it has been shared.
But you don’t know with whom the post has been shared? Maybe your comment is already on diaspora.dodgy-identity-thieves.com because the post author shared it with a person on this pod. You don’t know it, you don’t see it, you can’t control it. So you are trying to control something, where you don’t even have control when you write your comment.
If you write a comment on a post from alice, you trust alice, that alice shared the post (and your comment) only to trustworthy pods (you can’t control it). So why don’t you trust alice when she wants to move to another pod?
why do you try to control something where there is no control? This only makes this feature less usable, but doesn’t stop anybody to do bad things if he wants to. If you write a comment on a Post on Alice:
- You trust alice, that she has shared the post only to trustworthy persons
- You trust alice, that she don’t leak your comment to someone else (now and in the future and in the backup)
- You trust every other person (the person with whom alice shared the post), that they do the same …
You don’t have control on anything when you write the comment (you need to trust alice) … why do you try to imagine to control what alice could backup? If alice has her own pod, you also don’t have control on how alice backups here database and where she stores the backup and what and how she restores the database-backup on another server?
Everything you try to imagine control where there is no control only makes this cool and useful feature:
- more complex
- more error prone
- takes longer to implement
- less useful for the users