The nice part is that this sort of model allows the user to collect this data and send these notifications on an as-desired basis to the publisher.
Here’s more on how I’ve thought about it before: https://boffosocko.com/2018/03/10/thoughts-on-linkblogs-bookmarks-reads-likes-favorites-follows-and-related-links/
listen-ofand potentially other similar future verbs which may have a variety of “tenses” or a sense of progress across time, I wonder if it may be more advisable to have a completely separate progress/tense related microformat? This would provide the broader benefit of allowing it to be reused in those other cases rather than being specific to the read case only.
Perhaps a grow-able spectrum of statuses like:
p-finished? (These are placeholder suggestions as we may do better with some thought on naming). These could be used in combination with the other proposed read, watch, and listen related microformats (or other potential future classes of verbs). The “want” status is reasonably well attested for activities like want to read, want to watch, want to listen, want to buy (or acquire), etc. Most of these are often finished in relatively short (or very long) time frames such that on-going statuses like watching, listening, or owning may not be posted frequently the way that an ongoing “reading” progress-like status might be used over the days, weeks, months that books are being read. I could see myself using ongoing statuses like these being used with to-do list items or project management related functionality as well. Longer term checkins at on-going events (conferences, festivals, vacations, etc.) might benefit from these statuses as well.
Separating the progress (tense) from the verb/action may also make it easier to create collections of posts around the related content. (An example may be the collection of all the posts about a particular book: the want post, the progress posts, notes, annotations, etc.)
On a separate note, I’ll mention that @swentel’s Indigenous for Android has added publishing support for both
p-read-status (as well as all the proposed values) in the past few months.
If you’ve ever talked to me about books and reading, then there’s chance that I’ve brought up GoodReads and how I’m pretty active there. I can’t claim so active that I’m updating daily. I do, however, make sure to keep my current book statuses accurate. On the flip-side, as highlighted b...
Readup tracks your reading progress. In our community, you can’t comment on articles you haven’t really read.
Ton made a post recently about federated bookshelves, sparked by a post from Tom. It’s an idea that Gregor has done a good bit of thinking about from an IndieWeb perspective. Book recommendations is something I’m always interested in. At base, all it needs is a feed you can follow just of what p...
V0.1 for an experimental open bookshelf spec
Example assignment: https://archive.jgregorymcverry.com/5570-2/
Notice the replies underneath which came from other sites including my response which is mirrored on my site at https://boffosocko.com/2018/08/04/highlighting-some-of-my-favorite-edtech-tools/
Example podcast post for a class: https://archive.jgregorymcverry.com/2toponder-episode-one/
Notice the listen webmention in the comments which links to my listen response at: https://boffosocko.com/2018/08/06/2toponder-episode-one-intertextrevolution/ where I own a copy of the context and my own response. As a student, even if the originals disappear, I’ve got the majority of the important content from the course.
I’m waiting for people to start documenting examples of owning their knitting on their websites and syndicating to/from Ravelry. #IndieWebKnittingChallenge
Social reading and reviewing, decentralized with ActivityPub - mouse-reeve/fedireads
I love seeing more activity in the reading space for IndieWeb!
<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!
#######-user-nameis the typical user number and name combination at one’s profile page.