Skip to main content

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



Would a magazine by another name sound so expensive? Medium launching a $5/mo member program


goes with a client called Screech!! If only @SoundCloud et al could do this...


it's a thing
The Vegetable Technology Gap via @hbottemiller"


(Consider Adding Web Annotations to WordPress) – WordPress Trac

Mostly to provide some additional resources to the conversation I'll add the following:

Web Annotation Working Group's [ three recommendations and two additional notes]

Prior to the WPTavern post which motivated the conversation, there was a [ post written by Dan Whaley of] who worked extensively within the group. This post has some interesting overview, but those interested in a fully implemented annotation platform (presumably using many of the pieces of the proposed standard) should take a quick look at [], what it is and what it allows. Their front page has a pretty useful video introduction.

Keep in mind that some of the standard is geared specifically toward browsers and browser vendors, though WordPress could certainly implement some of the pieces from the CMS side.


UX/UI Suggestion: Meta box in the admin UI with PressForward metadata and comments · Issue #902 · PressForward/pressforward

I'd suggest that it would be worthwhile and convenient to have a meta box in the admin UI for editing the final draft that contained all of the pre-existing PressForward metadata.

Bits and pieces of it appear in other portions of the PressForward UI throughout the vetting (reading, nominating) process (typically hidden under the "info" button which pops up the details), but having portions of it while actually editing the draft of the post would be very handy/useful. In particular, it would be nice to have access to the comments which are added to the particular piece in the earlier parts of the process.

![meta box information](

Comments in particular, would presumably have ideas, thoughts, and editorial leanings that could help the writer/editors shape the final piece or notes on/around it, but as it stands, one needs to dig back into the PressForward interface, typically with search, to re-uncover the particular data and notes relevant to the original piece.

Ideally making it relatively small so that it could fit into the sidebar may be the most beneficial. If you want to go all-in on such a feature, I've seen a fantastic meta box in the [Academic Blogger's Toolkit plugin]( labeled "Reference List" which is pinnable and maintains its position at the top of the UI while the rest of the page scrolls.


Example instance · Issue #1 · terminalpixel/postrchildbot

You should add a readme page with a link to the working instance

Congrats on this btw!


"copying a manuscript of this kind proceeded at the rate of about one (two-sided) folio per day; pecia rentals typically lasted one week and involved about four folios."

Syndicated to:


Bookmarklet chopping out NYTimes text · Issue #900 · PressForward/pressforward

When nominating/drafting from NYTimes stories, typically the first several graphs are excised or not copied over into the post.

Based on some quick experiments it appears that the portion of stories that appears before (typically followed by some advertising before the story resumes) are the ones being left out for some reason. From the bookmarklet's point of view NYT articles seem to begin with the portion


Old posts with no value set for `pf_forward_to_origin` are automatically forwarded · Issue #899 · PressForward/pressforward

This has probably been present for a while, but I just noticed after turning on forwarding posts to the canonical URL by setting a time >0 in the forward settings: all the old posts in my database (prior to having PressForward) auto forward as a default back to their own URLs. This means that every X seconds (as set in the setting) pages on my site automatically reload (or are redirected to themselves) and this makes the site relatively useless to attempt to read. (This seems to be a follow on error not noticed in, but which persists after the upgrade to 4.2.2 which resolved the problem for posts set to `no-forward`.)

Users adding PressForward on preexisting sites are going to have a tremendous shock if this is the default.

A better option is that all old posts (prior to installation) should default to no-forward (or at least not forward if there is no value set for `pf_forward_to_origin` in the database. PressForward should, in my mind, ideally default to no-forward in all new future posts with the possible exception of posts generated specifically by PressForward's nomination/draft workflow to default to `forward`/`no-forward` based on a possible new setting option in addition to the time setting.

It would be nice if the portion for null/non-existent values of `pf_forward_to_origin` was fixed before 4.2.2 rolled out into the WordPress repository if it hasn't been pushed already.

Running 4.2.2 on WP 4.7.2

Congratulations again to everyone, as always, on what I think is surely one of the most valuable plug-ins in the entire WordPress repository.


OPML link not working · Issue #898 · PressForward/pressforward

## What I tried/expected:
From the page `/wp-admin/admin.php?page=pf-tools` under the `OPML Link` tab, the instructions indicate:
You can share your subscription list as an OPML file by linking people to

## What happened:
Visiting the indicated link throws the following error:
`Warning: Creating default object from empty value in /htdocs/example/wp-content/plugins/pressforward-4.2.2/includes/opml/object.php on line 48

## Additional information:
I've got a handful of feeds, so I should expect something to appear. Is there a setting I'm missing somewhere? I know that there's a setting for the /feedforward RSS functionality/plugin, is there a similar one for OPML that I'm missing?

Running GitHub version 4.2.2, WordPress 4.7.2


Interesting example of backfeed for in the wild at @biorxivpreprint


Text Before Links text should have stylable class · Issue #47 · dshanske/syndication-links

In tweaking/changing the CSS for the multiple sizes (around v3.1.1), you removed the class from the "Text Before Links" portion, so it's not easily accessible for theming.

It might also be worth putting the entire output into a div with a class as well for better CSS control.

cross reference: