31–40 of 263 posts
It also recommends the use of some XML thing so that all your "contact" objects are the same format.
I really would like to support this, but I seem to miss the big picture. Looking at the github repos, Solid appears to be mostly about giving a second life to TBL's and W3c's failed pet projects, notably semantic web, linked data, RDF, SPARQL, JSON-LD.
They didn't fail for not being useful, but because their engineering was clunky and their demands on resources were way beyond the hardware of the time. Also those systems were too complex for the classic programming techniques. Now that we have a better understanding of reactive programming and async dependencies, maybe we can finally build the tools ecosystem to take advantage of homoiconic data, and these systems can take off.
I get that its great when its working and secure, and I can control it. But exploits happen, and now all my data is in one place.
I'm on mobile, so please excuse my innacurracie, but from memory how it works is pretty simple. A solid server is sort of like Dropbox. everything is a file, and you can give apps read-write access to a "folder". It also recommends the use of some XML thing so that all your "contact" objects are the same format.
Maybe I am just naive, but this all seems terrible. There are paragraphs of ideology everywhere for every aspect of this and nothing boils down to any understandable description of what engineering mechanisms I can use or how it solves the problems laid out. I really want to like this, but if I spend 15 minutes clicking the guides, the “build a solid app on your lunch break” link, and going all over the site, and I s…
Tim Berners-Lee is as finished as Woz. We should stop giving him air time because he's just embarrasing himself. Reminds me of this recent story with Michael Atiyah.
I mean, in spirit I seem to value the same things as Solid (decentralized, own your data, etc.), but what I don't understand is why it has to introduce so many abstract/new names when it wants to be 'simple'?
Building on top of the Semantic Web concepts isn't going to help either as it has enough disadvantages of its own (e.g., complex standards without adding any real value).
I hesitate to call it outright bad, but I have no idea what to do after I create a pod. And I'm someone who knows how to write Solidity.
Maybe I am just naive, but this all seems terrible. There are paragraphs of ideology everywhere for every aspect of this and nothing boils down to any understandable description of what engineering mechanisms I can use or how it solves the problems laid out. I really want to like this, but if I spend 15 minutes clicking the guides, the “build a solid app on your lunch break” link, and going all over the site, and I s…
Tim Berners-Lee is as finished as Woz. We should stop giving him air time because he's just embarrasing himself. Reminds me of this recent story with Michael Atiyah.
applications :( Does anyone else feel nostalgia for the pre-"web app" days of the internet? I'm talking about personal sites on Geocities and web rings built on communities of shared interest. The browser was an application for navigating hyperlinked information. Other applications include email clients, news readers, FTP clients, and IRC clients. You never had to download a megabyte of minified JavaScript just to re…
As exciting as those days were, I wouldn't want to go back to dial-up, CRT monitors, no-broadband, no-wi-fi, no-wikipedia, no-dropbox, no-stackoverflow, no-git, no-digital-distribution, etc.
Interesting idea, but I'm interested in the security implications. Now I have a Pod that has all my data in it, and I can host this pod anywhere I want. Great, but its now the single target for getting all data on me. I get that its great when its working and secure, and I can control it. But exploits happen, and now all my data is in one place.
So in terms of security, you can choose to trust a 3rd party with hosting your data, keeping the apps etc up to day or you can host it yourself. I'm not sure what's better!