The first solid reference implementation was written in Go. We had a pod (databox.me) where people could come and try out solid.
But this was still not ideal, because the test server did not provide a permanent home for people wanting to create a WebID and storage. On the web, URIs gain a reputation over time, and there is enormous benefit from having a stable home for your URIs, stable data, and a stable server. Anyone that has moved a WebID from one place to another knows that it is almost impossible. I know very well from experience, moving my own WebID from http to https took several years, and still, today is not fully complete.
As I had been collecting solid domains over time, one from my personal collection was solid.community. I felt this could be a great domain for users to create long-lived identifiers for people in the community. I ran the idea past timbl and he liked it, and after some persuasion, the solid.community pod was born. Eric and I ran it, I think on a box sitting in MIT at first, but then later on digital ocean, where it runs today. I think we should revisit hosting soon, with an aim to become self-sustaining. The pod predates inrupt, and when inrupt launched some inrupters kindly helped out with running and updating the software.
So, that's where we are today. Going forward, what I would like is for solid community to be run by the community, if that's possible. We've been going for two years and we'd like to go as long as possible. I created this repo to document some of these things and to provide support for users who were getting frustrated with being locked out of their pods
I'm not paid and have never been paid to work on solid. Those kindly helping with this repo are volunteers, and we could do with more help. The more volunteers we have the better we can help out users, and longer we can keep going
So what would we like the ToS to convey
- We are community-owned and community-run and community administered
- User privacy is our core value
- We believe users have complete sovereignty and agency over their own data
- Our aim is to create stable, long-lived identities and long-lived storage space
- Ultimately our goal is to become self-sustaining, and provide a model for other communities
Budget and resources
So we are not 100% on a sustainable path right now, but our costs are low. I pay the cost to renew the domain. I also get a free SSL certificate from letsencrypt. We have a small relatively low-cost instance on digital ocean. So we are in survival mode this year. The larger cost is in terms of time with people helping to support and admin users, fix bugs, perform upgrades etc.
Term of Services
Hopefully, we can use this information as a basis to create a ToS. Templates look great, but we should probably ask permission before reusing the text of others. Ultimately we would ourselves like to provide a template so that many other communities can host their own pods leading to a distributed system of pods for individuals and groups
- How to delete a file Data-Browser guide
- I cannot login : error ???? Clear your browser cache
- I cannot access my POD
Have you tried to edit the root ACL => your
.aclmay be broken => File an issue for admin help
- Error 401 : You do not have the access rights to this resource.
- error 403 : origin unauthorized
Means that the origin of the app is not trusted.
Add origin to trusted app => with the
manage your trusted applications
- error 409 : conflict If you were trying to delete a folder => the folder is not void. If you don't see any file in your folder it means there are orphan.acl files => File an issue for admin help
- error 500 : it is a server error
How to fix a broken root ACL
(the file may or may not not exist).
.aclfrom another pod
edit the acl :
nano .acland replace the
pod owner's webId
Fix other broken ACL (.acl or file.acl):
for badNamedAcl like .acl$.any_ext :
mv badNamedAcl .acl
for malformed content ACL :
To help the user understand the origin of the problem, you can :
cp badAcl to acl.txt
How to reclaim a subdomain
- Go to the
datadirectory and delete or archive the directory
rm -r de.solid.community
- Go to the
.db/oidc/users/users/directory and remove