I’m waiting for people to start documenting examples of owning their knitting on their websites and syndicating to/from Ravelry. #IndieWebKnittingChallenge
I’m enamored of Aaron Parecki‘s Monocle reader. I can subscribe to almost anything I want, read it without interfering algorithms, and reply to posts directly in the reader, which uses Micropub to post those directly on my site, which has Webmentions to send notifications to those sites in turn.
I’m similarly in love with an app version called Indigenous for Android.
But really, who can have just one favorite?!? I also love:
They’ve not only got interesting sites, but they’re always doing cool things that are worth following.
And if you want some other interesting ones to take a peek at, I have longer list (with RSS/OPML) at https://boffosocko.com/about/following/
and if you’re *really* careful, you can get a D in Chemistry and win the Nobel Prize!
“Chemistry was my worst subject in high school! I imagined my chemistry teacher aspirating his cornflakes when he found out his worst student had won the Nobel Prize!”
Peter Agre was awarded the 2003 Chemistry Prize. pic.twitter.com/h2AaNmR945
— The Nobel Prize (@NobelPrize) August 4, 2019
Using the Webmention and the Semantic Linkbacks plugins you can post events to your WordPress site and others can RSVP from their sites to notify you. Here’s an example of it working on my site: https://boffosocko.com/2017/11/30/virtual-homebrew-website-club-meetup-on-december-13-2017/#comments
Bookmarked to reply on Feb 21, 2020 at 15:20
With my limited time wedged between family and work, I was often left trying to achieve more than was possible.”
I’m still thinking about the broader implications of the essay and want to revisit it a few more times, but it had an interesting concept which seems worth considering further.
<ul> <li class="bookprogress"><progress value="177" max="465">38%</progress> <label for="">38.0% done; loc 4290-4847 of 12932</label></li> </ul>
You could always use
<span> instead of
ul/li tags (with some app specific classes to allow the receiving site to create its own custom CSS for display. Otherwise browsers should be able to display a reasonable visual default.
I’d recommend support for pages, percentages finished, and potentially even Amazon’s default location numbers, with the ability to translate back and forth potentially when given at least two of the parameters as a minimum which should allow the calculation of the others. I find in practice that it’s generally pretty rare to have both page numbers and location numbers, but it could happen.
I’ve also got an extended version available at https://boffosocko.com/2012/06/17/big-history/#READING%20PROGRESS
My first use of the read post functionality was a tad confusing because I wasn’t aware that either the WordPress Micropub client or Post Kinds supported the read-status set up that IndieBookClub.biz had pioneered.
The vast majority of my read posts are for online articles which are relatively short in nature and so don’t use the read-status features and are simply marked up with
read-of. When I originally suggested that Indigenous support read posts, I only expected the
read-of support and didn’t imagine the additional
read-status support for “to-read”, “reading”, or “finished” to be included. These are highly experimental and have thus far only been supported by IndieBookClub which focuses on much longer book-length content that can take better advantage of the ideas of the idea of a bookmark to read, ongoing reading, and finished reading markers. Even with this support gRegor still thinks that it may be better to use the addition of
u-category microformats instead of the read-status tags. The WordPress Micropub server is the only other software that supports these additional read-statuses besides gRegor’s own website.
- an exceedingly small number of sites have support for read-status;
read-ofmicroformat has somewhat better support (though it is still an experimental microformat itself);
- the majority of posts that Indigenous users are likely to use for creating read posts will be articles (as opposed to either smaller posts like notes, likes, favorites, checkins, RSVPs, etc. or book length material),
I would recommend that you have a default setting in Indigenous for just read-of without a specific read-status (the UI could either indicate “none” or “read” without a read-status value). However for the occasional longer form usages leaving the other options in would be useful. I can easily imagine myself using the option for “to-read” over the simpler bookmark functionality now that it exists!
Thanks again for all your work!
Seriously, I’ve resurrected mine a while back too. And included sub-sectioned OPML files just for kicks.
More details on the project and implications for the future: https://boffosocko.com/2019/06/18/from-following-posts-and-blogrolls-following-pages-with-opml-to-microsub-servers-and-readers/
In addition to all of this, since you’re a coder, you might also appreciate some of the more advanced feed discovery code David has written into the Yarns Microsub Server for WordPress (code on Github). You may be able to build some of the discovery bits into some of your syndication hubs/planets in the future.
Of course, like FeedWordPress and the relatively similar PressForward plugin, you might also be able to bend Yarns into an aggregator in similar ways.
Can’t wait to see what you do with it next.
I notice that in your follow me section you’ve got a handful of buttons that may eventually begin to give you a NASCAR Problem, or prompt others to say “What about feed reader XYZ?”
I’ve run into the issue before and used Julien Genestoux‘s excellent SubToMe follow button. It’s got a simple user interface, allows you to recommend a particular feed reader, but also gives readers the choice of several dozen other common feed readers. Best, it functions relatively well without getting into the whole what-is-RSS-and-how-do-I-use-it-issues. Obviously we have a long way to go to make some of these things simpler and easier to use, but slow iteration will get us there eventually.