3 ms·

They should charge to get an enterprise version with certain guarantees. Without payment and a contractual guarantee, it can only ever be for personal use.

• spraak 9y ago
  But it may be too early to even offer that
• KirinDave 9y ago
  You say this, but we use it as a convienient way to onboard new engineers. There is a huge amount of key material to exchange to bring one of our developers online and its a lot easier to move it without thumb drives or passwords shouted across the room (or the famous email-tar.gpg and slack the password). It's not reliable for storing customer data, no. But it's quite useful for a lot of quick engineering work.
  • pishpash 9y ago
    That is basically 'personal' usage. You can't build that into any formal process, even for onboarding -- any day it may not work. I also failed to mention that having an internal namespace for an organization may be relevant. People may not want to be public.
    • KirinDave 9y ago
      Neither seems terribly relevant, to be honest. In terms of namespacing, Corporations don't have their own space. What you do is have individuals send files amongst each other. And, are you suggesting that a corporate process has to rely on technology that is always available? I'm fairly sure that they don't. If corporate Wi-Fi and Microsoft Office are any indication, anyways. Please excuse any punctuation or capitalization today. I am training a new interface to Hacker News and the voice recognition sometimes produces slightly odd text.