in commentary, Internet, question |

I was reading TBL’s profile in Vanity Fair and I learnt of this new idea he is working on – an idea of “Socially Linked Data” (SOLID) – which wants to decouple data and the apps that consume them, thus allowing more data portability and data ownership. The profile itself was more focused on the persona and his Oxonian wispy hair (I can’t blame Vanity Fair for focusing on that, but I can blame them for not linking to Solid’s homepage or github on their site) so the above description is from Solid’s sites.

Has anyone I know used it or played with it? How does it differ from or relate to IndieWeb?

Also, how does this truly help in making our data more free? The value that Facebook and Google derive from our data is not from the data itself, but the linking of that data with other data, or the relations that said data makes within itself. I do not know the extent of the data that Facebook creates on me. That data, wholly solely is owned by Facebook. Even if I export large parts of data about myself using their export, including the data they’ve collected (such as the WiFis I connect to, the times I browse my phone, all the items I’ve left in carts of shopping sites that connect with Facebook), I still cannot, afaik, get my hands on the data they create on me. How will a solution such as Solid make that data less harmful?

Anyone care to comment?

Photo by willowbl00

I was once described as a philosopher programmer. I think I'd like to describe myself as a lifelong student.

Published

Updated

What do you think?

Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Webmentions

  • Back in 2012, I wrote a post called Conversations as a future of blogging. Well, I say I wrote, but actually I must have had a conversation on this up-and-coming platform called branch.com with a few people I invited to it from twitter. Using their tools, I embedded the conversation to my blog on the link above. I thought the embed would last forever, because a) where is branch going to go, and b) WordPress usually gracefully downgrades embeds, right?
    Nope. branch.com died three years after launch. They gave us a period of time to request backups of our conversations. I remember doing that, but I never received one in my email. Perhaps they expected me to come back to their site to download the files? I asked all the other people involved in the conversation and none of them cared to request a backup of the copy. This goes back to my posts here about the futility of exporting your data from online services, even though in this case, a full backup was exactly what I needed to recover my blog post.
    I was further wrong in that WordPress does no such thing with embeds. In the case of officially supported embeds, I’ve seen the system do this once before and I thought that was standard behavior, but in the case of link embeds, there’s no clear way for it to be possible.
    Recently, I introduced a random post finder to my blog. With it, I’ve been discovering a lot of great and terrible posts I’ve written over time. It’s my way of getting closer to my blog.
    But it has also left me reeling from all the broken links and embeds that I trusted to work forever. The branch.com embed, images and links I’ve linked to, PDF files I thought would never go away. Heck, even Facebook CDN stuff has disappeared and that company doesn’t let go of any data!
    Recently, Automattic introduced inline GIFs from giphy through Jetpack. The model they’re following is pretty neat – they shipped the Gutenberg editor within WordPress 5, and have been extending it using Jetpack with blocks that allow various kinds of content, including GIFs. It shows the scope that Gutenberg has in the future.
    Coming back to embeds, Giphy, the company Automattic is leaning on, came into existence in 2013, and I suspect will be out the door before its 10 year mark. Such is the way of life on the Internet. All of these are fads and fads can raise millions, but they eventually all die. Automattic will simply pull out the block from Jetpack and replace it with something else, but we users will be left with broken links and missing context on our blogs.
    When the block was introduced some time ago, I played with it and added some GIFs to a blog post. It’s a lot of fun to express ourselves visually. But if branch.com is any indication, embeds come back to bite us later on.
    Therefore, I’m getting off embeds. I’d rather download the GIF and upload it to my media. I’d rather take a screenshot of a webpage than to iframe it and hope it sticks around a few years from now. Jetpack already has a massive CDN operation behind them, so you’re never really serving your content directly from your site if they can help it. So there’s no need to worry about storage and bandwidth issues.
    As I go through my site, rediscovering old posts, I’ll keep coming across these embeds. Whenever I have context, I’ll try to replace it with relevant information. But, as in the case of branch.com, I will just put a note that explains what happened there, some general thoughts on the topic, and move on. Once bitten by embeds, twice shy now.