@TheEastsiderLA Any update on the pursuit in Glassell Park this morning? Helicopters still hovering almost 2 hours later...

A few days ago, in part based on something that [Richard MacManus wrote](https://richardmacmanus.com/2017/06/22/openness-rivers-indieweb/) (and which may have prompted @scripting's response), I noticed that Inoreader differentiates between importing an OPML and subscribing to an OPML.

> # Importing an OPML
> If you import an OPML file in your RSS reader, you are creating a static copy of the reading list. If the owner of the original list updates the list, this change will not be shown in your feed collection.
>
> # Subscribing to an OPML
> An OPML subscription, however, creates a live connection between the original source and your feed folder. Whenever a feed is added or deleted from the original list, the change will be reflected in your subscriptions. The notification system in Inoreader will notify you that new feeds were imported or existing feeds were removed.

Ideally, if a site had a blogroll or other mechanism by which they maintained and publicly published their own OPML list, then the user could plug that into the reader to subscribe to the list which could update dynamically. One could also subscribe to others' OPML lists (or subsets of them?) as well without needing to pay attention to them. In total, this sounds like what Ben's reader (and Known's subscription list) were doing, but by using a pre-existing standard that's broadly supported. (As an example WordPress sites with the Links module enabled publish their OPML files at example.com/wp-links-opml.php).

Andreas, The best way I'm aware of to do read posts with #WithKnown currently is to post a status update to the effect. I've been considering doing a plugin similar to Jonathan LaCour's Watching https://github.com/cleverdevil/Known-Watching but for books. In fact, other than some cut and paste work and changing the microformats, it should be a simple thing. I'd almost feel guilty for "stealing" it.

I've started hacking away at a Read plugin similar to the bookmark or like functionalities that simply bookmarks articles which I've read online, but it's got some quirky upstream issues that need to be solved before I can finish it. Ultimately it's really for online content more so than books (or even magazines) though. I may circle back around to it sometime toward the end of the summer as I'm trying to finish up some last pieces on my Reading workflows for WordPress.

@jimmymansaray I'm sure it's not an Independent Publisher issue. You might also ask Colin where he got it and if it had actually worked for him. I think I saw that snippet floating around last week. I think Colin has ultimately changed to the following instead: https://github.com/colin-walker/wordpress-blank-title.

It adds the kind of date/time stamp you're looking for (or is modifiable with some research) and has the added benefit that micro.blog should ignore the time stamp and just import the_content() of your status update instead.

Honestly, I'd recommend going without a title if you can manage it. If you need something in your admin UI, you might try this suggestion as well: http://boffosocko.com/2017/05/04/title-less-status-updates-for-micro-blog/

I notice that https://baty.blog/ (also https://micro.blog/jack) is also using Independent Publisher to do somewhat the same thing.

Time for the quarterly update of my Twitter archive http://boffosocko.com/twitter/
How you can do it http://boffosocko.com/2016/12/05/how-to-own-display-your-twitter-archive-on-your-website-in-under-10-minutes/ #Indieweb

Jeremy, no worries, it's not openly transparent unless you look at the html source of the page directly. WordPress has a nifty feature that if you add an .mp3 URL to the text field, it will automatically format it as a player (much like embedding a youtube video), in my case I used an <audio> element wrapped around a .mp3 URL which creates a slightly different player (based on the web browser implementation of the spec) with somewhat different functionality.

As for replying to multiple sites at once on Known, on a "reply" post you'll have one URL in a field by itself, then you can click on the "Reply to a site" link under the "New Status Update" box to add another box, and so on. Thus, this particular post will send three replies. One to your response about the media player, one to your question about multiple replies, and a third which I'm sending to my original post which preceded your reply, so that it contains a full chain of the replies. There's also a "Remove URL" link in case you add too many--I don't think the post will publish if you have empty reply fields.

If you look on the wiki, there's a thing called salmentions (salmon+webmention) which programatically checks all the replies to replies and syndicates one's response everywhere so that all the posts in a chain of conversation get webmentions to have a complete record of a conversation. Few sites do this yet in practice, but if you're diligent on Known, you can effect salmentions manually.

I ultimately edited the original instagram post to remove the emoji to get around it, but haven't dug further into the issue after Otto's post via wordpress support. I suspect that I need to update the encoding to my database to have it work, but haven't had time to tinker with it recently.

I've seen the problem via two other hosts which aren't GoDaddy managed, so I don't suspect that's the underlying problem.

@rhiaro I see why now, it changed to tagS... may want to update that LinkedIn page.... clever idea for a web-based CV. I considered something similar a few weeks back, but have yet to build it.

@cswordpress @redcrew Thanks for the recommendation Amanda!
I'm guessing you installed PressForward directly on your production server without using a test environment? I can tell because all of your posts are trying to redirect, but are redirecting to themselves! It's a known bug I mentioned here: http://boffosocko.com/2016/12/31/pressforward-as-an-indieweb-wordpress-based-rss-feed-reader-pocketinstapaper-replacement/#run+across+an+issue+with+the+automatic+redirect that Aram has apparently fixed in the Github repo and will push with the next update. https://github.com/PressForward/pressforward/issues/878

Until then you may want to go to the settings and set the redirect time to "0" which will prevent all of your pages from continually re-loading OR you could uninstall it from your production site and run on a test server.

I've been loving it since I installed and can't wait for the forthcoming patch. I'm curious what others think of it for the off-label use I've proposed.

@zack06007 It looks to me like this plugin isn't being actively maintained and I don't even see it in the main WordPress.org repository anymore. It's also possible that with the recent WP 4.7 update some of the functionalities have broken further. The last commit to the code was almost a year and a half ago with the bulk of the code being even older.

If you'd like to maintain a lot of this functionality in a better way with some smaller discrete plugins I would recommend the following:
- [**JetPack** ](https://wordpress.org/plugins/jetpack/)or [**Social Media Network Poster**](https://wordpress.org/plugins/social-networks-auto-poster-facebook-twitter-g/) for syndicating/sharing your content to Facebook, Twitter, et al. JetPack is simpler to set up, but SNAP provides a lot more customization and has some good documentation.
- [**IndiwWeb Plugin for WordPress**](https://wordpress.org/plugins/indieweb/) - This will allow you to add some sub-plugins like Webmention and some simple comment plugins which will let your comments/likes/etc. come back to your pages and posts. The Syndication Links plugin within the IndieWeb plugin will allow you to easily display which services you syndicated individual content.
- [**Brid.gy**](http://brid.gy) - Connecting to this free service will give you comments, likes, and reactions from major social hubs like Facebook, Twitter, Instagram, G+, and Flicker to come back to your original content in a pretty way. It is expandable to other platforms if you'd like to contribute to the code base. Bridgy uses their open APIs to bootstrap the new W3C Webmention spec to send the comments back to your site using the Webmention plugin within the IndieWeb Plugin mentioned above. Webmention is essentially an internet wide @mention functionality much like Twitter and Medium have.

If you need more help in setting these up or using them, feel free to visit http://indieweb.org/WordPress which has lots of documentation or ask in the [IndieWeb chat](http://indieweb.org/irc) where someone can help point you in the right direction.