The Data Transfer Project was formed in 2017 to create an open-source, service-to-service data portability platform so that all individuals across the web could easily move their data between online service providers whenever they want.
The contributors to the Data Transfer Project believe portability and interoperability are central to innovation. Making it easier for individuals to choose among services facilitates competition, empowers individuals to try new services and enables them to choose the offering that best suits their needs.
Current contributors include: Facebook, Google, Microsoft, Twitter
The Data Transfer Project makes it easy for people to transfer their data between online service providers. We are establishing a common framework, including data models and protocols, to enable direct transfer of data both into and out of participating online service providers. http://datatransferproject.dev
cross reference: https://boffosocko.com/2018/07/22/data-transfer-project/
In what way are avatars a privacy risk? To display an avatar image, you publish an encrypted version (MD5) of the e-mail address in the gravatar’s image URL. Gravatar.com then decides if there is an avatar image to deliver, otherwise the default image is delivered. The default image’s address is also part of the overall gravatar …
I’m going on the journey of building a simple, private, self-hosted, cookie-free analytics tool that I’m calling Kownter. I may fail. But it will be fun and interesting! Come along!
Hi, My name is Ross. I’ve been thinking a lot about GDPR lately and considering how I will become compliant with it as I run my business and projects, so I’m looking to slim down the data that I capture about people.
The topics of both analytics and server logs have come up several times. It’s not entirely clear to me that either fall into the category of personal data, but I’ve been considering my use of them anyway.
I use Google Analytics on most sites/projects that I create, but I’m not that sophisticated in my use of it. I’m mostly interested in:
and it occurred to me that I can collect this data without using cookies and without collecting anything that would personally identify someone.
- how many visitors I’m getting and when
- which pages are popular
- where people are coming from
I would also be happier if my analytics were stored on a server in the EU rather than in the US – I can’t find any guarantee that my Google Analytics data is and remains EU-based.
I’m aware that there are self-hosted, open-source analytics solutions like Matomo (previously Piwik) and Open Web Analytics. But they always seem very large and clunky. I’ve tried them and never got to grips with them.
So I wondered: how hard would it be to build my own, simple, high-privacy, cookie-free analytics tool?
According to the company, it can't separate content posted before and after the age of 13.
Another solid reason why to be a member of the IndieWeb.
Here’s a reminder to export or back up your social data, or better yet post it to your own site first and syndicate it to social silos you don’t have direct control of second.
In the run-up to Friday’s launch of the new GDPR privacy protections, most of the focus has been on how it will affect huge data-mining tech giants like Google and Facebook. But as many people are finding out today, GDPR applies to any site that collects user data or, in the case of publishers like Gizmodo Media Group, displays advertisements that collect this data. What that really means in practice is extremely complicated.
It’s the “morning after”: a mere twelve hours have passed since the GDPR applies and while still awaiting breaking news on hobbyist blog owners being fined EUR 20 million, an army of burnt-out web and legal professionals has begun to clean up from the party that was “the final dash towards GDPR”.
A nice article pushing folks to focus more on the privacy portion of the discussion rather than the non-nonsensical technical GDPR regulations.
tl;dr: Do unto others as you would have them do unto you.
Since tracking people took off in the late ’00s, adtech has grown to become a four-dimensional shell game played by hundreds (or, if you include martech, thousands) of companies, none of which can see the whole mess, or can control the fraud, malware and other forms of bad acting that thrive in the midst of it.
And that’s on top of the main problem: tracking people without their knowledge, approval or a court order is just flat-out wrong. The fact that it can be done is no excuse. Nor is the monstrous sum of money made by it.
Some interesting thought and analysis here on the pending death of adtech with the dawn of GDPR in the EU. I’m hoping that this might help bring about a more humanistic internet as a result.
There’s a lot to unpack here, but it looks like some tremendously valuable links and resources embedded in this article as well. I’ll have to circle back around to both re-read this and delve more deeply in to these pointers.
Summary: With the GDPR regulations coming into effect in Europe on May 25th, privacy seems to be on everyone’s mind. This week, we tackle what webmentions are, using them for backfeed, and the privacy implications.
Related Articles and Posts
- The Indieweb privacy challenge (Webmentions, silo backfeeds, and the GDPR) by Sebastian Greger (n.b. the comments here are worthwhile as well)
- Webmention Specification
- Philosopher reference at the end of the episode: “I want the whole world.”
Related IndieWeb wiki pages
I admit to a certain amount of frustration on the subject of privacy lately. It seems, in all aspects of my life, both personal and professional, the new data privacy regulations that the EU rolls out May 25th are a theme in every discussion.
Some interesting thoughts on personal data and privacy. I can’t wait to talk to David about some of this in greater depth in our next podcast episode.
Sebastian, first of all, thank you for your detailed write up on this issue. I think much of your roadmap is worthwhile, and of great interest.
I cannot, however, say that I am convinced by your contentions regarding the effect of GDPR and indieweb sites. In particular, I think your definitions are excessively broad, and you elide much information from both the Regulation itself and the Recitals.
It’s certainly interesting to see some of the replies to Sebastian’s article. It’s definitely stirring up some interesting thought. Daniel’s reply here is primarily to the legal issues at stake more than the design related issues, which have some interesting merit aside from the legal ones.
I think I fall somewhere in the middle of the two and see some of the moral and ethical pieces which are more important from a people perspective. I’m not as concerned about the law portion of it for a large variety of reasons. It’s most interesting to me to see the divide between how those in the EU and particularly Germany view the issue and those in the United States which may be looking at regulations in the coming years, particularly after the recent Facebook debacle.
As I think of these, I’m reminded about some of the cultural differences between Europe and the United States which Jeff Jarvis has expounded upon over the past several years. Europeans are generally more leery of corporations and trust government a bit more while in America it’s the opposite.