git ssb


0+

keks / untitled



better nomenclature

%1oi2yMBUsJ1Na5bUz8DemaCT9QXs7slowvLIvRyqTyk=.sha256
Opencryptix opened this issue on 2/22/2017, 3:59:04 PM

better nomenclature

%d8ujrpNHo27qS8hc5auyg6LQMlxUgaTFdun6R18Av08=.sha256 cryptix · 2/22/2017, 3:59:10 PM

users: differentiate between _backupee_s and _operator_s.

%v6K+VBEATdm/QMg1XGTNW8uCmnL7cjVL+vSUN2/1Rrg=.sha256 cryptix · 2/22/2017, 3:59:12 PM

servers: differentiate between live backup location a point where a user can send and retrieve their data and cold spare which holds (some) of the redundant blocks but can't be used to access the _backupee_s data.

%/8yoxeYnaHQOU0LIjtZJI2+HkYd7FhU0eoUEMX++vmQ=.sha256 keks · 2/22/2017, 9:57:31 PM

I agree on the distinction of the servers (my server vs my server's peers), but for me the user always was the backupee, never the operator. The operator might also be a user though.

Do you have a proposal for the server names?

%5OclBoT30gQoVpvx42dZb/j13Dx1Im1HOI1nX/1vFzU=.sha256 cryptix · 2/24/2017, 3:46:41 PM

The operator might also be a user though.

Sure. Nothing stops you from playing two roles but they should both be defined cleanly.

Do you have a proposal for the server names?

I feel tempted to make stupid word plays on the band but nothing good yet.

I'd like for it to signal that the hot mirror can be fully accessed at all times. It's essentially a clone of your data.


Built with git-ssb-web