See also: https://twitter.com/search?q=from%3A%40m_ott+webmention+craft
There’s an IndieWeb stub page for Statamic, but no examples of usage yet.
I’m curious to hear what you think of them after playing a bit.
See also: https://twitter.com/search?q=from%3A%40m_ott+webmention+craft
There’s an IndieWeb stub page for Statamic, but no examples of usage yet.
I’m curious to hear what you think of them after playing a bit.
Webmentions are so freaking cool and I've only dipped a toe in
— Jeremy Felt (@jeremyfelt) January 9, 2020
Thank you, Jeremy, for helping me along on getting these tools figured out. Very few things about the web have excited me as much as learning about the IndieWeb work that has been ongoing.
I think? If you know how to send a Webmention, please do so that I know it works!
I’ve installed the IndieWeb plugin as well as its companions, Webmention and Semantic-Linkbacks.
The IndieWeb plugin adds a few semantic things to the user profile in WordPress and acts as a launch platform for ...
This phlog is about web stuff. Specifically it's about Indyweb things and microformats.
I use my website https://tomasino.org as an IndieAuth [0] portal. When logging into sites that understand the IndieWeb concept, I provide my "Home" URL as an identifier. Then the site scrubs through all the various links I have on that page and picks out those that it can understand for authentication. In most cases I get GPG and GitHub hits, though occasionally a site will support more. I oAuth in, and bam... identified. It's pretty neat and requires very little effort on my side.
James Tomasino wrote about his experience with implementing #IndieWeb Webmentions on his Gopher blog.
To bridge my webmention from HTTP to Gopher, I'm web-mentioning his post through the Floodgap Gopher proxy. If you're using Lynx or another Gopher-capable browser, open his post here: gopher://gopher.black:70/phlog/20191223-webmentions-and-microsub
I love love love Instapaper. I should pay for premium. But I don’t like that all my highlights and notes get locked up in their proprietary system.
— Matt Maldre (@mattmaldre) December 30, 2019
Right now, I save all my Instapaper articles to PDF and make my highlights/marginalia in the PDF. I get to keep it.
Op Twitter, Instagram, Facebook, Mastodon en LinkedIn is het vrij normaal om andere gebruikers te vermelden door hun accountnaam in je update te noemen. Groot gemaakt door Twitter is de @-mention nu een bekend fenomeen op het web. De netwerken zijn zo slim om deze gebruiker een notificatie te sturen...
I’ve tinkered a bit with CROWDLAAERS, but it’s always seemed to me geared toward a very niche audience including teachers potentially using it for grading? Perhaps I’m missing some more of its flexibility? Remi Kalir might be able to help elucidate it or indicate if he’s noticed anyone using it for off-label usage.
I might see it being more useful if one could analyze site-wide annotations on a domain with a wild-card search of this sort: https://tomcritchlow.com/*.
I have to imagine that it would be cool to see all the annotations and conversations across something like the New York Times with a data visualization tool like this.
Jon Udell and gang are aware of Webmention, but haven’t pulled the trigger (yet) on making the decision to build them in. I’ve outlined some methods for making their platform a bit more IndieWeb friendly by adding markup and some additional HTML to allow people to force the system to be able to send webmentions. I do frequently use Jon’s facet tool to check highlighting and annotation activity on my website.
I have found Crowdlaaers useful several times in that I’m aware that some pages are annotated, but they’re either not public or are part of other groups for which I’m not a member. An example of this is this page on my website which has one annotation which I can’t see, but by using Crowdlaaers, I can. Another example is viewing annotations on sites that have subsequently blocked Hypothes.is like this example. Of course, sometimes you’ll do this and find odd bugs floating around in the system.
I also maintain a collection for most of my WordPress IndieWeb-based research, which may answer additional questions or go into more depth. Hopefully the above three can get you started quickly though.
As part of getting back into using micro.blog I’ve been working to customize my hosted site. One of the things I wanted to do was add webmentions rather then comments like Disqus.
Since they’re unlikely to report on the mechanics of some of their own website and journalistic output, I’ll take a moment to highlight it on their behalf.
Traditionally known as linkblogs back in the old blogosphere days, this sort of web pattern is probably better and more specifically called a “reading page” now. (Even Nieman titles the page “What We’re Reading” and uses /reading/
in the URL path to the page itself.) Many people still maintain linkblogs or bookmark pages (often on social silos like Pinboard, Pinterest, Twitter, Pocket, Instapaper, et al.), but generally the semantic name there implies articles or pages that were found to be of general interest or that one wanted to keep to read or consume later. On today’s more advanced web, there’s actually more value in naming it a reading page as it indicates a more proactive interest in the bookmarked content–namely having spent the time, effort, and energy to have actually read the thing being bookmarked. This additional indication of having more skin in the game provides a lot of additional value of a read post over a simpler bookmark post in my mind. It’s also part of the reason my website sends and receives read-specific webmentions.
This pattern of providing links of read material is pretty cool for a variety of reasons.
First, if you’re following and reading the Nieman Lab, you’re very likely going to be interested in many of the things that they’re reading, researching, and covering. By providing a reading page they’re giving their readers a trove of useful data to discover articles and material in similar and tangential spaces that the lab may not be able to actively cover or engage in at the time.
By knowing what the Lab is reading, you’re provided with a broader perspective of the things they’re actively interested in. By reading those things yourself, you’ll have increased context into what they’re doing, what those areas look like, and what they are adding to the conversation in their research and work.
Linkblogging has long been a thing, and, in part, is what a large number of Twitter users are typically doing. In Nieman Lab’s case, they’re just doing it on their own website, which adds tremendous value to it. By smartly hosting it on their own site they’re also guarding against the built value of their read archive disappearing if they were hosted on a social silo (remember Delicious? CiteULike?). Also by keeping it on their site, it has more long-tail value than if it were to all disappear into the new-content-wins attention machine that Twitter has become.
Of course I’d personally find it a lot more beneficial if they provided or advertised a linkblog feed for their reading page. Sadly they don’t. However, if you’re as interested as I am, you’ll dig under the hood a bit to discover that Nieman Lab’s site is built on WordPress and they’re using that page likely with a category, tag, or other taxonomy. So with a short bit of intuitive guessing about how WordPress is structured, we happily discover there is a feed of their reads at https://www.niemanlab.org/reading/feed/. (I suspect this feed exists as a design choice by WordPress than by the design or will of the Nieman Lab.) If you prefer a faster, one button subscribe option:
If Nieman would like their own universal follow button like this, take a peek at what SubToMe has to offer on this front.
By accumulating a trove of links and summaries, which they’re hopefully keeping, they’re creating a huge relevant database for future research on the topics in which they have interest. The small pieces that may not make sense today may potentially be woven into future narratives and pieces of research later, but this sort of thing is vastly harder to do without reading and making note of it. In a sense, they’re creating a corporate or research lab-based commonplace book for their own use.
While I’ve seen many people (generally individuals and not magazines, companies, or other bigger outlets) regularly publish newsletters or weekly posts on what they’ve found on the web that is interesting, I haven’t seen as many who publish specific pages or archives of what they’re reading. Even fewer provide RSS or other feeds of this content.
The IndieWeb wiki read page has some useful and interesting examples of this behavior, but they’re almost all individuals.
One other example I can think of in the journalism space, mostly because it’s getting to that end-of-the-year recap time is Bloomberg’s Jealousy List, which this year incidentally has some fun little drolleries that move as you scroll the page. This subset of reading lists is interesting as a group of articles Bloomberg wished they’d written and published themselves. This may indicate that they’re keeping a reading list internally, but just not publishing it regularly like Nieman is.
I can’t help thinking if Nieman Lab’s OpenFuego bot is a part of their workflow in creating their reading page as well?
And finally, since I also have a similar behavior, I’ll mention that you can find my reads on my reading page (sometimes with commentary) or follow it all via RSS if you like.
Are you aware of other people or organizations publishing lists of what they’re actively reading online? Do they provide feeds? How can we make this feature more prevalent on the open web?
In addition to some other useful upgrades and bug fixes, the big new feature this release adds is excellent syndication support for Micro.blog.
While many people use RSS feeds, JSONfeed, or other plugin methods for syndicating their WordPress website’s content to Micro.blog, this plugin now provides for a per-post decision about exactly what content to send to Micro.blog. It also naturally provides a syndication link from your site back to the Micro.blog post. To my knowledge no other method provides this syndication link functionality.
As I suspect many may already be aware, if your site supports Webmention (typically done with the Webmention and Semantic-linkbacks plugins), then Micro.blog will notify your site with replies and comments to your post as they appear on Micro.blog. This provides one the ability to do two-way communication between the two platforms.
If you don’t already have it, install the plugin and activate it, otherwise update it within your site’s administrative interface.
Add your Micro.blog account username to your user profile on your WordPress site. This is typically found at /wp-admin/profile.php
. In my case I simply added c
to the field labeled Micro.blog username.
Adjust your WordPress Syndication Links settings page (typically found at /wp-admin/admin.php?page=syndication_links
) to include Micro.blog by using the appropriate checkbox. Be sure to save the setting.
Remove, if necessary, any of the RSS, JSON, or other syndication feeds from your Micro.blog account so you’re not accidentally duplicating the syndication.
Add the JSONfeed URL from the bottom of the Syndication Links plugin settings page into your list of feeds at https://micro.blog/account/feeds.
Create a post, select Micro.blog as an endpoint in the relevant meta-box, and publish your post.
Once published, your post will ping Micro.blog’s server to indicate the new content which will then be displayed in your timeline. The Syndication Links plugin will then find the permalink URL of your post on Micro.blog and display it on your post (as per your settings) along with any other syndicated copies. This notification process is roughly real time, but may take a minute or two for your post to display and the syndication link to appear on your site based on the processing times on the relevant servers.
As an added bonus, Syndication Links plugin will also find the syndication links from Micro.blog in your current feed and add those to your original posts.
If you have any questions, need clarifications, or find bugs with regard to your set up, you can file issues for the plugin on GitHub.
I just set up b2evolution CMS/blog(s) ver 6.11.4. It has the ability to send and receive Webmentions as per the Indieweb. This was discussed before but now I can confirm. I’m still wandering around the backend getting familier with it.