Biomedical and Electrical Engineer with interests in information theory, evolution, genetics, abstract mathematics, microbiology, big history, IndieWeb, mnemonics, and the entertainment industry including: finance, distribution, representation
Here's a list of sites within the Fediverse that report supporting Webmention:
https:/
I'm not sure if Aaron Parecki has a public list of all the sites that are using webmention.io, but that would add a huge number as would all the native sites that are part of micro.blog. I'm not sure if either publishes a list of sites using their services for a variety of reasons.
@benwerd @benwerd@mastodon.social It would be cool if they could easily expose numbers of interactions (reads, replies, bookmarks, etc.) as a signal in a way such that social readers could filter using this data along with tags/categories for prioritizing what we might want to read.
Selfishly they could use these signals internally for better measuring engagement with articles and particular writers. Is it high quality engagement (useful comments, reads) versus lower quality engagement (bookmarks which might indicate "I read the headline and might be interested").
Highly enterprising publications, and especially "local" publications/newspapers, might consider offering IndieWeb as a Service to allow their readers the ability to have their "own platform" within the publisher's platform/stack. This could be done on a co-op basis or potentially even bundled into subscription prices. Something along the lines of Kinja perhaps, but with more ownership/control/ability to move. Or perhaps a white-labeled version of something like micro.blog, but run/managed by the NYT, WSJ, other?
A well tummeled version of the Hometown fork of Mastodon with "local only posting" could be an engaging thing for a sophisticated newspaper or magazine to create. The publication could have closer control/moderation of the local posting for article related conversations, but people could still communicate with others outside of that "home" server. Alternately, in the standard Mastodon model, the "public timeline" could be filtered for posts about or commenting on the outlet's own content and all other content goes into the federated timeline.
Publications offering their own microsub social reader interfaces could be fun and clever. It could be an interesting way to have a more streamlined reading experience for paid subscribers among other potential options. This could be an interesting interface for helping people build a truly custom reading experience specifically for them, particularly for larger newspapers with large amounts of content that could be better filtered and personalized to individuals.
@TerribleMia You've got your own site and control your URLs, so you're definitely on it! And you've got Webmentions for additional icing on the cake. Kudos! I'm glad you've managed to get things set up and working for yourself. It definitely helps to have small bite-sized pieces of technology to rely on to get it all going.
You're right that it's a lot of work on individuals, but there are some emerging platforms/providers attempting to make all of this technology easier on the general public who don't have the time, technical skills, or desire to maintain any of their own systems. Micro.blog is one of these options to be sure. A few others can be found here: https:/
Congratulations again!
This morning I find myself wondering what is the longest post that has ever appeared on micro.blog? I'm hoping it's not me... #WallOfText
@edheil Because of the IndieWeb principle of plurality, you've got a tremendous amount of choice. Part of the issue is that there are SO MANY options and potential combinations of doing things.
What do you want the site to do? How much admin time to you want to spend on it? How flexible and modifiable do you want it to be? What skills do you have? What skills do you want to work on?
Both of the options you mention are excellent, though there's probably more immediate flexibility in WordPress with plugins. If you want something with no admin, but still some reasonable flexibility then micro.blog is a great way to go. (All three support a very broad range of all the IndieWeb building blocks. Of course, this doesn't even touch the custom-built or static site generator spaces which are also available options. And who's to say you should only have one site? ;)
This is a great question to ask in the IndieWeb Dev chat channel for advice from a bigger group of people with a tremendous wealth and diversity of building experience. https:/
@alexwilliams Micro.blog is an inexpensive turnkey IndieWeb friendly solution for doing something like that. Bring your own domain or subdomain and you're off to the races with all the benefits and none of the overhead or work.
@MarcoInEnglish micro.blog sends/receives them, but only from sites that are registered to its own userbase as I recall.
@matpacker There's some documentation at https:/
I also suspect that some of the WordPress/iOS crowd hanging out in micro.blog may have some experience with this.Searching in chat may reveal more: https:/
Here's an example of a reply from an entirely different website that isn't affiliated with micro.blog or WordPress--It's running the WithKnown CMS.
Congrats on getting two-way conversations going on your website.
@noahread @madebydusk @manton2 @m_ott @CraftCMS
It depends on what data you want back into Craft. Most just want the replies/comments. Micro.blog does this via webmentions, thus the reason for having the webmention plugin set up to collect those replies.
@madebydusk @CraftCMS I think @m_ott has experience (and a plugin) with the webmention portion: https:/
The micro.blog portion should hopefully be as simple as inputting an RSS/JSON or other feed. @manton2 may possibly know of others.
@sadlerjw You've certainly found a few of the remaining pain points within the broader community and specifically with WordPress. There are obviously some UI bits like properly threaded conversations across multiple syndicated silos that could be better. I've written a tad about how threaded comments work between sites using WordPress, though didn't touch on the idea of doing so also using Twitter or micro.blog: http:/
Ideally in the end, everything would support Webmention and needing to syndicate to outside services would be somewhat moot.
As long as the conversation for something on micro.blog starts on your own site, the replies that occur there will generally flow back to your site via Webmention, but sadly one needs to use some manual chicanery to get a similar back and forth effect with other services like Twitter.
I suspect that in the coming months/year(s) things on this end will improve as the community marches forward.
Either way, congratulations on what you've done with you're site! Hope to see you around either via reader or micro.blog.
@chenoehart What you're describing is something akin to what I've been experiencing on micro.blog for the past several months.
@jgkoomey @judell As an inexpensive model of this approach, Micro.blog has a paid, hosted version of this for $5/month. It takes a much more ethical approach to both community and data and encourages you to own your own data. https:/