To ask the obvious: once a user shares their data, isn't the genie out of the bottle?
Seems like there is nothing to stop a service from perpetually storing all data that is shared with them once. In the long term, this would negate any benefit enjoyed by users since users who share their data no longer have "full control" over it (to use the verbiage found on the site's Users page).
You are totally right. Still, the platform could be considered a step in that direction. For example, a further improvement of the terms and conditions could at least force the services to agree not to store any data. If I manage to find at least a service willing to use the platform and some users, it's definitely something to look into.
Edit: I will improve the landing page in the near future, to better show the purpose of it and also to make it less vague.
Nice, last year i wanted to work in that direction. Cool to see someone actually started.
If you ever need someone helping out, let me know. I habe many thoughts about a project like this and where this should go.
You make a very good point here. Solid is obviously a considerably more advanced version of what I tried to do here. The main motivation for my project was to ease transactions like registrations, logins and any other
forms of identification or information sharing. Like in the case of Solid, my idea was to try and standardize data by
organizing it by topics & keys.
The main differences compared to Solid, would be the non-decentralized data storage (smartphone) and the active user involvement in each data sharing transaction, meaning the user has to actively scan a QR code (later other forms can be added like NFC, etc.) for the data sharing to take place (as opposed to Solid, where data can be read indefinitely by an app until access is revoked). An extra thing that Qodebeam provides is (user-supervised) write access, meaning a service can also request to save something in the user data store.
Overall, I'd say it's just a (slightly) different approach to the problem of personal data ownership and sharing.
Maybe something that would work well as an intermediate step towards something more advanced like the Solid offering.
I hope it makes sense.
This could very well be used for that IMHO. Other uses could be recruiting platforms, online shops, etc. It's not yet a mature project, but in theory, it can be used for anything that needs user data of any kind.
Yes, if you have an iPhone. I didn't find time to complete the android app, but I'll probably do it soon. Should be easy enough since the app is written with react native.
11 comments
[ 2.9 ms ] story [ 41.5 ms ] threadSeems like there is nothing to stop a service from perpetually storing all data that is shared with them once. In the long term, this would negate any benefit enjoyed by users since users who share their data no longer have "full control" over it (to use the verbiage found on the site's Users page).
Edit: I will improve the landing page in the near future, to better show the purpose of it and also to make it less vague.
The main differences compared to Solid, would be the non-decentralized data storage (smartphone) and the active user involvement in each data sharing transaction, meaning the user has to actively scan a QR code (later other forms can be added like NFC, etc.) for the data sharing to take place (as opposed to Solid, where data can be read indefinitely by an app until access is revoked). An extra thing that Qodebeam provides is (user-supervised) write access, meaning a service can also request to save something in the user data store.
Overall, I'd say it's just a (slightly) different approach to the problem of personal data ownership and sharing. Maybe something that would work well as an intermediate step towards something more advanced like the Solid offering. I hope it makes sense.