i notice that Hashbase is a Delaware company:

security from being forced to disclose data (I mean as it’s all encrypted I’m not sure if this is an issue - but maybe there is meta data that could be forced to hand over), if so maybe Switzerland. I notice that’s where proton mail setup.
What criteria are you using for this? Eg
- ease of set up (RS would be easy)
- location (US for some reason?)
- security from being forced to disclose data (I mean as it’s all encrypted I’m not sure if this is an issue - but maybe there is meta data that could be forced to hand over), if so maybe Switzerland. I notice that’s where proton mail setup.
I mean as it’s all encrypted I’m not sure if this is an issue
uh, at the moment Scuttlebutt is more a public record, only private messages are encrypted and they are still "on the record" (connected to everything else on the record).
> I mean as it’s all encrypted I’m not sure if this is an issue
uh, at the moment Scuttlebutt is more a public record, only private messages are encrypted and they are still "on the record" (connected to everything else on the record).
Oh right - so you don’t need a key to decrypt the record? That seems like a basic misunderstanding I have had of how ssb works.
In that case I’d say in the long run the jurisdiction of the service company for peach cloud should be in a location that has strong data protection laws/leanings.
For now it’s what ever is easiest for you.
Oh right - so you don’t need a key to decrypt the record? That seems like a basic misunderstanding I have had of how ssb works.
In that case I’d say in **the long run** the jurisdiction of the service company for peach cloud should be in a location that has strong data protection laws/leanings.
For now it’s what ever is easiest for you.
@ahdinosaur you are Root Systems as much as any of us - if you want to use the company as shell for now in the same way as Tapin and TTB have I think you have the agency/mandate to to decide this. The only considerations I will want to check are operational risks and is insurance coverage needed.
If the question is more "does Root Systems want to pickup and run the businesses of peachclound - that will need a broader conversation on rolls and responsibilities. We could have this conversation at our retreat next week :)
@ahdinosaur you are Root Systems as much as any of us - if you want to use the company as shell for now in the same way as Tapin and TTB have I think you have the agency/mandate to to decide this. The only considerations I will want to check are operational risks and is insurance coverage needed.
If the question is more "does Root Systems want to pickup and run the businesses of peachclound - that will need a broader conversation on rolls and responsibilities. We could have this conversation at our retreat next week :)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
question is whether to
i notice that Hashbase is a Delaware company:
What criteria are you using for this? Eg
uh, at the moment Scuttlebutt is more a public record, only private messages are encrypted and they are still "on the record" (connected to everything else on the record).
Oh right - so you don’t need a key to decrypt the record? That seems like a basic misunderstanding I have had of how ssb works.
In that case I’d say in the long run the jurisdiction of the service company for peach cloud should be in a location that has strong data protection laws/leanings.
For now it’s what ever is easiest for you.
well, is Root Systems keen to do business as PeachCloud?
@ahdinosaur you are Root Systems as much as any of us - if you want to use the company as shell for now in the same way as Tapin and TTB have I think you have the agency/mandate to to decide this. The only considerations I will want to check are operational risks and is insurance coverage needed.
If the question is more "does Root Systems want to pickup and run the businesses of peachclound - that will need a broader conversation on rolls and responsibilities. We could have this conversation at our retreat next week :)