Live data from Hacker News

Show HN: SlikSafe – A decentralized, end-to-end encrypted alternative to Dropbox

news.ycombinator.com

31–40 of 194 posts

Re: Show HN: SlikSafe – A decentralized, end-to-end encrypted alternative to Dropbox

#31

Earlier quoted context omitted.

Are you looking for Syncthing? https://syncthing.net/

I am looking for syncthing but with an iOS app.

Has iOS just not been implemented yet or is there a technical hurdle?

Re: Show HN: SlikSafe – A decentralized, end-to-end encrypted alternative to Dropbox

#32

An e2e Dropbox alternative would be great. Though for it to actually count as a Dropbox alternative (to me) it would need: 1) a Linux app 2) an Android app 3) on-demand syncing, aka "smart sync"

Are you looking for Syncthing? https://syncthing.net/

Syncthing doesn't do smart sync. The library of stuff I want available is larger than can fit on my phone.

Re: Show HN: SlikSafe – A decentralized, end-to-end encrypted alternative to Dropbox

#33
post #17
post #11

Isn't it impossible to really delete something from ipfs? I'd think that would make this dangerous, as any security flaw would be impossible to fix retroactively. Everything before the flaw would be compromised and can't be reencrypted safely. If a passphrase was lost, the security of every past file would be at risk. This is what has kept me from approaches like this in the past.

Can you really delete anything from NSA servers? Or from Internet in general? For me the problem with IPFS is - it is just not interesting enough. It's not a storage solution, it is distribution and caching mechanism. You can't really upload to IPFS, you can only publish via IPFS - the same way you publish via HTTP.

I am quite confident that the NSA does not have a complete image of the encrypted data in my self-hosted Nextcloud instance. With IPFS they wouldn't even have to do anything, if they sometime in the future were able to break the encryption.

Re: Show HN: SlikSafe – A decentralized, end-to-end encrypted alternative to Dropbox

#35
post #31

Earlier quoted context omitted.

I am looking for syncthing but with an iOS app.

Has iOS just not been implemented yet or is there a technical hurdle?

There was a propriety implementation a few years ago (written in Rust of all things), but I think it's dead.

I think the bigger problem is that both iOS and Android are doing everything they can to deprecate the concept of a filesystem. Android has a history of killing filesystem features, receiving tons of developer backlash, and then hacking in workarounds with reduced performance. I think the writing is on the wall.

In my experience, porting general purpose tools to Android is a nightmare.

Hopefully something like pinephone gets good enough before things are too bad.

Re: Show HN: SlikSafe – A decentralized, end-to-end encrypted alternative to Dropbox

#36

So, how does this compare to a solution like Bittorrent Sync? And, perhaps more interestingly, why would this become popular where BT Sync failed to live up to the hype? Furthermore, storage can be paid for by crypto. Does this mean the storage is linked to some kind of cryptocurrency, or is there some kind of central payment system that converts crypto into actual value in the system?

It seems btsync (Resilio) has had minimal development over the last few years. I used to be a huge fan but had to stop using it since I kept hitting weird SQLite errors and all support channels seemed dead

Re: Show HN: SlikSafe – A decentralized, end-to-end encrypted alternative to Dropbox

#37

Congrats on the launch! Your implementation of sharing from the whitepaper scares me. The second that the private key travels anywhere it's no longer safe in my opinion. This is why Signal uses the double ratchet and 1password has their own sharing. Unless I missed something.

Great point! We integrated the QR-code and link based sharing into the app to provide a seamless experience for users.

However, we also have an email sharing solution already integrated into the app which uses public-key cryptography. This is protected from accidental leaks as you correctly pointed out.

Thanks for the feedback, we would update our WhitePaper with the details from above, and also indicate that to users in the UI - so that it scares people less! ;)

Post reply on HN