Skip to main content

Biomedical and Electrical Engineer with interests in information theory, evolution, genetics, abstract mathematics, microbiology, big history, Indieweb, and the entertainment industry including: finance, distribution, representation

boffosocko.com

chrisaldrich

chrisaldrich

+13107510548

chris@boffosocko.com

u/0/+ChrisAldrich1

stream.boffosocko.com

www.boffosockobooks.com

chrisaldrich

pnut.io/@chrisaldrich

mastodon.social/@chrisaldrich

micro.blog/c

 

Replied to a post on github.com :

@RossGoodman are you by chance using a fragmentions plugin? If you are, the /#comments hash at the end of the URL will cause the targeted element to be highlighted in yellow like that.

 

Jeremy, I think this was a known issue with the WordPress Semantic Linkbacks pluin and thought it got address/fixed in a recent update. If not, do file a bug at https://github.com/pfefferle/wordpress-semantic-linkbacks

Also interesting, it looks like Independent Publisher (theme) isn't outputting a permalink for the comments on Among The Stones either. If they're webmentions, all the URLs point to the locations of of comment originals, which makes it harder to target individual comments with fragmentions.

 

@billbennettnz @davewiner I think I mentioned to you that @Chronotope was mulling something over along these lines:
https://twitter.com/Chronotope/status/830097158665801728

I'm curious if there's a middle ground? The way that @davewiner does his blog with updating hashes throughout the day would be interesting within news distribution, that way the URL changes, but at the same time it doesn't really. Example: http://scripting.com/2017/08/17.html#a094957 (Naturally the ability to update RSS feeds over time would be useful---as he describes in this particular post--, but it would also depend heavily on how users are subscribing to their news.) In his case, the updates are categorized by day/date rather than topic or category which is what an unfolding story would more likely do in a digital news publication.

In some sense, these hashes are related to the IndieWeb concept of fragmentions: https://indieweb.org/fragmention, though in their original use case, they're meant to highlight pieces within a whole. This doesn't mean they couldn't be bent sideways a little to serve a more news-specific piece that includes a river of updates as a story unfolds--especially since they're supported by most browsers. It would be much easier to syndicate the updates of the originals out to social media locations like Twitter or Facebook this way too. Readers on Twitter, for example, could see and be directed to the latest, but still have easy access to "the rest of the story" as Paul Harvey would say.

Depending on implementation, news sites could offer a tl;dr toggle button that gives a quick multi-graph synopsis. As I recall USA Today and Digiday used to do something like this on longer pieces:
https://twitter.com/ChrisAldrich/status/632063182811467776
Here's a version of the functionality via the WayBackMachine that still works: https://web.archive.org/web/20150818075138/http://digiday.com:80/publishers/mics-social-approach-distributing-first-obama-interview/

Imagine how powerful a long running story could be with all of these features? Or even snippets of inter-related stories which could be plugged into larger wholes? Eg: The Trump Administration's handling of North Korea seen in fact snippets over time spanning months while pieces of this could be integrated into a larger Trump Administration mega-story going back to January or even the beginning of his campaign. Someone who hasn't been following along could jump back months or years to catch up relatively quickly, but still have access to more context that is often missing from bigger pieces which need to stand on their own relatively.




 

@mattscomments No, not a plugin (yet?). I exported them via the Amazon Kindle Desktop app and added some CSS to improve the mark up a tad. Doesn't take too long though. I greatly prefer to own this type of content on my own site first and then syndicate it to places like GoodReads after the fact.

I've written some details here: http://boffosocko.com/2016/10/24/notes-highlights-and-marginalia/
Searching my site for "marginalia" will uncover other resources: http://boffosocko.com/?s=marginalia

I also recently helped guide Jeremy Cherfas though some of the process and he's well documented a similar (non-WordPress) workflow here: https://www.jeremycherfas.net/blog/setting-my-marginalia-free

Given your Twitter background at @mattmaldre:
There are some in the indieweb movement working on notes, highlights, marginalia, fragmentions, etc. You can search/find wiki pages for those topics here: https://indieweb.org. In particular, Kartik Prabhu has a fantastic set up which he describes (and you can see implemented along with sample code) at: https://kartikprabhu.com/articles/marginalia

I presume you'll already know about https://www.w3.org/blog/news/archives/6156? As well as work by groups like http://hypothes.is.

 

@ivasef85 @lukashmayyn @Anthony Adding highlighting to my @WordPress blog with fragmentions and @hypothes_is took 2 minutes.

 

UI: Duration doesn't make sense in Read post kind · Issue #65 · dshanske/indieweb-post-kinds https://github.com/dshanske/indieweb-post-kinds/issues/65

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://boffosocko.com/2016/11/14/chris-aldrich-is-reading-facebook-restores-iconic-vietnam-war-photo-it-censored-for-nudity/
![duration](https://cloud.githubusercontent.com/assets/5882943/20466247/6e5f67aa-af24-11e6-9d57-f83c3928163f.PNG)

For a small portion of IndieWeb sites, the scraper is returning data in these fields that are identical for both the published and updated fields which returns an odd duration result as well. (See: http://boffosocko.com/2016/11/11/chris-aldrich-is-reading-fragmentions-for-poets/) Perhaps if the date/time in both fields are identical, there could be some error checking to prevent a spurious output since published shouldn't equal updated.

 

Replied to a post on github.com :

Because Independent Publisher works really well with [IndieWeb technologies](https://wordpress.org/plugins/indieweb/), people interested in this type of functionality might look into Kartik Prabhu's post (and resources) relating to marginalia at: https://kartikprabhu.com/articles/marginalia

Using this, one could allow for [Fragmentions](https://indieweb.org/fragmention) and then in conjunction with the marginalia set up, one could be nearly ready to go. It's not quite as "native" as the simple functionality that Medium offers, but is much nicer from the philosophic viewpoint of allowing the user to own all their data.

 

@KevinMarks FYI, the time posts on your webmentions appear to be off by 7 hours. See also my last comment on: http://www.kevinmarks.com/fragmentions.html

 

Replied to a post on github.com :

There are two Fragmentions plugins available that might be included in the IndieWeb plugin:

Christiaan Conover:
https://wordpress.org/plugins/wp-fragmention/
https://github.com/cconover/wp-fragmention
Luis Rodriguez:
https://wordpress.org/plugins/fragmentions/
https://github.com/goblindegook/Fragmentions/

At present Conover's has 20+ installations and was written first while Luis's has 0 installs,but is more recently updated. Both seem to work on my site reasonably well, though someone more experienced than I may have an opinion on which is "better" from a coding standpoint.