3 ms·

I hate sounding like a broken record here but if you don't meet the following criteria then stop saying you're going to preserve users' data forever. * Have a

by jmathai 14y ago

I hate sounding like a broken record here but if you don't meet the following criteria then stop saying you're going to preserve users' data forever. * Have a full featured API right out of the gates * Outline how users get their data out of your system * Open source the code to ensure the ability for it to live on Pledges are cheap.

pg 14y ago
Not as cheap as dismissive comments on forums.
- jmathai 14y ago
  How's this dismissive? I've blogged and posted about this topic for a while [1]. I've also spent the last 2 years full time on a project that relates to data ownership and portability [2][3]. For those of us who write software specifically designed to solve this problem it's unfortunate when others make the same claims based simply on promises. [1] http://blog.theopenphotoproject.org/post/10537443380/namespacing-the-web-for-your-photos http://blog.theopenphotoproject.org/post/10537443380/namespa... [2] https://github.com/photo https://github.com/photo [3] http://www.shuttleworthfoundation.org/fellows/jaisen-mathai/ http://www.shuttleworthfoundation.org/fellows/jaisen-mathai/
  - garry 14y ago
    Your suggestions are absolutely valid, and I appreciate them Jaisen. Your efforts with the Open Photo Project are noble, and I respect them a ton. Give us some time -- Posthaven was a vague idea just a few months ago. We are under the gun to ship software at the moment.
    - jmathai 14y ago
      Appreciate the response. I do hope you get around to adding some of these features. The Internet needs services like that desperately. But until those features are released I have to remain a cynic :). Ping me on Twitter (@jmathai) if you wanted to grab coffee. I never pass an opportunity to chat with someone about the preservation of digital archives.
jorde 14y ago
Providing fully featured API out of the gates for a service which got launched in a hurry (at least that's the impression I got) would probably be a bad idea considering the early nature of the service. I'm confident that Garry will provide one but API is something people shouldn't rush too much with. I'm a firm believer of shipping fast but with APIs I tend to be cautious. As for feedback to Garry: it would be nice if the line width would be shorter or text being larger, I find it myself playing tennis a bit (fan of large article type here)
- jmathai 14y ago
  I just think when you make a pledge to users that you'll safeguard their data forever that you need to think through a few things that their team hasn't yet. Postponing the forever message until the underlying features to support it are built would go a long way. Personally, I don't see the issue in launching with an API early. We launched the API for OpenPhoto well before we had any UI.

by jmathai 14y ago

pg 14y ago

Not as cheap as dismissive comments on forums.

jmathai 14y ago
How's this dismissive? I've blogged and posted about this topic for a while [1]. I've also spent the last 2 years full time on a project that relates to data ownership and portability [2][3]. For those of us who write software specifically designed to solve this problem it's unfortunate when others make the same claims based simply on promises. [1] http://blog.theopenphotoproject.org/post/10537443380/namespacing-the-web-for-your-photos http://blog.theopenphotoproject.org/post/10537443380/namespa... [2] https://github.com/photo https://github.com/photo [3] http://www.shuttleworthfoundation.org/fellows/jaisen-mathai/ http://www.shuttleworthfoundation.org/fellows/jaisen-mathai/
- garry 14y ago
  Your suggestions are absolutely valid, and I appreciate them Jaisen. Your efforts with the Open Photo Project are noble, and I respect them a ton. Give us some time -- Posthaven was a vague idea just a few months ago. We are under the gun to ship software at the moment.
  - jmathai 14y ago
    Appreciate the response. I do hope you get around to adding some of these features. The Internet needs services like that desperately. But until those features are released I have to remain a cynic :). Ping me on Twitter (@jmathai) if you wanted to grab coffee. I never pass an opportunity to chat with someone about the preservation of digital archives.

jorde 14y ago

Providing fully featured API out of the gates for a service which got launched in a hurry (at least that's the impression I got) would probably be a bad idea considering the early nature of the service. I'm confident that Garry will provide one but API is something people shouldn't rush too much with. I'm a firm believer of shipping fast but with APIs I tend to be cautious. As for feedback to Garry: it would be nice if the line width would be shorter or text being larger, I find it myself playing tennis a bit (fan of large article type here)

jmathai 14y ago
I just think when you make a pledge to users that you'll safeguard their data forever that you need to think through a few things that their team hasn't yet. Postponing the forever message until the underlying features to support it are built would go a long way. Personally, I don't see the issue in launching with an API early. We launched the API for OpenPhoto well before we had any UI.