Alternate Sharing Buttons (Now with Less Tracking!)

Posted on March 30, 2018

I’ve been trying out some alternate sharing buttons that don’t talk to Facebook, Twitter, etc. — or to a third-party button provider like ShareThis — until you actually click on the button. Facebook can track you across the internet when sites include the standard “Like” button hosted on their services. Same with Google and the +1. Even WordPress’ Jetpack buttons will call out to Facebook and Pinterest to display the share count. I want to reduce my contribution to ubiquitous tracking.*

Sharingbuttons.io is totally self-contained and doesn’t even use any JavaScript. You use their site to generate a set of buttons for a particular page, then copy the HTML and CSS to your site. Downsides: The HTML includes embedded SVG that has to be repeated on every page, and your page title and URL are repeated in each button within the page. I used this set on the old Alternative Browser Alliance site, replacing ShareThis. It’s only around five pages, so it was faster to repeat the generator five times than write a tool to template it.

Share42 uses locally-hosted JavaScript to avoid repeating the title and URL on every button, and a single image sprite generated from the set of buttons that you choose. You copy both files to your own site, so that it doesn’t contact a third-party server just by appearing. This also made it simpler to add to WordPress, because I only need to add an easily-templateable stub and enqueue a local script. So I put it on Speed Force, replacing Jetpack’s sharing module. I may put it on the old Flash reference site (which used to have ShareThis on it) if it seems like it’s worth it.

These are both topic-based projects. For my personal blog here, I’ve decided to just drop the share buttons entirely. I’m not sure how useful they are these days, anyway, especially on mobile, where sharing to an app is built into the system.

*Yes, I said reduce, not eliminate. I’m still using WordPress stats, for instance, though I’m phasing out Google Analytics on my personal sites, and of course anywhere you actually embed content from another site, the remote site can potentially track your visitors.

Link Sharing and Source Trails

Posted on February 8, 2018

Kelson

I read a lot of articles in one of two ways:

Open a bunch of tabs and then read them one at a time
Save a bunch of interesting-looking stories to Pocket and then read them one at a time

So by the time I’ve decided to share a link to the story on Facebook Twitter, Mastodon, etc., I’ve often forgotten where I saw it to begin with.

If it’s a site I follow regularly, or I found it through a search, or if it was recommended by Pocket, no big deal, but if someone else shared the link and I saw it, I feel like I ought to give a little credit.

Now, the share/retweet buttons do automate this trail…but only if you do it immediately on Facebook or Twitter, because they have a nasty tendency to update your timeline when you come back, making it difficult to find the post you clicked on.

So anyone notice how twitter actively discourages you from reading an article before RT it? I read, take my time, and when I go back, the tweet I was reading is “gone”, pushed down my timeline.
— Lee Skallerup Bessette makes zero magic (@readywriting) January 1, 2018

(It took me 30 minutes to find this tweet, since I couldn’t remember who had written it, only who on my list had retweeted it.)

This encourages you to share articles before you read them, no doubt contributing to the problem of people sharing stuff that turns out to be total BS, sending it halfway around the world before the truth can get its proverbial pants on.

I’m not sure how much people care about the trail these days. Citing the original source? absolutely. Posting someone else’s idea as yours? Hell yeah, just search for “stolen tweets.”

But the intermediary? Whether you follow the person you retweeted, or you follow someone who follows someone who follows someone who retweeted them, it looks the same to the rest of the world. Back when reposts and linkblogging were done manually, it was a BIG DEAL. I remember people getting upset that big-name bloggers would share links to things that smaller bloggers had already shared without crediting them. (Admittedly, I don’t remember whether it was a common complaint or just a few people.)

On the other hand, if you’re studying the spread of ideas, opinions, information or misinformation, it’s invaluable. And if you’re trying to hide a propaganda operation, you might want to disguise the trail…

But social media users do care about share counts and like counts. Original posters want the validation. Viewers see high counts as social proof that other people find the post valuable. And the platforms themselves use it as a signal to prioritize display in the newsfeed algorithm du jour. So there’s a strong incentive to get people (or bots) to use those share, reblog, retweet buttons.

So when it comes down to it, the normal use case preserves that link trail (even if you only see the oldest and newest links in that chain)…and I’m just an outlier when it comes to the way I use social media.

Web Intents

Posted on August 5, 2011

Kelson

Cool idea: Google is designing a “Web intents” system for web apps similar to intents in Android. For those who haven’t used Android, “intents” allow apps to register actions they can take — such as “I can share (or edit) images!” — and other apps to hand data over to them. That way your camera app doesn’t need to know about every possible image-sharing or editing app you can put on your phone.

Now they’re extending the idea to web applications. There’s a JavaScript-based proof of concept, and they’re planning to add native support to Chrome.

Originally posted on Google+

Update: While it would have been cool, Web Intents never got off the ground. Paul Kinlan describes what happened.