Avatars from Gravatar.com are great, but they come with certain privacy implications. You as site admin may already know this, but your visitors and users probably don’t. Avatar Privacy can help to improve the privacy situation by making some subtle changes to the way avatars are displayed on your site.
The plugin works without changing your theme files if you use a modern theme, and it does support (simple) multisite installations. It requires at least PHP 5.6 and WordPress 4.9. For the plugin to do anything for you, you need to visit the discussion settings page in the WordPress admin area and save the new settings. Please note that the plugin does not provide an options page of its own, it rather adds to the existing discussion settings page.
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.Syndicated copies to:
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.Syndicated copies to:
I could have sworn I filed this as an issue before myself, but I’m not seeing it in the queue. Perhaps I mentioned in chat somewhere?
Simple location’s privacy setting seems to override the post’s public/private settings on my site as well. Perhaps it’s a naming conflict (function/filter/etc.) with WP’s core content visibility code?
In any case, I can’t make a post private while Simple Location is installed/activated either. This seems to happen regardless of other plugins. I do seem to be able to use @vishae’s method of using the quick edit option to change a post to private. I’m not sure if this may indicate a potential solution to the issue based on what is firing on a post save/update versus what fires on a quick edit save.
Additionally, I don’t seem to be able to mark a particular location as “private” in a post either as upon saving it it defaults back to public in the UI. I only seem to be able to use “public” or “protected” options for locations.Syndicated copies to:
The same DNA analysis used to find the alleged Golden State Killer has led to the arrest of a second alleged murderer. It’ll likely lead to more.
I can see this going to the Supreme Court sooner than later on privacy related underpinning. I can’t help but recall the words of Jed Bartlett in The West Wing when he was saying in season one that privacy would be one of the most pressing issues for the Supreme Court in the coming century.Syndicated copies to:
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.Syndicated copies to:
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.”