upspin VS Peergos

Super intriguing. Thanks for sharing!

It reminds me a bit of an early Go project called Upspin [1]. And also a bit of Solid [2]. Did you get any inspiration from them?

What excites me about your project is that you're addressing the elephant in the room when it comes to data sovereignty (~nobody wants to self-host a personal database but their personal devices aren't publicly accessible) in an elegant way.

By storing the data on my personal device and (presumably?) paying for a managed relay (and maybe an encrypted backup), I can keep my data in my physical possession, but I won't have to host anything on my own. Is that the idea?

https://upspin.io/

There are a few Go projects meant to be learned from:

- https://github.com/pion/opus for to learn audio

- https://github.com/benbjohnson/wtf for overall production quality

- https://github.com/upspin/upspin difficult to explain, personally I'm not a fan of the errors

You could also take a look at some real-world open-source projects. I like upspin for its idiomatic approach.

For example, Rob Pike's upspin places all its validations in the separate package. Do you agree with that approach? Which yet proven options there are?

Just a few projects that could perhaps interest you in terms of design of your own solution :

Upspin: https://upspin.io/

The early error wrapping work which emerged out of the Upspin project, that eventually made its way into the errors package, included stack traces in the wrap error. This would provide exactly what it appears you seek.

A good Dropbox alternative is Peergos (founder here). Peergos is an E2EE P2P storage, sharing and application protocol. Fully open source, including the server, self-hostable, no VCs.

https://peergos.org

You can do that with peergos [1]- mount a peergos folder locally using FUSE. Or login to the web interface and share easily and privately.

[1] https://github.com/peergos/peergos

You might be interested in the p2p design of Peergos. You sign up to Peergos[0]. Your initial server is just responsible for storing your data (although you can run as many live mirrors as you like), and clients verify all updates. You can automatically move server (by running a command) and all your data is moved, and old links continue to work, and you keep your social graph and identity.

You can also log in through any instance, including localhost. Links also work on any server because they include a capability to the content in the link.

This is the beauty of content addressing plus public key based addressing.

[0] https://peergos.org

Totally agree! Shameless self promotion: have a look a Peergos - https://github.com/peergos/peergos

Our tech book might be a better starting point for this group: https://book.peergos.org

https://peergos.org

https://book.peergos.org

https://github.com/peergos/peergos

Features:

* audited by Cure53

* protects metadata (directory structure, file name and properties, file sizes, social graph)

* fine grained capability-based access control

* built-in social media

* sandboxed 3rd-party apps: e.g. word doc viewer, calendar, text editor, games etc.

* FUSE bindings

* CLI

* cross platform

* browser client

I use Peergos[0] for E2EE storage, doc editing, sharing media, calendar, kanban boards and social media. (Disclaimer: I also work on Peergos).

[0] https://peergos.org