If you are aiming at creating a webapp you can simply use it with latest released version of the SAFE Browser, we don’t have documentation for API yet though, but you can see some examples API calls in this electron example app: https://github.com/bochaco/electron-neon-safe/blob/master/renderer.js#L13
Just note you should find the Safe object at window.Safe() for a webapp, so change that first line to let safe = new window.Safe(); and the rest of the JS API calls should work the same in your webapp as in that example.
Great update!
In relation to the data management is was wondering if it might be interesting to start implementing something like “groups”.
In our day to day life we have a lot of data as well that we share withouth explicit consent such as our name, work, hobbies, health issues etc. If we go to our doctor both parties understand the context of this visit and the doctor won’t share this data with parties that go beyond the shared understanding of this context, say an advertiser. But I do need to trust my doctor in sharing my medical information in case of an emergency.
Having fine grained control over your data is great but my observation so far is that the large majority of people simply doesn’t want to be bothered by such settings. Therefore it would be great if we could create a shared understanding of applications and in which context they belong and therefore if they could get acces to certain data.
If you want to keep sharing to a minimal you turn this off, and if you want maximum ease of use you use the common understanding of the network.
See this as a slider that moves from completely closed down to more flexible contexts. (you could always alter the permissions for one specific app of course)
@JimCollinson I don’t know how you do it but dammit you get it done and the end result is always amazing. That was a tall order you just ninja’d. And the mock ups look fantastic! Also props to @m3data
Late to the party, and much has already been said. Much praise deserved. Awesome = attention to UX, data hierarchy. Getting rid of Guarded and putting that responsibility on the app dev is a deep insight… love it when thinking through all the possible endgames makes things simpler. Did I just hear ‘digital bearer bonds on a private, encrypted, uncensorable global network’?
Great update, and seeing the UX side of things progress as well as the core network tech is brilliant.
I’d be up for another Glasgow meetup if others are.
I don’t think we should wait until any significant announcement due to uncertainties in timing - probably best to just book one and go for it, perhaps in February? Let’s discuss it in the Glasgow meetup thread.
Thanks for the kind comments folks. It’s most definitely just the first steps we are on here on the UX of data controls, plenty more complexity to layer up, but it feels like the right place to be, and hopefully it will bear some really useful fruit.
On a day off today, but looking forward to getting stuck in to the nitty gritty next week.
Cool to see the UI design work going in to the file permissions, thanks for taking the time to share those insights. Good to know it’s being very carefully thought out
DBCs sound like a Good Thing and I want them very soon.
BUT… IMHO DBCs should NOT be part of the MVE.
The devs are doing a fantastic job, lets not stretch them any thinner. DBCs should, if feasible, be part of a future upgrade. I don’t think they are part of the ‘M’ for Minimum in the MVE
And the mock ups look fantastic! Also props to 