Live data from Hacker News

Inrupt, Tim Berners-Lee's Solid, and Me

schneier.com

171–180 of 183 posts

Re: Inrupt, Tim Berners-Lee's Solid, and Me

#171
post #90

Earlier quoted context omitted.

As soon as you grant access to some data in your pod to someone, they can make a copy and then it's out of your control. I don't see how you can govern it unless you just never grant access.

You still control the original and they control the copy. If it’s hosted on their service you don’t control anything.

The copy is identical, so I think functionally there's no difference between those. Your data is out of your control either way.

Re: Inrupt, Tim Berners-Lee's Solid, and Me

#172
post #170

Earlier quoted context omitted.

If analytics are beneficial to customers, why aren't they opt-in but instead businesses try hard not to let them even opt out?

this question makes no sense. since on street analytics are already beneficial to everyone, consumers and providers, why should they be opt-in? they should be, and currently are, automatic opt-in with an option to opt-out. you are walking on the street, so any privacy is gone just from walking outside of your home.

What doesn't make sense is to consider never leaving the house a realistic option. Nor does the phrase "automatic opt-in".

And I hope this:

> since on street analytics are already beneficial to everyone, consumers and providers, why should they be opt-in?

is a joke. It's pure authoritarianism.

Re: Inrupt, Tim Berners-Lee's Solid, and Me

#173

I have mixed feelings about Solid. I really love the ideas behind it, and having Tim Berners-Lee (big name in tech) at the helm is a huge plus. However, I have some trouble with some of the technical choices, like RDF/Turtle. Given that most web developers are familiar with JSON, and many web APIs / services talk JSON exclusively, I feel like that should be the default recommended choice. Given that there is a lot of…

Note that currently, the Solid spec mandates both RDF/Turtle and RDF/JSON (JSON-LD). That said, it's perfectly possible for an app to read/write any data format they choose, but RDF deals with some challenges regarding data discovery and interoperability, and allows for more granular updates with smaller payloads.

(I also work at Inrupt, though views are my own.)

Re: Inrupt, Tim Berners-Lee's Solid, and Me

#174
post #45

I am very excited about Solid. That motivated me to write my thesis about a decentralised wiki, where Solid is its foundation. For further information, you can have a look at my work journal ( https://ma.parrillo.eu ).

I'm very excited about your thesis! It's great you found a topic that you love. Keep at it! Any chance we can get rss for that blog of yours? :)

As a heads-up, it's been added: https://ma.parrillo.eu/rss.xml

Re: Inrupt, Tim Berners-Lee's Solid, and Me

#176
post #169
post #82

Earlier quoted context omitted.

> extremely beneficial to both consumers What "extreme benefits" do I derive from being filmed and analyzed by stores I happen to walk past?

you get better products. the store gets better sales. it's a win win all around. this is already happening and it's already providing value.

How do you get better products?

What does a filmed image give you that isn't reflected by sales numbers?

The goal of tracking isn't to make and sell better products, the goal is to create an environment in which the product you already got gets sold more. So essientially people who track you want to manipulate you into buying shit you don't need at prices you wouldn't pay unless manipulated.

Tracking people who would buy your product anyways isn't all that interesting: you've already got them.

Re: Inrupt, Tim Berners-Lee's Solid, and Me

#177

Earlier quoted context omitted.

> Nothing is recorded. In some cases, processing even happens at the edge. If the data is not processed at the edge, how is nothing recorded? This smells like extremely minced words. IANAL (definitely not a German one) but I'm almost certain that even post-2017 it's still illegal to take video in a public space and send it elsewhere, without a sign, even if that video is not in some sense "preserved" elsewhere.

If data stays in RAM and is not written to permanent storage, I think you can reasonably say it’s not recorded. Frankly, I think you could even persist it to disk as long as it was pruned within 24 hours and reasonably say it’s not recorded. Otherwise I’m not sure how you can argue ANY data is “unrecorded”. Writing to a hardware buffer in the camera module would seem like “recording” to me by the strict standard.

Ah yes, the "NES ROM" theory of public surveillance laws. Definitely well-considered.

Re: Inrupt, Tim Berners-Lee's Solid, and Me

#178

Earlier quoted context omitted.

Not saying this is not hard, but I assumed (without having read into it) that the protocol solid itself is much more low-level than that. What you're describing sounds more like owncloud's level of operation: we host email / we host pictures I'd expect Solid (or any competing protocol) to provide very low-level access to "data" in some form. A third party (let's call them smail) would then provide the service "send a…

"Crucially, the value that service adds would not be hosting and backing-up of your email, but rather just the interface and functionality" Yeah but doesn't that create a problem, vendor lock-in. Let's imagine we managed to separate data into 2 parts (which I suppose pretty hard), content and meta-data ( by meta i mean service specific information ) Let's say, if I label an email in gmail, it is meta (service specifi…

I think of solutions like Solid more like traditional filesystems. Many file formats exist for things like images, and yet there are lots of apps that work with these formats.

Re: Inrupt, Tim Berners-Lee's Solid, and Me

#179
post #81
post #22

Solid's goal is nice but its solution ia based on RDF and semantic web. Those technologies failed to take off for a web 3.0. I dont see this going to take off either. Turtle is just another syntax for RDF because XML is too verbose.... Anyway i do see a lot of value in IPFS, its solving a different problem, but it's related. It could allow for storing private data encrypted in a non centralized way, having the pinned…

I am inclined to be skeptical of semweb technologies as well, and certainly I think there are many in the Solid community that look at it as a sort-of second chance for it. However, I do think many of the reasons I think it failed the first time around might not apply in the case of Solid, where it's used for modeling just personal data stored in a place under the user's control - which comes with its own unique chal…

I'm interested in hearing more about this.

Re: Inrupt, Tim Berners-Lee's Solid, and Me

#180
post #90
post #78

Earlier quoted context omitted.

Well for one your data lives in a place where you can govern it. Nowadays your data lives in all places you use (Facebook, Gmail, Twitter). Ever tried taking stock of your data lately? It can take weeks to do it for all services and importing the exports into a self hosted alternative is nigh impossible. Still one risk I am seeing is that services might still want to intern you once you have given than access to your…

As soon as you grant access to some data in your pod to someone, they can make a copy and then it's out of your control. I don't see how you can govern it unless you just never grant access.

It might make it easier to regulate. If you revoke access and can prove you own the pod the data originated from, it provides a way for a sort of "individual DMCA".
Post reply on HN