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
Jeremy, congrats on owning your reading! I'd recently seen your note about using reading.am, but I've been on holiday and not had a chance to get back to you.
In general it seems like you've found most of the salient pieces I liked about it. For the record these include:
* I like the idea of "bookmarking" everything I'm reading as I read it. Even for things I don't quite finish, I often will want to know what the thing was or how to easily find it at a later date.
* It has an easy to use desktop bookmarklet that makes the friction of using it negligible. (On mobile I use the ubiquitous sharing icon and use my account's custom email address to email links to my account which is quick enough too.)
* Its RSS feed is useful (as you've discovered), but I've integrated it into my WordPress site using IFTTT.com for porting the data I want over. In my case I typically save the post as a draft and don't publicly publish everything that my lesser followed reading.am account does. Generally once a day I'll look at drafts to add some notes if necessary, or do some follow up reading/research (especially when I've read something interesting via mobile and didn't have the time), and then publish a subsection of the captured reads as public.
I've filed an issue with the developer to see if he'd include the comment data within Reading.am into the RSS feed so that it could be included in the passed data, so that when commenting there, the commentary could also be passed across to my site as well.
While I typically prefer to default to POSSE when I can, this PESOS workflow is generally acceptable to me because it required very little effort and I like having the drafts to determine which I should post publicly/privately as well as for a nudge on potential follow up for some of what I've read.
One other small thing I had done was (via plugin) to have any links on my site auto-post to the WayBackMachine on archive.org as I read/post them that way there's a back up version of what I'd read so that in the future copies are available even if the site goes down at a future date. I suspect you could do this with a simple POST call, an example of which I think is documented in the wiki.
As a subtle tweak you may wish to take a look at https:/
I know you're always saying that you're not a developer, but you've puzzled out a regex filter, implemented it, and posted it to your site for others to benefit. I would submit that you could now proudly wear the title even if you have no intention to do it professionally. Neither of us may be at the level of people like aaronpk or snarfed, but then, really, who is?
I also love that you've got a Webmention form set up, working, and looking great. Congratulations! If you want a small challenge, perhaps you could massage it to create a Grav plugin so others could easily implement it? If you want less challenge (and obligation for support), perhaps submit what you've got as an issue to the Grav Webemention plugin https:/
Congratulations again Mr. Developer!
@EatPodcast Jeremy, does All in One SEO do POSSE, and if so where? I didn't think it had this capability, though ti does do a lot. I know it does include some of the Open Graph metadata so that you can control Twitter cards when you POSSE there, but didn't think it had the capability. Perhaps you were referring to SNAP?
Why couldn't journalists use bigger publishers/aggregators as syndication partners this way? #POSSE
For the syndicated portfolio, you might want to take a peek at the PressForward plugin for WordPress [http:/
As an example, compare:
This is beneficial as you can syndicate (POSSE) the post with your own URL to Facebook, Twitter, et al. and folks who click to read will be sent to your site for a moment before being forwarded on to the original. Thus you get a ping and the original outlet also gets a ping (as well as the advertising revenue for it.) And if, for any reason, the original outlet goes out of business, gets sold, or disappears, you've got a word-for-word copy of your original and can simply un-forward it so that it can appear on your site as it was originally published. Naturally if you prefer and the outlet doesn't stipulate otherwise, you could publish the original to your site and not forward it (or even forward it for an exclusivity window of time pre-agreed with the original publisher.)
Additionally, if you're using Brid.gy for backfeed, anyone who comments on your POSSE copies will have their commentary sent to your site. While others won't necessarily be able to see the commentary (if you're forwarding the URL to the publisher's original), at least you'll be aware of it and can reply to it and get your own replies in return. I suspect that in the future brid.gy may be able to scrape commentary based on the syndicated URL so that your personal version aggregates commentary from the publisher's original as well as mentions of it on Facebook, Twitter, et al.
There are still some missing pieces I'd like to see in such a workflow for journalists, but it's slowly and surely getting somewhere.
(I've written about other parts of PressForward before at http:/
@cleverdevil Thanks for the kind words Jonathan. I nearly used your example in the piece, but it was already clocking in around the 4,600 word/20 minute mark, so I had to let it go. I've been thinking about this issue since last November and your post a while back was part of the kick-in-the-pants that made me write up all the moving pieces together so that feed readers not aware of the possibilities could see the bigger picture.
If you remember, do manually POSSE your comment to the main article so those who come across it have the extra example!
I like the ability to put URLs on crossposted versions as well.
If you include the ability to link to cross posted versions, particularly for hosted, be sure to include a u-syndication (microformat) class on it: see also: http:/
For those on WordPress, it would be nice if there were built in support for the Syndication Lins plugin https:/
I view replies to be similar to notes in not needing/requiring titles.
For metadata it can often be useful to have an actual title in the admin UI to identify the post in those administrative views.
What I find even more interesting/useful is having the ability to put in a custom title for automatic POSSE purposes, and the title is often used by many (most? all??) POSSE plugins for just this. In this UX/UI case it can mean some of the content could be displayed multiple times, once in the title and again in the body, which isn't ideal.
I'm certainly in the boat that stripping the title is a theme issue. I'd argue that for the best possible broad usage, Post Kinds should strip it out (using CSS) as a default and allow those who'd prefer to display it on the front end, just untoggle the CSS setting.
If this is the case, then the final consideration is the duplication of content between the title and body within RSS as well.
Jonathan, perfect, the new version fixes the issues with the content showing on the permalink.
The separate, but somewhat related issue is that the post interface still shows all of the UI for syndicating to all of the options (facebook, twitter, WordPress, Tumblr, LinkedIn, etc.), yet choosing those options doesn't actually syndicate the content. (Typically I wouldn't POSSE these post types anywhere anyway, but other users may expect this piece to work if it's shown.) I know some post types in Known hide the syndication targets when they're not supported (ie, only audio related posts can be syndicated to soundcloud), but I'm not sure how these are done.
Interestingly, when editing these types of posts, the syndication targets (correctly) aren't shown in the editable version.
Replies not working · Issue #4 · dg01d/KnownPnut https:/
When trying to reply to a pnut post and syndicating to pnut, the post not only doesn't thread, but doesn't even post to pnut, nor does it return the permalink of the post.
Manual POSSE: https:/