The layoffs cut the streaming music site’s work force by about 40 percent and could be a way to make it more attractive to a buyer.
What is a rel=”me”?
Rel=”me” is a microformat tag put on hyperlinks that indicates that the paged linked to is another representation of the person who controls the site/page you’re currently looking at. Thus on my home page the Facebook bug has a link to my facebook account which is another representation of me on the web, thus it has a rel=”me” tag on it.
His data is a bit old as I now maintain a page entitled Social Media Accounts and Links with some (but far from all) of my disparate and diverse social media accounts. That page currently has 190 rel=”me”s on it! While there was one other example that had rel-mes pointing to every other internal page on the site (at 221, if I recall), I’m proud to say, without gaming the system in such a quirky way, that each and every one of the rel=”me” URLs is indeed a full legitimate use of the tag.
I’m proud to be at the far end of the Zipf tail for this. And even more proud to be tagged as such during the week in which Microformats celebrates its 12th birthday. But for those doing research or who need edge cases of rel-me use, I’m also happy to serve as a unique test case. (If I’m not mistaken, I think my Google+ page broke one of Ryan’s web crawlers/tools in the past for a similar use-case a year or two ago).
The Moral of the Story
The take away from this seemingly crazy and obviously laughable example is simply just how fragmented one’s online identity can become by using social silos. Even more interesting for some is the number of sites on that page which either no longer have links or which are crossed out indicating that they no longer resolve. This means those sites and thousands more are now gone from the internet and along with them all of the data that they contained not only for me but thousands or even millions of other users.
This is one of the primary reasons that I’m a member of the Indieweb, have my own domain, and try to own all of my own data.
While it seemed embarrassing for a moment (yes, I could hear the laughter even in the live stream folks!), I’m glad Ryan drew attention to my rel-me edge case in part because it highlights some of the best reasons for being in the Indieweb.
(And by the way Ryan, thanks for a great presentation! I hope everyone watches the full video and checks out the new site/tool!)
A hazy day for Tumblr. A shoe dropped. After a year of dancing around, the Yahoo (Tumblr owner)/Verizon deal closed. There were immediate layoffs across their new Frankenstein org, “Oath.” Some of these layoffs hit inside Tumblr, and that’s bad. In addition to the real life talented human beings impacted by these layoffs, the move is a warning and reminder- Tumblr is no longer in the protective purgatory of pre-Verizon Yahoo.
I’ve been watching or on Mastodon since about October of last year. While it does have some interesting/useful features that differentiate it from the rest of the corporate silos, in some senses it’s got worse problems.
Average users are still putting blind trust in the (mostly/completely anonymous) administrators of the individual federated versions–and these are even more likely than well financed corporations, which have some reputation to maintain, to do questionable things with your data. These individuals are also taking on the financial burden of hosting and storing all their users’ data in addition to continually building and maintaining the platform itself. As a result, you’re setting yourself up for potential disappointment yet again, unless you’re going to set up and run your own Mastodon instance. (Especially since there’s no contract for them to maintain their instance on your behalf–they could literally turn it off tomorrow if they liked. Here’s link to a great article comparing and contrasting how well or poorly some communities are run to give you an idea of how drastically different they can be.)
Since January I’ve also been following a project called Micro.blog which is expected to be released in Beta next Monday, April 24th to its Kickstarter backers. It’s an inexpensive paid service that will provide a domain and hosting to those who don’t want to manage those things themselves. Most importantly, it is built on open protocols with a decentralized architecture which will give you greater control of both your identity online, but also ownership of your data. Because of its structure, it’ll also be inter-operable with other platforms like WordPress. In some senses, it takes the Mastodon federation structure and flattens it down an addition level to the point that it’s much easier for the average user to have their own personal version of the service so they’re more self-reliant in many respects and far less reliant on corporate entities. Since it’s a paid service, the level of service will likely be better than the free services offered by silos like G+ where the user (and their data) ultimately become the product.
This said, I still believe a more future-proof long-term alternative is to have your own domain and post your content on it first. This will still allow you to syndicate it out to one or more social media silos to reach individual audiences who still choose to use them. Because it’s your own site, you’re far less constrained by what an outside corporation might dictate, and you have a lot more freedom and control.
John, since I’d mentioned the indieweb movement to you last, it’s come a long way, particularly on CMS platforms like WordPress and Known which both support the W3C spec for webmentions (you can now use your own website to @mention people all across the web who also support the spec), and can use Brid.gy to backfeed all the interactions (comments, likes) you have on Facebook, Twitter, Google+, Instagram, and Flickr back to your original post so it appears the entire conversation around your content is on your own site. Last week I actually wrote a small piece about setting up functionality for having @mentions from Twitter come back to my own website, which is just a small piece of this type of functionality.
When you (or others) have time to chat about potentially implementing something like this, I’m happy to walk you though a few demos and help you set things up to better support all this new open technology.
If anyone wants to test-drive WithKnown, I’ve set up an open instance at http://known.boffosocko.com where you can register and try out some of the basic functionality. I haven’t completely finished setting up all the configuration options for the major social media sites including a new one for Mastodon, but the settings should allow one to OAuth with Twitter to cross-post content there and then one can register (in the settings) with Brid.gy to backfeed replies and likes. I’ll also recommend installing the browser bookmarklet to make interacting with it easier for bookmarking and replying to things.
Next month, two seminal image-sharing communities, FFFFOUND! and MLKSHK, will close their doors within a week of each other. There's a profound difference in how they're doing it as noted by someone who's previously sold off a community.
Next month, two seminal image-sharing communities, FFFFOUND! and MLKSHK, will close their doors within a week of each other. Launched in June 2007 as a side-project by a Japanese design agency, FFFFOUND borrowed the visual bookmarklets of Wists, a social shopping service launched a year earlier, to...
In a project which I started just before IndieWebCamp LA in November, I’ve moved a big step closer to perfecting my “Read” posts!
Thanks in large part to WordPress, PressForward, friends and help on the IndieWeb site too numerous to count, and a little bit of elbow grease, I can now receive and read RSS feeds in my own website UI (farewell Feedly), bookmark posts I want to read later (so long Pocket, Instagram, Delicious and Pinboard), mark them as read when done, archive them on my site (and hopefully on the Internet Archive as well) for future reference, highlight and annotate them (I still love you hypothes.is, but…), and even syndicate (POSSE) them automatically (with emoji) to silos like Facebook, Twitter (with Twitter Cards), Tumblr, Flipboard, LinkedIn, Pinterest, StumbleUpon, Reddit, and Delicious among others.
Syndicated copies in the silos when clicked will ping my site for a second and then automatically redirect to the canonical URL for the original content to give the credit to the originating author/site. And best of all, I can still receive comments, likes, and other responses from the siloed copies via webmention to stay in the loop on the conversations they generate without leaving my site.
Here’s an example of a syndicated post to Twitter:
👓 Physicists Uncover Geometric ‘Theory Space’ | Quanta Magazine https://t.co/HuKg1d4a80
— ChrisAldrich (@ChrisAldrich) February 23, 2017
R.I.P Vine. So long, Meerkat. Rest in power, Sports Authority. This was a rough year all the way around.
Ah, Vine. I loved the idea of a platform for sharing tiny video moments. It was truly a platform for some really amazing things.Personally, I didn't make ver...
This is a message to all Readability API key-holders. Here’s what’s happening:
After more than five years of operation, the Readability article bookmarking/read-it-later service will be shutting down after September 30…
I am glad that bookmarks are one of the post types that I’m now saving by posting on my own site first though. For more of my thoughts on these post types, take a look at: