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
Support for importing syndication links for Mastodon Autopost · Issue #75 · dshanske/syndication-links https:/
Now that SL has the Mastodon icon (#66), I'll also note that the latest version of [Mastodon Autopost plugin](https:/
see also: https:/
> The 2.0 update shipping tomorrow attaches a new key to the post metadata: "mastodonAutopostLastSuccessfullPostURL"
> This key contains the url of the last toot.
UI: Duration doesn't make sense in Read post kind · Issue #65 · dshanske/indieweb-post-kinds https:/
When making a "Read" post in which data exists in the "time" tab for published dt and updated dt, the output displays more like one would anticipate with a music post type (or jam, listen, play, watch, travel) using start/end vocabulary instead and outputting a "Duration".
Duration may make sense if one were doing a start/end time for their reading, but then the scraper shouldn't be automatically pulling in the publish/update dates/times. Personally I'd prefer to let the publication time of my post indicate when the thing was read and have Post Kinds indicate the publication of the original piece I was reading.
Possibly better would be an if/then statement to differentiate types and for Read types outputting a date/time for the original publication and/or potentially an updated date/time if it exists.
At present, the issue is most common on New York Times posts for which the scraper pulls in the correct metadata.
Example: http:/
 to allow easier styling of individual post kinds, particularly since we all know styling on microformats is a bad idea... ;)
Maybe pk-like, pk-bookmark, etc. for the "titles" and a class on the blockquote as well? It seems odd to me that the title is smaller than my default blockquote font, but there isn't anything non-semantic to style on...
 which don't correspond well with the content :
> ?