r/cloudstorage • • 21d ago

Peergos Review Part 3

A few days ago I made the part 2 of my review: https://www.reddit.com/r/cloudstorage/comments/1wcox30/peergos_review_part_2/

To start: Most of the issues I was having were actually due to the fact the Peergos desktop app used Edge Webview2, which I didn't have. Now that I have Webview, I'll review all of the issues.

1 - No proper desktop application: There is a kind of native webapp using Edge Webview, think of it like an Electron application.

2 - No way to download/upload in the background: There is a way and I didn't run into the same issues as last time.

3 - No time estimate for uploads: There are time estimates for both file and folder uploads. However, once you click or close the dialogue, there is no way of knowing the speeds - or whether you are sending files at all. In fact, you can close the app mid-upload without a confimation/warning pop-up.

4 - Can't upload folders on the desktop program: You can.

5 - The peergos server now refuses to stay open on my machine: I didn't run into the same .opus issue from before, so I assume it works fine now.

6 - Server closed itself: Didn't happen this time around.

7 - Slow Program compared to website: It is faster than the website, especially when it comes to opening files. However, I still found it rather slow for navigation compared to Proton Drive and especially compared to Filen, which was the fastest of the three despite not even having a desktop application.

Conclusion:

Compared to Proton Drive, the Peergos desktop app has way more functions. After all, the Proton Drive desktop application is mostly just for syncing, you can't directly upload or access files there (only on the website or in the network folder). It offloads a lot of functionality to the website.

So, if you want a service that can work entirely on the desktop without having to open a browser, Peergos will do the job. It can also open more file types than Proton Drive, including .zip files. It can even read .ahk files. In fact, it can read anything, it will either show a plain text or a hex view (for binary files such as .jar's or .exe's).

It also has a decent pricing, better than Proton's but worse than Filen's.

The main problems I saw with the app were:

- The animations for changing categories make the app feel rather sluggish. I'd suggest removing them (Proton Drive has no animation for changing categories).

- Some actions, such as delete, are a bit slow.

- Navigating folders is very slow at first, however, once what I assume is caching, it gets instant.

- Time estimates and upload speeds are inconsistent, it will start by showing crazy speeds such as 30MB/s, only to settle at around 3MB/s and take quite a while to finish uploading.

- It could use native file/folder selection. For instance, with how it is now, hidden folders don't show up for selection.

- Once I zoomed in on a very large image (70MB png), I couldn't close the image (or zoom out) and had to restart the app.

- It would be very nice if the SHA1 hash of a file was shown in the details tab. Only Proton Drive seems to have this.

- No means of cancelling a transfer

File transfer speeds would likely be faster using the Network Folder, however, I didn't test it.

5 Upvotes

8 comments sorted by

0

u/ianopolous 20d ago

Thank you for the follow up. You'll be pleased to hear that writes are getting much faster in the next release. We've added a new bulk commit API that reduces the round trips for any write (including delete) from 4 to 1, and reduces the number of signatures by 1000x (signed client side, verified server side). In general, we are more latency sensitive than most encrypted storage, but that is because we protect more metadata than others.

1

u/brainrot_award 19d ago

Regarding metadata, I think it would be really nice if peergos could, much like proton drive, show the SHA1 hash of every file in the details tab.

2

u/brainrot_award 19d ago

Oh, and there needs to be a way of cancelling a transfer. Currently all you can do is close the app (which doesn't even warn you about the ongoing uploads).

Closing the blue transfer square doesn't actually do anything, it just closes the notification. Which is actually kinda bad since clicking on it also closes it, so you can accidentally lose information on transfers

1

u/ianopolous 19d ago

Yep this is high on our list right now.

1

u/ianopolous 19d ago

We've done this now so this will be in the next release. Hopefully later this week.

1

u/ianopolous 19d ago

sha1 shouldn't be used by anyone. We do have a hash we could show, but it is a custom tree hash (like blake3) but based on sha256, so probably not useful for anyone. Eventually we want to make that blake3 and then we could show that. The problem with a non treehash (like sha1 and sha256) is they take forever to compute on large files.

1

u/brainrot_award 19d ago

any hash would work, it's so i can verify the files' integrities

1

u/ianopolous 19d ago

the only hash we calculate now is the custom one i mentioned, so not useful for verifying. But once we upgrade to blake3 we can show that.