Open haasn opened 7 years ago
This is a really cool idea! I don't think I've seen it posted publicly before, but I'm sure it's something that's at least come up to the dev team--especially considering the main audience of Keybase.
I really hope it's on the roadmap.
For a quick example of what I was thinking of, it would be possible to use a format not unlike the git-LFS infrastructure to store “pointers” to server-backed files rather than storing the files directly, together with their filesize and hash.
Edit: Note that this concept might need extending to meet the needs of multi-user shared private directories, since the backing server would need to store encrypted files in that case.
Is there any update on this? I'm also interested.
Bitwarden's open source model is interesting.
Self hosted app is limited unless you "install" a "certificate" that is signed by Bitwarden...........
However you could comment out two or three lines and open up everything... but because it is GPLv3, you would also need to provide the source showing your misdeed if anyone asked for it.
Open sourcing backend is veeeery tricky... but bitwarden is a good project to watch to see what a very useful app that is open sourced on front and back end can do financially.
Well I think that the servers could sign each other and cross authenticate like mastodon
Apologies if this is a duplicate feature request, I found no issues under the term “self hosted”.
What I would like is the ability to self-host my kbfs backend - for stuff I upload, using my own quota and my own server, so I don't have to rely on the “generosity” of a service like keybase.io providing me with “free 10GB” that may or may not disappear in the future.
I'm not sure how this would work internally - but I imagine it would be something along the lines of running my own “kbfsd” on the server in question and then somehow proving that it's mine (or at least, linking it to my config somehow). After this, files signed by me would be uploaded as some sort of reference to this server instead, so clients trying to access the file would request it from there instead.