Edge case post "duplication" · Issue #10 · meitar/wp-crosspost https://github.com/meitar/wp-crosspost/issues/10

I once had a blog at wordpress.com that I exported and moved to a self-hosted wordpress.org install where I now use the WP-Crosspost plugin to cross-post back to the original .com version.

When going back to edit/modify old posts on the new self-hosted site, this plugin creates duplicate copies of the original posts, typically with a "-2" (or other incremental integer) appended to the original URL.

For those in a similar situation knowing about the issue (I can see some archivists seeing this as a major feature) is half the battle and some users may appreciate a caveat in the manual.

If it's a bug you feel that's really worth fixing or working around (it doesn't affect/bother me now that I'm aware of it), I'll note that in the self-hosted .org installation, the imported posts from the original .com site all appear to have a "guid" field in the wp-posts database which indicates the URL where the original version resided. Perhaps you could run a check against this value (and the base URL) before creating a new post with a new URL to catch the edge cases when they occur?

Feature suggestion: Separate clearing of speakers and logs · Issue #18 · kevinmarks/noterlive https://github.com/kevinmarks/noterlive/issues/18

For use cases in which one is liveblogging regularly recurring events or multi-session/multi-day events, it may be useful to be able to separately clear the logs and clear the speakers (i.e.: a button for each function instead of one that does both). This way one can cut and paste the log, clear it out for the next session/day/other while not needing to re-enter all the speaker data back into the system redundantly - particularly when one may need to look up all the data again.

While the Twitter look-up is useful as a stopgap toward re-populating , the data return doesn't always do the best job as some Twitter bios don't use full names and may or may not include websites, or when users (Tantek for example) have an emoji as their "name" Noterlive doesn't allow modifying (and re-saving) corrected versions of the name (though the workaround for this appears to be to save the speaker, delete the the speaker, modify the text and then resave.)

Mostly these type of fit & finish ideas are meant to serve livetweeters who don't necessarily have lists/data on speakers pre-entered prior to an event and are forced to do the searching on-the-fly during which they are missing potential content.

Jeremy, it's not exactly a mobile bookmarklet, but perhaps you can co-opt the sharing function on mobile with something like URL Forwarder in the Google Play store the way I did for mobile use with Known [http://stream.boffosocko.com/2016/sharing-from-the-indieweb-on-mobile-android-with-apps-and ]? It'll let you strip out a URL and other data to share to Huffduffer or other apps. It's also available on GitHub [https://github.com/daverix/urlforwarder ] if you want to roll your own. #deathsentence

UI suggestion: Synopsis labeled in parallel with other data · Issue #24 · donnapep/book-review https://github.com/donnapep/book-review/issues/24

Given the way the standard data in "book info" (except the star rating) is scrapped based on ISBN, it would be nice if the word "Synopsis" appeared in bold in front of the synopsis to provide a similar parallelism between it and the book title, author, etc.

This tweak to the UI would help to indicate a more parallel structure for the base book data and help to separate it from the user's actual review. Without it, some readers of reviews may mistakenly assume the reviewer wrote the text rather than it more likely being scraped from the publisher's description.

Similarly it might make better UI to have the star rating separated from the rest or possibly preceded by "My rating" (in bold) to indicate it as separate from the rest of the bulk data as well? Perhaps adding fields for other User specific data like "date started" and "date completed" would aid in this separation from basic book data and user generated data.

Display issue for Speakers without Twitter Handles · Issue #12 · kevinmarks/noterlive https://github.com/kevinmarks/noterlive/issues/12

The display of speakers without Twitter handles could default to their names and/or URLs instead of being left blank.


Can't delete Speakers without Twitter Handles · Issue #11 · kevinmarks/noterlive https://github.com/kevinmarks/noterlive/issues/11

If an added speaker doesn't have a Twitter handle, the delete button doesn't work to delete them.

Spurious(?) error thrown when changing themes · Issue #9 · meitar/wp-crosspost
https://github.com/meitar/wp-crosspost/issues/9

Not mission critical, but possibly a small hook-based bug?

Any time I change themes on my self-hosted site running WP-Crosspost, I get the following error:


I'm not sure how changing themes would cause this error, or why WP-Crosspost code would run when changing a theme and thereby cause the error to be thrown.

To my knowledge, it doesn't seem to be misbehaving otherwise when changing themes, but thought I'd pass it along.

In case you need it: https://github.com/kylewm/KnownReactions

Events scraping properly or improper markup? · Issue #3 · indieweb/this-week https://github.com/indieweb/this-week/issues/3

In today's (8/12/16) edition, the upcoming note about HWC for 8/24 includes most of the usual suspects, but leaves off Los Angeles, despite the fact that many of them are listed as TBD while LA actually has data.

Am I missing something that causes it to skip over LA, or is something else going on?

Feature suggestion: Site Owner push notifications · Issue #1 · pushpad/pushpad-wordpress https://github.com/pushpad/pushpad-wordpress/issues/1

WordPress.com announced push notifications for site owners regarding likes/comments yesterday: https://en.blog.wordpress.com/2016/08/10/instant-browser-notifications/

Given the infrastructure you've got, it would be cool to have this as an engagement option too... I don't think many of the current push plugins have this type of functionality, so this could be a nice differentiator.

h-entry is currently on body instead of <article> · Issue #17 · pfefferle/wordpress-uf2 https://github.com/pfefferle/wordpress-uf2/issues/17

See discussion at https://github.com/snarfed/bridgy/issues/691 for details

Thanks everyone for taking a look and for the help!

Apologies if I offended anyone -- without having read through any of the brid.gy code, I wasn't quite sure what was going on. My suspicion for a while has been that using the [uf2 plugin](https://github.com/pfefferle/wordpress-uf2/) for WordPress certainly isn't quite always the best, though it's fairly impressive what it **will** allow. I've been hacking around at a new/different theme that adds microformats directly rather than programmatically to have greater control of exactly where they're put, but it's also a one-off solution rather than a solution for the masses. Better microformats injection into themes is certainly a small stumbling block for coming generations.

I was previously aware that the entry-content div on my theme overextended itself (https://github.com/WordPress/twentysixteen/issues/470), but didn't realize that the hentry/h-entry was being injected too early via uf2.

I saw some of the resulting discussion in the #indieweb-dev channel, so I'm glad my beastly banging on and breaking of things may help improve things for coming generations. ;)

@dshanske We should remember to ping the Independent Publisher theme if you decide to make changes, as I suspect it'll have the same issue(s). It's been a while since I looked at the code for it, but I recall he created a mf2.php in the theme to inject microformats similarly to uf2 or one of your recent blogposts.