Biomedical and Electrical Engineer with interests in information theory, evolution, genetics, abstract mathematics, microbiology, big history, Indieweb, and the entertainment industry including: finance, distribution, representation
I've read that it was something they tested out last year in select markets around Mother's Day. It's possible that it was brought back today again for Mother's Day on a limited basis.
Interestingly these "loves" (and I suspect other reactions) from Facebook aren't parsed as webmentions (I'm guessing by semantic linkbacks plugin) as the comment_type in wp_comments is empty rather than "webmention", but they are assigned a semantic_linkbacks_type of "reply". I suspect that this is why they're not categorized in the webmention section. I'm not sure what the bug is for giving all the names the same URL....
And this is where I start to get really mad. Like many others here, I have invested a lot of personal time and energy building a following here. Like many of you, I have poured heart and soul into filling this place not just with great content, but also with a sense of community. I could have made those investments in Twitter or Facebook or reddit, but like many of you, I made them here. And now I'm starting to wonder how smart of a decision that was.
I'm in the same boat with you Jeremy. Each silo certainly has it's own set of functions, personality, and even audience. For me, Facebook and Instagram are more close friends and family, LinkedIn work-related, Twitter and Google+ generic town squares for interacting with people I might not otherwise meet in real life, and Foursquare/Swarm/Nextdoor are for interacting (albeit, not much) with neighbors and people in my geographic vicinity.
Twitter is almost too short in some sense while platforms like Mastodon, pnut, and 10C give more length and often feel more like chat rooms (or IRC or old multi-person instant messenger) interspersed with Twitter-like status updates. There's also a difference in who you're communicating with and which of your audiences they fall into (friends, family, real life acquaintances, internet friends, people with similar interests, etc.). Some of it comes down to interface, space given, and the organic nature of how the people in those communities choose to use them. Though Mastodon is very similar to Twitter, it's the more conversational direction that the users and community who are actively using it push it into that will determine some of its fate--certainly an interesting topic of study for cultural anthropologists.
Another thing I find interesting is their relative sizes. The smaller they seem to be (or perhaps closer to the Dunbar number of users they have) the more conversational and less "post-y" they feel. While I might syndicate some articles or status updates to some of these more chat-like services, I don't feel as much like syndicating all of my chat to them--at least until I could make my personal UI easier to use to do that, and that portends to be quite a way off.
As I bring up Dunbar's research, I also realize there are only so many slivers of the web that I can mentally keep up with at any given time. The closer I come to posting on my own site and interacting that way, the lower my cognitive load seems to become. I no longer spend time in or visit some of the major silos 3-10 times a day anymore since those interactions come back to me in a more natural way.
@miklb I literally started an outline of a post today entitled "How WordPress could improve the world while eating Facebook’s Lunch" as I was having a chat with David Shanske over IM. The outline essentially had three bullet points and one of them was really just a bonus. I'm sure it'll take a day or two to flesh things out, but hopefully it will get to the heart of the same idea you're writing about.
Jonathan, perfect, the new version fixes the issues with the content showing on the permalink.
The separate, but somewhat related issue is that the post interface still shows all of the UI for syndicating to all of the options (facebook, twitter, WordPress, Tumblr, LinkedIn, etc.), yet choosing those options doesn't actually syndicate the content. (Typically I wouldn't POSSE these post types anywhere anyway, but other users may expect this piece to work if it's shown.) I know some post types in Known hide the syndication targets when they're not supported (ie, only audio related posts can be syndicated to soundcloud), but I'm not sure how these are done.
Interestingly, when editing these types of posts, the syndication targets (correctly) aren't shown in the editable version.
Join some like-minded people in building and updating your personal website.
Location: Starbucks, 4430 York Blvd., Los Angeles, CA 90041
•Work on your IndieWeb Resolutions for 2017
•Finish that blog post you’ve been working on
•Demos of recent IndieWeb breakthroughs
•Share what you’ve gotten working
•Ask the experts questions
Join a community with like-minded interests. Bring friends that want a personal site.
Any questions? Ask in chat: http:/
Optional quiet writing hour starts at 18:00 (Pacific)
Add your RSVP in the comments below, by adding your indie RSVP via webmention to this post, or by RSVPing yes to one of the posts below:
Indieweb.org event: https:/
The IndieWeb is a growing people-focused alternative to the ‘corporate web’.
Duplication of links upon update · Issue #45 · dshanske/syndication-links https:/
With v3.1.1 and relying on SNAP for POSSE, I'm noticing that after publishing and syndicating, if one comes back and edits a post and then updates it, Syndication Links regrabs the URL's and duplicates the links.
The first unedited version that is shown seems to be a plain http link and after editing/updating, the second duplicated link that is added automatically is an https version.
Manually deleting either of the included links from the Syndication Links box doesn't get rid of the links.
This duplication of the links only happens on posts which have been later edited/updated.
Here the Twitter and Facebook links, which are generated from SNAP, are duplicated, first as http and then again as https. As a test, the two other syndication links are non-SNAP generated links: huffduffer was manually inserted, and the WordPress one was generated from the WordPress Cross Post plugin, so I'm guessing it's an issue caused by the storage of SNAP links (which are https) versus Syndications Links' storage.
I'm curious what you've tried that you've now abandoned? I've tried a handful of methods and haven't been very happy with many of them myself.
JetPack's publicize is seemingly the simplest of the lot, but gives almost no control over the end result, so either you like it or you don't. Bridgy Publish plugin has gotten much better recently, but my theme has some quirks to it that need some work to get things there working smoothly. Most recently I've been using Social Network Auto Poster which has a huge number of POSSE targets, but also requires a lot of set up time and configuration (and also relies on other plugins like All in One SEO or Yoast to set appropriate Open Graph Protocol metadata so that versions that get sent to Twitter/Facebook display exactly what I want them to--and even then it's not always 100%. I've been tempted to try Keyring next, but I suspect it'll be much of the same convoluted dance.
If most of my readership wasn't hiding in the silos, I think I'd give up on POSSE too. I can't wait until the broader idea has completely taken over to the point that syndication is a useless function.
Scott, I don't think I'd replied to you for some reason, but I think I'm generally in the same boat as you. While I prefer to have one Swiss Army knife-like tool that can do everything, I know that it just isn't going to happen, or at least it certainly isn't quite there yet. I use Twitter and Facebook for different things (primarily audience based), so I suppose I shouldn't expect to have my own site do exactly everything I want it to.
Part of the problem is that I don't have the skills, the time, or maybe even the patience to make my own site do everything I'd like it to (and if I did maintenance can be a bear), so sometimes picking up pieces of things here and there from other developers or even on other platforms seems to be the result. In some sense that's why I'm using both Known and WordPress simultaneously (along with a few other side projects which don't fit into either of those). WordPress does a lot of what I'd like, but the speed, simplicity, and ease-of-use that Known provides just couldn't be overlooked to give me more of what I wanted. Over time, I do find myself moving more and more under the WordPress banner, but I always hear the siren song of other tools calling, so it may never be under one umbrella.
I also find that using other tools lets me test drive UX, UI, and general functionality to see if it's something worth building, maintaining, or having myself. And even then, I like to do "manual until it hurts" to raise the bar a bit further.
I'd noticed this a few days ago too as it seemed to have fixed an issue they'd had previously with the Facebook URL they displayed in the admin interface that didn't work, but was different from the URL that Syndication Links picked up. I mostly noticed because when using the SNAP buttons after initial publication they give modals showing success in posting which include the returned URLs, which for some silos can make it easier to cut and paste if necessary.
Your solution sounds like a sound one.
Your other thought recently about storing the URLs separately from SNAP's store is a good one as well because I've noticed (and generally not cared, though others surely may/will) that if one re-syndicates a post with SNAP, it overwrites the prior URL with the new one, which means that Syndication Links wouldn't have a "complete" list of all POSSE copies. This also means that Bridgy will only return replies on the most recent one for each silo this is done in. Anyone using SNAP's scheduling feature will be losing some of their backfeed as a result.