📑 The Indieweb privacy challenge

Bookmarked The Indieweb privacy challenge (Webmentions, silo backfeeds, and the GDPR) // Sebastian Greger by   (sebastiangreger.net)

Originally intended to showcase a privacy-centred implementation of emerging social web technologies – with the aim to present a solution not initially motivated by legal requirements, but as an example of privacy-aware interaction design – my “social backfeed” design process unveiled intricate challenges for Indieweb sites, both for privacy in general and legal compliance in particular.

As someone involved in K-12 education, I always wonder where the #IndieWeb might sit. This analysis of webmentions and privacy from Sebastian Gregor poses so many questions and things to consider. I was particularly intrigued about the questions of dragging in ‘likes and favourites’ which might be used and interpreted in different ways.

From an ethical design perspective, however, I still have a stomach ache thinking of publishing the name and image of unknowing Twitter users on an unrelated website, presenting a “like” potentially intended as a bookmark of a short tweet as a “like” for a long essay on some blog site they have never visited. Here, too, some kind of transparency/consent mechanism would be required; and while I am sorry to not have a ready solution to offer, the idea of simply warning about a backfeed in a sticky post on top of a timeline is not really something I consider sufficient. Likely, the solution for the silo backfeeds would have to come after a solution for Webmentions in general has been developed.

Just thinking about my own use, I usually use the ‘Like’ post-kind to recognise posts that I find interesting, but do not have anything to add (that would be a bookmark.) This does not mean I ‘like’ the post or agree with everything written. This is where confusion can occur.

I think this is one of those posts that I will come back to as my knowledge of webmentions and the #IndieWeb continues to grow and evolve.

Leave a Reply

Your email address will not be published. Required fields are marked *