@Timehop Why no hooks into WordPress? #RelaxMoreSplines #REST #API

@jasongreen, it looks like you know @krisshaffer, but have you run across his Hypothes.is Aggregator for WordPress? http://kris.shaffermusic.com/2016/08/hypothesis-aggregator/

After upgrading yesterday to both WP 4.6 and SNAP 3.6.8 (pro), I'm getting the following error when publishing new posts:

Fatal error: Cannot use object of type WP_Post as array in /homepages/htdocs/wordpress/wp-content/plugins/social-networks-auto-poster-facebook-twitter-g/inc/nxs_functions_adv.php on line 155

The post publishes as expected and then the error is thrown. When reviewing over the post afterwards, it appears that it didn't post to Facebook, Tumblr or Twitter, which had been selected on this particular post.

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.

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...

@sdepolo I wrote big chunks of the documentation on some of @WordPress pages, would love to hear how easy (or not) it is to follow.

My answer to "What is your review of LiveJournal? - Quora"

It’s definitely not a good platform from an IndieWeb (http://IndieWeb.org) perspective. The details on the wiki entry at Indieweb pretty much say it all from a flexibility and long term perspective: LiveJournal - IndieWeb (https://indieweb.org/livejournal). You’d be better off with your own personal site and then cross-publishing to LiveJournal if you have a particular audience there that you want to reach and it’s worth spending the money.

If you’re choosing a platform, perhaps take a look at projects (https://indieweb.org/projects). For beginners looking for something simple and inexpensive as well as easy to maintain, I’d recommend WordPress.org (http://WordPress.org) or Known (http://WithKnown.com). These will be better at allowing you to own your own domain and own your own data while still offering a large number of more modern blogging/web features.

Other resources:
* Getting Started - IndieWeb (https://indieweb.org/Getting_Started)
* Transitional Steps (https://indieweb.org/Transitional_Steps)

Are you sure you copied the code correctly? After making the changes, I get most of the post I expect, but instead of the embedded tweet, I get a blockquote with the text "+document.title+" instead of the tweet text. I was testing this in chrome as well.

I'm suspecting that the code portion about brid.gy uses bridgy to cross-post the like/retweet to Twitter, but without including a URL link back to the permalink of the post on WordPress?

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.