Ruben Verborgh
Ruben Verborgh
> My question is, how should a developer reverse that transformation? In a standard web application with centralized data, you have already saved the previous state of the application in...
> However, there are many apps that doesn't have an explicit save button, and it often shouldn't be necessary. That of itself shouldn't make a difference. I realize that I've...
That might be hard, as services can change their usage of analytics products whenever they want. Would it be helpful to instead point people to proper protection software, such as...
> So how about creating a form by writing RDFS or ShEx? We are very actively investigating this in the context of Solid. Will transfer this issue there.
@perploug Is that you? 😮 (Umbraco, 10 years ago?)
@perploug Great to hear back from you! The interesting backstory here is that I left the Umbraco project to focus on my PhD research on Linked Data, which eventually lead...
Updated databox.me to use "not accepting new users" phrasing.
(Continued from #151 where @melvincarvalho and I were discussing.) > > Edge case indeed, but it has major architectural consequences. All current Solid client s> ftware assumes that the user...
> Should this say something like, "For a given origin, at any given time, solid client side apps and libraries (that I know about) assume that the user is identified...
So coming back to: > WebID-OIDC was proposed to run alongside WebID-TLS, not to replace it. So there's going to be push back if that is changed. What this implies...