We’ve been working on this in our spare time for 5 years now. Super excited to hear what people think.
for others, who like me were not familiar with the tool, I found this brief intro useful:
You can think of Peergos as a cross between Dropbox, email, Facebook, YouTube and Twitter, but fully end-to-end encrypted and decentralised to keep your data and social graph private.
My questions for @ianopolous would be
a) can I use the technology without singing up for anybodys’s central service
b) can I host some content (eg my resume) on my mobile phone (android), and what would happen when phone is off (eg, is there caching?) , if not there yet – is that planned?
c)how can my resume (as example noted in b) can be discovered/searched by others
d) can it be deleted? forever?
e) I did not know fully understand appreciate the social network aspect – is that like mastodon or something else?
thank you for sharing
Thanks for your questions. Yes you can self host Peergos and then your instance will be responsible for storing all your data. When you sign up you communicate with a global pki to claim your username. We chose the UX tradeoff there because that’s what people are used to.
Currently there isn’t any guaranteed caching (though if someone else views your file, ipfs should cache it on their instance temporarily. Longer term we hope to let you mirror your stuff on your friend’s nodes.
Only people who you grant access (read or write) to a file can see it. You can also create a public link to a file which anyone can use to view it, without needing to install or sign up to anything, e.g.:
You can delete your files yes. That was a core requirement. It should behave like a global filesystem.
At the moment the social side is quite primitive, you can share files and folders (read only, or writable) with other peergos users who follow you (and revoke said access, which means rotating keys and re-encrypting). We plan to add many-to-many messaging ala Signal, and later a more traditional social feed as well. The whole thing is independent of DNS or the TLS certificate authorities (unless you choose to use a public web interface) so there’s no need to get a domain name and manage all that complexity if you want to run your own instance. (You can access your instance from elsewhere still without DNS or TLD using ipfs’s p2p streams which are E2E encrypted independently).
About your problem of not having writablestream available on firefox, maybe you can use serviceworker instead.
Thanks for your suggestion. We’re already using service workers, but that’s not sufficient to download a file larger than you can fit in memory. As far as we’re aware there is no solution other than writable streams. For more information see https://github.com/jimmywarting/StreamSaver.js
I eventually understood.