Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Twake Drive – An open-source alternative to Google Drive

github.com

Post reply on HN
Print view View original

131–140 of 219 posts

Re: Twake Drive – An open-source alternative to Google Drive

#131

Post by toomuchtodo »

orliesaurus wrote: post #106

Lots of talk about must‑have features and backups here... BUT there's another piece that makes or breaks these tools... whether they can build a community around them and stick around for years... Open‑source cloud storage projects come and go when maintainers burn out... a sustainable business model or strong contributor base matters as much as technical checklists... ALSO interoperability is underrated... if your d…

Indeed. "S3 compatible" is the state of the art for object storage imho. As long as you can talk to a storage system that supports the basic S3 primitives, longevity is improved and there is no lock in. You can use S3 proper, Backblaze, Wasabi, Backblaze B2, local storage exposing an S3 api, etc. Any replacement is mostly drop in assuming it can read, scan, index existing objects.

Edit: @n3t heard wrt to the turn of phrase

Re: Twake Drive – An open-source alternative to Google Drive

#132

Post by n3t »

toomuchtodo wrote: post #131
orliesaurus wrote: post #106

Lots of talk about must‑have features and backups here... BUT there's another piece that makes or breaks these tools... whether they can build a community around them and stick around for years... Open‑source cloud storage projects come and go when maintainers burn out... a sustainable business model or strong contributor base matters as much as technical checklists... ALSO interoperability is underrated... if your d…

Indeed. "S3 compatible" is the state of the art for object storage imho. As long as you can talk to a storage system that supports the basic S3 primitives, longevity is improved and there is no lock in. You can use S3 proper, Backblaze, Wasabi, Backblaze B2, local storage exposing an S3 api, etc. Any replacement is mostly drop in assuming it can read, scan, index existing objects. Edit: @n3t heard wrt to the turn of…

https://en.wikipedia.org/wiki/State_of_the_art

Re: Twake Drive – An open-source alternative to Google Drive

#133

Post by [deleted] »

n3t wrote: post #132
toomuchtodo wrote: post #131

Earlier quoted context omitted.

Indeed. "S3 compatible" is the state of the art for object storage imho. As long as you can talk to a storage system that supports the basic S3 primitives, longevity is improved and there is no lock in. You can use S3 proper, Backblaze, Wasabi, Backblaze B2, local storage exposing an S3 api, etc. Any replacement is mostly drop in assuming it can read, scan, index existing objects. Edit: @n3t heard wrt to the turn of…

https://en.wikipedia.org/wiki/State_of_the_art

[deleted]

Re: Twake Drive – An open-source alternative to Google Drive

#134

Post by Tade0 »

3idet wrote: post #75

58.9% TypeScript and 32.6% JavaScript wouldn't be my first preference to implement such a high performance and throughput demanding application? Why is that?

It appears that the backend is written in TS, while the frontend in JS.

Personally I separate church and state by writing tests in JS and application code in TS.

If you're asking why these languages at all when this and that other language is faster, most likely it's less of a bottleneck than estimated.

Re: Twake Drive – An open-source alternative to Google Drive

#136

Post by CaptainOfCoit »

g-b-r wrote: post #124
CaptainOfCoit wrote: post #115

Earlier quoted context omitted.

> Why do you think it's embarassing? I don't? I said I remove it because it isn't useful to anyone, might even be adding more confusion than it solves, not because I'm embarrassed over anything.

If it really isn't useful, which I imagine means you committed somewhat haphazardly, ok, of course. If there might be some usefulness hidden there (for example, trying something and then reverting it shows that you did explore it), it's also possible to place the old stuff in another repository or another branch (better the latter, unless it increases the repository's size too much)

> for example, trying something and then reverting it shows that you did explore it

True, those things tend to go into the documentation itself, checked into the codebase itself instead of being somewhat hidden inside the git history. Usually I end up having both a "Open Problems" (things yet to solve) and a "Tried X, this is why it didn't work" section somewhere in the documentation.

> it's also possible to place the old stuff in another repository

Yes, before the process I initially described, I usually leave a copy intact with the full-full history, but that's not what I published, just kept as an archive.

Re: Twake Drive – An open-source alternative to Google Drive

#137

Post by wobfan »

juchilov wrote: post #121

Seafile is the only good enough thing i've found so far for self-hosted file sync. But it is still a pain to upgrade the server version. nextCloud and friends is a complete disaster in my oppinion.

> nextCloud and friends is a complete disaster in my oppinion.

Why is that? Have been using NextCloud in our company and for myself, and I couldn't be happier, no issues since 3 years, all the tools and plugins I need, sync running perfect and hassle-free and performant. I thought it's generally liked up until now - I didn't try any of the alternatives though, so they might indeed be better. Though I don't have any reason to try them tbh, as NC works almost too well.

Re: Twake Drive – An open-source alternative to Google Drive

#138

Post by keoneflick »

Gigachad wrote: post #5

Is this a fork of something? Or recently open sourced? Looks like there is a single commit where a majority of the code came from.

They were originally working on a MS teams replacement, with a bunch of things in one app like teams. (I tried it back then, it was pretty green). Now it looks like they are focused on drive, chat and email. The old app seems deprecated, so I presume they forked it into some of this new stuff.

Re: Twake Drive – An open-source alternative to Google Drive

#139

Post by wobfan »

wewtyflakes wrote: post #119
aborsy wrote: post #107

Earlier quoted context omitted.

No, it was serious! He complained about the difficulty of installing an application. He didn’t complain about establishing a personal data center. That one line will give you the Nextcloud. Exactly one more line in snap will give you a self sign cert. Alternatively, the line below will give you remote access, a domain, and a valid certificate for your application: curl -fsSL https://tailscale.com/install.sh | sh You…

It seems reasonable that someone would want to go beyond just installing software; they are presumably doing so in order to use it for its purpose. Being pedantic about the nature of the complaint (i.e. "He complained about the difficulty of installing an application. He didn’t complain about...") seems to miss the point. All of the additional steps you lay out also have their own steps to get done or decisions to be…

I mean if you want a working Nextcloud instance, available through VPN with backups, then no, it doesn't get more complicated than that, actually. It is incredibly easy.

Re: Twake Drive – An open-source alternative to Google Drive

#140

Post by raybb »

ekjhgkejhgk wrote: post #116
ptman wrote: post #90

There's also https://cryptpad.fr/ - https://cryptpad.org/ - https://github.com/cryptpad/cryptpad

That looks great, thanks for sharing. I would add to that list something like a splitwise alternative. And open source too? Seems too good to be true.

I think you're looking for https://spliit.app/
Post reply on HN