What I wouldn’t give for a web browser feature wherein I could log into it with my URL and have the browser query my website to show me when I’ve previously read, liked, favorited, replied, etc. to the content on a particular URL. #IndieWeb
Thanks to @threadreaderapp’s brilliant new auto-blogging feature for threads, here’s my first automated post! (Thanks also for all their help in getting the authentication working, and #IndieAuth too.) https://t.co/XGLg0ypnrX
I've worked on webmentions, but implementing them on a static website is far than trivial :-( But check out https://t.co/DbkZbOCFrB It's may be what you're looking for.
Another option, though without Micropub (yet!), is Kevin Marks‘ NoterLive tool. It’ll let you create a thread and then (manually) copy over the rich data into your website pretty quickly. I love it especially for conferences.
Micropub is one of several important IndieWeb building blocks, answering the question: what would a posting API look like if we started over, stripping away everything except the most basic requirement of sending post text to a server, and then build on top of that foundation when clients and servers in the real world need more?
This session will be to iterate on proposed extensions to Micropub, listed on the Micropub-extensions page.
We will discuss which extensions can be moved to stable, try to better define those proposed, and to see who is willing to implement what proposal.
I ran across ProseMirror yesterday and my first thought was: I want this for writing and posting to my website! Not having the time or experience to set it up and integrate it myself, I wonder if there’s a public instance of it on the web that has Micropub integration?
That would allow it to publish to to several dozen different CMSes including WordPress, Drupal, WithKnown, Craft, Jekyll, Kirby, Hugo, and Micro.Blog among a growing set of others.
I know that iA Writer recently added Micropub support to allow people to use their tool to publish this way. Sadly they’ve only got it working as Mac/iOS clients and not as a web client, which is something at which ProseMirror might excel.
Some small pieces, loosely joined for owning one’s highlights online.
I ran across a Chrome extension for highlights, annotations, and tagging tonight. It’s called Learning Paths. It works roughly as advertised for creating and saving highlights and annotations online. With a social silo log in process (I didn’t see an email login option), you’ve quickly got an account on the service.
You can then use the extension to highlight, tag, and annotate web pages. One can export their data as a .csv file which is nice. They’ve also got an online dashboard which displays all your data and has the ability to see public data from other users as well.
Screencapture of the Learning Paths UI for their Chrome extension
One of the interesting pieces they support is allowing users to tweet a thread from all their highlights of a piece online. Upon seeing this I thought it might make a useful feature for getting data into one’s personal wiki, website, or digital garden, particularly now that ThreadReaderApp supports posting unrolled Twitter threads to one’s Micropub enabled website.
So the workflow goes something like this (with links to examples of my having tried it along the way):
Use Learning Paths to highlight an article;
Use the sharing interface to share the highlights as a Twitter thread;
Make any modifications to the Twitter thread and then post;
Screencapture example of ThreadReaderApp’s Authored Threads tab interface
While this works relatively well, there are a few drawbacks:
The UI for the annotations is a bit flaky at times and in my experience often disappears before you’ve had a chance to save them.
The workflow misses out on any of the annotations and tags you might add to each of the highlights (unless you manually add them to the thread, and even then you may run out of space/characters).
The appearance of the thread on your site is simply what you get.
While the idea works roughly in practice, it isn’t as optimal as the workflow or data fidelity I’ve found in using more robust tooling like that found in Hypothes.is for which I’ve also built a better UI on my website.
Still others, might appreciate the idea, so have at it! I’d love to see others’ ideas about owning their highlights, annotations, and related data in a place they control.
Articles on Quill don’t seem to have the ability to syndicate to twitter and mastodo, so I might end up using micropublish.
Bit frustrating to figure this all out, but also kind of fun to be honest.
If you use the Syndication Links plugin and configure it, Quill should be able to find your Twitter and Mastodon “endpoints” on your site and provide you with buttons to syndicate to them.
It looks like your theme has an extra u-photo on it that’s causing that avatar image to be sent to Twitter by the way. The way the microformats are set up is also causing them (Syndication Links) to display too, but it’s fixable with some tinkering. You might try IndieWeb chat to see if someone can help you troubleshoot it.
Found out that the #indieweb plugin Bridgy (posts/backfeeds replies/likes from twitter into my site) will attach the featured image of a post to Twitter. Now I want a dedicated “Tweet-through-your-blog WordPress client” app.
With IndieWebCamp West just about to start I figured this would be a good time to write up some of my thoughts on one of the missing pieces of the IndieWeb ecosystem: Micropub Queries.What is Micropub
The quick version is that Micropub is an open standard to allow publishing to your own website from...
The session that this post kicked off may have been one of the most interesting ones at IndieWebCamp West this weekend.
I don’t have a specific “Edit” post kind on my website (yet!), but I’ve set things up–using a prior recipe–so that edits I make to the IndieWeb wiki are syndicated (via PESOS) to the Micropub endpoint on my website to create draft posts on my personal website!
Presently they were easiest to map to my website as bookmarks until I can create the UI to indicate edits, but changing the UI piece, and retroactively modifying some data for posts, should be fairly simple and straightforward for me.
I’m not sure I’ll keep the entire diff content in the future, but may just keep the direct text added depending on the edit and the potential context. We’ll play around and see what comes of it. It’s reasonably sure that I may not post everything publicly either, but keep it as either a draft or private post on my website. In some cases, I may just add the edit syndication link on an original bookmark, read, watch, or other post type, a pattern which I’ve done in the past for articles I’ve read/bookmarked in the past and simply syndicated manually to the wiki.
I’ll also need to tinker with how to save edits I make directly in the chat channels via Loqi, though I think that is straightforward as well, now that the “easy” part has been done.
I only wish I had thought to do this before I made the thousands of edits to the wiki earlier this week. Both IndieWebCamp West 2020 and the edits for part of organizing that were the inspiration for finally getting around to doing this.
This isn’t as slick as the process Angelo Gladding recently did a demo of and is doing to syndicate his edits to the wiki from his website using a POSSE syndication workflow, but I’ll guarantee my method was way less work!
Also, since my edits to the wiki are made as CC0 contributions, the POSSE/PESOS flow doesn’t make as much difference to me as it might on other social silos.
I don’t edit Wikipedia incredibly often, but perhaps I set that functionality up shortly too.
I’ll get around to fixing the remainder of the presentation and UI shortly, but it’s not a horrific first pass. It’s at least allowing me to own copies of the data I’m putting out on the Internet.
Those two are pretty advanced clients, so if it’s not working with them, you likely won’t find any. Your best bet is https://chat.indieweb.org/dev/ and find some help there maybe.
Gary (The WordPress.com Blog)
Ian Brown (Twitter)
Grant Richmond (grant.codes)
ThreadReaderApp (threadreaderapp.com)