8 ms·

No problem, you can already build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CV

No problem, you can already build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mounted filesystem.

montecarl 8y ago
Just in case anyone doesn't recognize this quote, it is from the 2007 hacker news post about Dropbox: https://news.ycombinator.com/item?id=8863 https://news.ycombinator.com/item?id=8863
- antoineMoPa 8y ago
  Are you telling me that I could build a startup with 3 lines of bash? (EDIT: and a fancy easy windows version)
  - deleted 8y ago
    [deleted]
  - Zak 8y ago
    A great many successful tech companies can be described in terms of more consumer-friendly Unix tools. Slack has the better part of a billion dollars in funding for what's essentially resource-hungry IRC with pictures. Dropbox does little you couldn't accomplish with a server and rsync. What I'm really eager to see is git for everyone else.
    - exikyut 8y ago
      What would "everyone else" do with Git? It's a Rube Goldberg solution implementing a highly specific set of ways to do file versioning. Most cloud storage providers offer rudimentary versioning; are you referring to the idea of promoting commits to being first-class? It would need to be baked into Word, Excel and similar, and those tools already have builtin version tracking, as horrible(?) as it is, so... :/
      - Zak 8y ago
        People I know who definitely have this problem tend to work in creative fields - especially musicians and (digital) visual artists. They almost universally have a bunch of files with names like project_final2_revised_reallyfinal3_with_edits_from_sally.psd. Of course, a solution that works well with all the different binary file formats people in those fields use wouldn't be easy.
        exikyut 8y ago
        Ah, that. Yes, absolutely I'd love for a solution that fixes that. It would definitely need to work with large files though, which categorically precludes Git. The first point, I think, would be building a delta engine with case-specific code for the most common ubiquitous file formats, like docx, xlsx, psd, etc. Of course it wouldn't be able to be perfect with everything but it would certainly be better than eg just recompressing each version or something equally naive. The UX would be the next major hurdle. Time Machine is a good example of the kind of simplicity that would be needed, but it would need to be a have a bit more surface area to be applicable and useful to all scenarios. One other feature that comes to mind, which would be incredibly difficult to get right but probably critical, would be useful version diffing. I think keeping this simple and just building something that can do $anything->SVG (with maybe cheats where bunches of the SVG is mostly just a bitmap in certain cases) and then doing something fast on the SVG (and/or its bitmap contents...) would probably be the most viable target.
        Zak 8y ago
        It think it does need branching and collaboration. There needs to be a way for Sally to contribute those edits, and they might not actually make it in to the final result. No doubt there would be a learning curve. I think that's OK. The target market here is serious users who already dedicate time to learning professional tools like Photoshop.
        exikyut 8y ago
        Oh no. Now you need full file format parsing so that you can resolve merge conflicts. :( That would take years to get anywhere with ._. The diffing idea I suggested above is just manageable, a la macOS Preview, with hacks. Branching requires folding-back-in, and that's not just a case of "A or B", it's a case of "A, B and C conflict with D and E, while F G and H are okay," where I could then say "save B and E but drop F". If B is a layer, E is an imported asset and F is a custom filter... you get the picture. You need a reimplementation of Photoshop (halting problem). :/ Sad that everyone hates GIMP. But... hmm, this could get folded into Blender, and then make the rest of the industry jealous.......
    - nlawalker 8y ago
      >> git for everyone else When you simplify and generalize git to the point where "everyone else" can use it, you get Apple's Time Machine and Windows' File History. I'm not that familiar with Time Machine, but if File History had a more visible interface that you could use to easily "checkpoint" individual documents or directories on demand, you'd pretty much be there. Branching is too complicated for most people to work with and overkill for most scenarios.
    - antoineMoPa 8y ago
      What about grep/sed/find for everyone else? Also, to get more ideas: echo "Make a startup with "$(ls /bin /usr/bin | sort -R | head -n 3)
- api 8y ago
  It really sums up nerds' lack of comprehension of the importance of user experience. It's like the UX version of the apocryphal "640k is all anyone will ever need."
  - pjc50 8y ago
    The other famous one of those is "No wireless. Less space than a nomad. Lame." https://slashdot.org/story/01/10/23/1816257/apple-releases-ipod https://slashdot.org/story/01/10/23/1816257/apple-releases-i...
    - Alex3917 8y ago
      The first iPod was terrible though and sold poorly. The 3G was the first good model, and they didn’t start taking off until the 4G. History only proves that his analysis was completely correct.
      - gargravarr 8y ago
        3G was when they added Windows support. Probably coincidence :)
        filmgirlcw 8y ago
        No, Windows support came with the 2G in 2002. iTunes for Windows wasn’t a thing and few Windows machines had FireWire, but the Windows-compatible iPod came out in 2002. The 3G was the breakthrough model, but I lend that as much to the dock connector (which was available in USB and FireWire) and the growth of x-platform iTunes as anything. The broader point that it required Windows support for the iPod to become mainstream is of course true. That said, the iPod was also the reason so many of us became Mac users in the early 00s because the “halo effect” was undeniable.
        mbreese 8y ago
        You're right. It really was the dock connector that made it a viable product for many people. The fact that the first iPods were Firewire (which I totally had forgotten about and I even had a 1G iPod) made it very difficult to make it work outside of the Apple ecosystem.
- rayiner 8y ago
  It’s a really great example of worse is better.[1] We went from sophisticated network file system to a daemon that destroys your battery life (at least on Mac) watching for file changes in a directory. [1] https://www.dreamsongs.com/RiseOfWorseIsBetter.html https://www.dreamsongs.com/RiseOfWorseIsBetter.html
  - michaelcampbell 8y ago
    Your situation is different than mine; this is the first I've heard of Dropbox even registering as a top use of battery. How many files do you have? I've got 26000 files in my Mac's dropbox folder. (Granted, very few of them change more than once or twice a day; maybe 20 or so of those do.)
    - rayiner 8y ago
      I last used Dropbox in 2011 or so (I stopped using it because it killed my battery life). It may have gotten better since then. (But my point is addressed to what it takes to get popular, i.e. that its easier to make a “dumb” tool popular, and Dropbox was popular back then.) EDIT: Clearly not just me: https://news.ycombinator.com/item?id=12464901 https://news.ycombinator.com/item?id=12464901 (thread from 2016)
      - jonknee 8y ago
        Going out on a limb here, but I think it's possible things have changed in 7 years (and that it was probably something specific to your setup, not something millions of Dropbox users with a Mac had to put up with).
      - michaelcampbell 8y ago
        > i.e. that its easier to make a “dumb” tool popular, If this was your intent, then using the tired "worse is better" trope and claiming an issue from 7 years ago, that no one else has claimed to have seen is seems a far cry from it. Dropbox became popular because it was easy, it worked, and did exactly what it said it did. That might be "dumb" in that it's not feature packed, but you use a lot of negative connotations when none are required.
- techopoly 8y ago
  I thought it sounded familiar!
- test6554 8y ago
  The dhouston on that YC post is this guy now: Andrew W. Houston is an American Internet billionaire entrepreneur who is best known for being the co-founder and CEO of Dropbox, an online backup and storage service. According to Forbes magazine, his net worth is ~$3 billion.
michaels9876 8y ago
Or just use Google Drive
- kbumsik 8y ago
  Sorry, Google Drive doesn't support Linux.
  - hatsunearu 8y ago
    https://abevoelker.github.io/how-long-since-google-said-a-google-drive-linux-client-is-coming/ https://abevoelker.github.io/how-long-since-google-said-a-go... And famously so.
  - Fnoord 8y ago
    No official support, but you can easily access the content read/write in multiple ways. I've used such a few years ago with a FUSE module, written in OCaml. The only complicated, annoying thing was getting authentication to work.
    - kbumsik 8y ago
      I've heard of it but is that reliable? I meant I'm a bit afraid of loosing data by using unofficial programs.
yread 8y ago
Reference for the uninitiated: https://news.ycombinator.com/item?id=8863 https://news.ycombinator.com/item?id=8863
deleted 8y ago
[deleted]
deleted 8y ago
[deleted]
srslack 8y ago
More seriously: Syncthing exists, and it is beautiful. I set my grandmother up with Synctrayzor and she doesn't know the difference between that and Dropbox. It is missing the ability to share things with a direct link, or share a repository or folder "easily" (read: in the same way it's done with Dropbox), but the trade off has been worth it for me.
- pjc50 8y ago
  Which cloud backend do you have it sync to?
  - vetinari 8y ago
    None. You run it on your machines and they will sync among themselves. No need for any cloud backend. Some people with Synology or QNAP run an instance on their NAS.
    - pjc50 8y ago
      But I (and I suspect quite a few other people) want a cloud backend to cover both the disaster-recovery cases and syncing while outside my LAN.
      - vetinari 8y ago
        1) you can sync with a device inside your LAN, even if you are outside, with global discovery (enabled by default). 2) you can run your own off-site instance, that can be hosted with your favourite cloud provider.
        amyjess 8y ago
        > you can run your own off-site instance, that can be hosted with your favourite cloud provider. How much would it cost to hire an admin to set up and maintain that instance? The whole point of Dropbox is that I don't have to do any work.
pjc50 8y ago
The modern alternative is probably Syncthing. I intermittently maintain a list of these things at https://github.com/pjc50/pjc50.github.io/blob/master/secure-clouds.md https://github.com/pjc50/pjc50.github.io/blob/master/secure-... ; none of them have ever been precisely what I wanted. The cheap alternative to Dropbox with Linux support you want was "Hubic" from OVH (edit: now discontinued)
- byproxy 8y ago
  How about Keybase? It has a pretty seamless files experience, I find. Open source, end-to-end encryption, Windows client, painless sync, free for 250GB...
  - bantunes 8y ago
    Stores your private keys, though.
    - byproxy 8y ago
      Well, according to this, they can't read your data. "These folders are encrypted using only your device-specific keys and mine. The Keybase servers do not have private keys that can read this data. Nor can they inject any public keys into this process, to trick you into encrypting for extra parties. Your and my key additions and removals are signed by us into a public merkle tree, which in turn is hashed into the Bitcoin block chain to prevent a forking attack. Here's a screenshot of my 7 device keys and 9 public identities, and how they're all related." https://keybase.io/docs/kbfs https://keybase.io/docs/kbfs
  - ahnick 8y ago
    Completely agree. I'm not sure why someone would choose Dropbox over Keybase nowadays.
    - skrebbel 8y ago
      Continuity? I mean, does Keybase have a business model yet? Or is it still "$bigshot_vc who is friends with the CEO believes a few crypto/security gambles are in order"? Not meant critically, I love that they exist and found funding. It's just, as long as the model is "once the privacy shit hits the fan in some widely published scandal, we'll be the one that's ahead" there's only two outcomes: 1. It doesn't happen soon enough and Keybase runs out of runway, or 2. It happens, one of the many Keybase products becomes wildly popular because of it, and Keybase will ditch the others because "yada yada focus core business".
fuzzy2 8y ago
In case anyone is wondering if there truly is something like Dropbox (delta sync, desktop app, mobile app, web interface, ...): There is. It’s Seafile. The Docker image is reasonably easy to set up and run.
dekhn 8y ago
I spent about a year of my life trying to get WebDavFS (backed by apache mod dav svn) working. I want that year back.
ekianjo 8y ago
Or you can use Syncthing instead, you know.
csomar 8y ago
What? No! The whole idea of paying dropbox 10 bucks per month is to get a ready-made functioning solution. It is not like they are not implementing a feature but removing one.

No problem, you can already build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mounted filesystem.

montecarl 8y ago

Just in case anyone doesn't recognize this quote, it is from the 2007 hacker news post about Dropbox: https://news.ycombinator.com/item?id=8863 https://news.ycombinator.com/item?id=8863

antoineMoPa 8y ago
Are you telling me that I could build a startup with 3 lines of bash? (EDIT: and a fancy easy windows version)
- deleted 8y ago
  [deleted]
- Zak 8y ago
  A great many successful tech companies can be described in terms of more consumer-friendly Unix tools. Slack has the better part of a billion dollars in funding for what's essentially resource-hungry IRC with pictures. Dropbox does little you couldn't accomplish with a server and rsync. What I'm really eager to see is git for everyone else.
  - exikyut 8y ago
    What would "everyone else" do with Git? It's a Rube Goldberg solution implementing a highly specific set of ways to do file versioning. Most cloud storage providers offer rudimentary versioning; are you referring to the idea of promoting commits to being first-class? It would need to be baked into Word, Excel and similar, and those tools already have builtin version tracking, as horrible(?) as it is, so... :/
    - Zak 8y ago
      People I know who definitely have this problem tend to work in creative fields - especially musicians and (digital) visual artists. They almost universally have a bunch of files with names like project_final2_revised_reallyfinal3_with_edits_from_sally.psd. Of course, a solution that works well with all the different binary file formats people in those fields use wouldn't be easy.
      - exikyut 8y ago
        Ah, that. Yes, absolutely I'd love for a solution that fixes that. It would definitely need to work with large files though, which categorically precludes Git. The first point, I think, would be building a delta engine with case-specific code for the most common ubiquitous file formats, like docx, xlsx, psd, etc. Of course it wouldn't be able to be perfect with everything but it would certainly be better than eg just recompressing each version or something equally naive. The UX would be the next major hurdle. Time Machine is a good example of the kind of simplicity that would be needed, but it would need to be a have a bit more surface area to be applicable and useful to all scenarios. One other feature that comes to mind, which would be incredibly difficult to get right but probably critical, would be useful version diffing. I think keeping this simple and just building something that can do $anything->SVG (with maybe cheats where bunches of the SVG is mostly just a bitmap in certain cases) and then doing something fast on the SVG (and/or its bitmap contents...) would probably be the most viable target.
        Zak 8y ago
        It think it does need branching and collaboration. There needs to be a way for Sally to contribute those edits, and they might not actually make it in to the final result. No doubt there would be a learning curve. I think that's OK. The target market here is serious users who already dedicate time to learning professional tools like Photoshop.
        exikyut 8y ago
        Oh no. Now you need full file format parsing so that you can resolve merge conflicts. :( That would take years to get anywhere with ._. The diffing idea I suggested above is just manageable, a la macOS Preview, with hacks. Branching requires folding-back-in, and that's not just a case of "A or B", it's a case of "A, B and C conflict with D and E, while F G and H are okay," where I could then say "save B and E but drop F". If B is a layer, E is an imported asset and F is a custom filter... you get the picture. You need a reimplementation of Photoshop (halting problem). :/ Sad that everyone hates GIMP. But... hmm, this could get folded into Blender, and then make the rest of the industry jealous.......
  - nlawalker 8y ago
    >> git for everyone else When you simplify and generalize git to the point where "everyone else" can use it, you get Apple's Time Machine and Windows' File History. I'm not that familiar with Time Machine, but if File History had a more visible interface that you could use to easily "checkpoint" individual documents or directories on demand, you'd pretty much be there. Branching is too complicated for most people to work with and overkill for most scenarios.
  - antoineMoPa 8y ago
    What about grep/sed/find for everyone else? Also, to get more ideas: echo "Make a startup with "$(ls /bin /usr/bin | sort -R | head -n 3)
api 8y ago
It really sums up nerds' lack of comprehension of the importance of user experience. It's like the UX version of the apocryphal "640k is all anyone will ever need."
- pjc50 8y ago
  The other famous one of those is "No wireless. Less space than a nomad. Lame." https://slashdot.org/story/01/10/23/1816257/apple-releases-ipod https://slashdot.org/story/01/10/23/1816257/apple-releases-i...
  - Alex3917 8y ago
    The first iPod was terrible though and sold poorly. The 3G was the first good model, and they didn’t start taking off until the 4G. History only proves that his analysis was completely correct.
    - gargravarr 8y ago
      3G was when they added Windows support. Probably coincidence :)
      - filmgirlcw 8y ago
        No, Windows support came with the 2G in 2002. iTunes for Windows wasn’t a thing and few Windows machines had FireWire, but the Windows-compatible iPod came out in 2002. The 3G was the breakthrough model, but I lend that as much to the dock connector (which was available in USB and FireWire) and the growth of x-platform iTunes as anything. The broader point that it required Windows support for the iPod to become mainstream is of course true. That said, the iPod was also the reason so many of us became Mac users in the early 00s because the “halo effect” was undeniable.
        mbreese 8y ago
        You're right. It really was the dock connector that made it a viable product for many people. The fact that the first iPods were Firewire (which I totally had forgotten about and I even had a 1G iPod) made it very difficult to make it work outside of the Apple ecosystem.
rayiner 8y ago
It’s a really great example of worse is better.[1] We went from sophisticated network file system to a daemon that destroys your battery life (at least on Mac) watching for file changes in a directory. [1] https://www.dreamsongs.com/RiseOfWorseIsBetter.html https://www.dreamsongs.com/RiseOfWorseIsBetter.html
- michaelcampbell 8y ago
  Your situation is different than mine; this is the first I've heard of Dropbox even registering as a top use of battery. How many files do you have? I've got 26000 files in my Mac's dropbox folder. (Granted, very few of them change more than once or twice a day; maybe 20 or so of those do.)
  - rayiner 8y ago
    I last used Dropbox in 2011 or so (I stopped using it because it killed my battery life). It may have gotten better since then. (But my point is addressed to what it takes to get popular, i.e. that its easier to make a “dumb” tool popular, and Dropbox was popular back then.) EDIT: Clearly not just me: https://news.ycombinator.com/item?id=12464901 https://news.ycombinator.com/item?id=12464901 (thread from 2016)
    - jonknee 8y ago
      Going out on a limb here, but I think it's possible things have changed in 7 years (and that it was probably something specific to your setup, not something millions of Dropbox users with a Mac had to put up with).
    - michaelcampbell 8y ago
      > i.e. that its easier to make a “dumb” tool popular, If this was your intent, then using the tired "worse is better" trope and claiming an issue from 7 years ago, that no one else has claimed to have seen is seems a far cry from it. Dropbox became popular because it was easy, it worked, and did exactly what it said it did. That might be "dumb" in that it's not feature packed, but you use a lot of negative connotations when none are required.
techopoly 8y ago
I thought it sounded familiar!
test6554 8y ago
The dhouston on that YC post is this guy now: Andrew W. Houston is an American Internet billionaire entrepreneur who is best known for being the co-founder and CEO of Dropbox, an online backup and storage service. According to Forbes magazine, his net worth is ~$3 billion.

michaels9876 8y ago

Or just use Google Drive

kbumsik 8y ago
Sorry, Google Drive doesn't support Linux.
- hatsunearu 8y ago
  https://abevoelker.github.io/how-long-since-google-said-a-google-drive-linux-client-is-coming/ https://abevoelker.github.io/how-long-since-google-said-a-go... And famously so.
- Fnoord 8y ago
  No official support, but you can easily access the content read/write in multiple ways. I've used such a few years ago with a FUSE module, written in OCaml. The only complicated, annoying thing was getting authentication to work.
  - kbumsik 8y ago
    I've heard of it but is that reliable? I meant I'm a bit afraid of loosing data by using unofficial programs.

yread 8y ago

Reference for the uninitiated: https://news.ycombinator.com/item?id=8863 https://news.ycombinator.com/item?id=8863

deleted 8y ago

[deleted]

deleted 8y ago

[deleted]

srslack 8y ago

More seriously: Syncthing exists, and it is beautiful. I set my grandmother up with Synctrayzor and she doesn't know the difference between that and Dropbox. It is missing the ability to share things with a direct link, or share a repository or folder "easily" (read: in the same way it's done with Dropbox), but the trade off has been worth it for me.

pjc50 8y ago
Which cloud backend do you have it sync to?
- vetinari 8y ago
  None. You run it on your machines and they will sync among themselves. No need for any cloud backend. Some people with Synology or QNAP run an instance on their NAS.
  - pjc50 8y ago
    But I (and I suspect quite a few other people) want a cloud backend to cover both the disaster-recovery cases and syncing while outside my LAN.
    - vetinari 8y ago
      1) you can sync with a device inside your LAN, even if you are outside, with global discovery (enabled by default). 2) you can run your own off-site instance, that can be hosted with your favourite cloud provider.
      - amyjess 8y ago
        > you can run your own off-site instance, that can be hosted with your favourite cloud provider. How much would it cost to hire an admin to set up and maintain that instance? The whole point of Dropbox is that I don't have to do any work.

pjc50 8y ago

The modern alternative is probably Syncthing. I intermittently maintain a list of these things at https://github.com/pjc50/pjc50.github.io/blob/master/secure-clouds.md https://github.com/pjc50/pjc50.github.io/blob/master/secure-... ; none of them have ever been precisely what I wanted. The cheap alternative to Dropbox with Linux support you want was "Hubic" from OVH (edit: now discontinued)

byproxy 8y ago
How about Keybase? It has a pretty seamless files experience, I find. Open source, end-to-end encryption, Windows client, painless sync, free for 250GB...
- bantunes 8y ago
  Stores your private keys, though.
  - byproxy 8y ago
    Well, according to this, they can't read your data. "These folders are encrypted using only your device-specific keys and mine. The Keybase servers do not have private keys that can read this data. Nor can they inject any public keys into this process, to trick you into encrypting for extra parties. Your and my key additions and removals are signed by us into a public merkle tree, which in turn is hashed into the Bitcoin block chain to prevent a forking attack. Here's a screenshot of my 7 device keys and 9 public identities, and how they're all related." https://keybase.io/docs/kbfs https://keybase.io/docs/kbfs
- ahnick 8y ago
  Completely agree. I'm not sure why someone would choose Dropbox over Keybase nowadays.
  - skrebbel 8y ago
    Continuity? I mean, does Keybase have a business model yet? Or is it still "$bigshot_vc who is friends with the CEO believes a few crypto/security gambles are in order"? Not meant critically, I love that they exist and found funding. It's just, as long as the model is "once the privacy shit hits the fan in some widely published scandal, we'll be the one that's ahead" there's only two outcomes: 1. It doesn't happen soon enough and Keybase runs out of runway, or 2. It happens, one of the many Keybase products becomes wildly popular because of it, and Keybase will ditch the others because "yada yada focus core business".

fuzzy2 8y ago

In case anyone is wondering if there truly is something like Dropbox (delta sync, desktop app, mobile app, web interface, ...): There is. It’s Seafile. The Docker image is reasonably easy to set up and run.

dekhn 8y ago

I spent about a year of my life trying to get WebDavFS (backed by apache mod dav svn) working. I want that year back.

ekianjo 8y ago

Or you can use Syncthing instead, you know.

csomar 8y ago

What? No! The whole idea of paying dropbox 10 bucks per month is to get a ready-made functioning solution. It is not like they are not implementing a feature but removing one.