An infographic on the origin of the elements #bighistory https:/
@bradenslen Looks like it did pretty well on your site, though the syndicated version to Twitter needs some help. I suspect you're using Brid.gy Publish to do that? Test away...
I can only see this and think about #WOPR and #WarGames
https:/
@mattscomments Are all the journalists leaving their homes?
https:/
@malcolmblaney Odd. I'd been subscribed to the feed in @inoreader for a while, but it didn't seem to be picking up/storing anything. It just looked like it had been dead for a while.
It's interesting to see that you've stored/used my old Christmas-themed Twitter handle. :)
#indiewebasaservice anyone? This sounds like the kind of thing @schnarfed will show up with at camp and it'll be fully built out using WebSub.
https:/
@rustybrick I won't presume to speak for @martijnvdven, but if he's had the same experience I've had with @disqus, their system tends to mark anything with a useful link in it as spam and one's (considered) responses are thus moderated out of existence. It's far better to write and own your response on your own site as he has.
It looks like @martijnvdven's site sends and receives webmentions (a W3C recommended spec), so if @seroundtable's site did (or Disqus did on its behalf), then the comment would exist both on Martjin's site as well as SER's as well.I suspect that since your site doesn't, he used Twitter to push across the notification so you'd be aware.
It might be more useful for @seroundtable to provide links to portions of their conversations/content (like the one I'm replying to on Twitter) syndicated to other platforms like Twitter on the site (similar to the way you did for the "forum discussion"), so they're easier to find and participate in--especially for those who don't want to sign up for a Disqus account.
@dajbelshaw Noterlive is primarily a posting interface to Twitter (mostly for livetweeting though it could continue to add some of that functionality in the future) that gives you back your data. You would still want to pay some attention to your account for side conversations and replies as well as other conference activity. In many cases I use it primarily as a note taking tool to keep content for archival purposes after the fact.
For additional two-way interaction you could use WordPress plugins like Webmention and Brid.gy Publish to get the comments, likes, etc. back to your website. I've outlined a piece of that type of workflow here: http:/
Otherwise, you might also consider going full IndieWeb, in which case you could post everything directly from your website and syndicate to Twitter and then getting all the responses directly back to your site. Some of this depends on how much work you want to do to get the moving pieces working properly. You'll notice this is roughly what I'm doing on my own site with you now. Example: http:/
@dajbelshaw In future, if you prefer to keep your content on your own site (hooray!) but still use Twitter briefly for conferences, you might consider taking a look at Noterlive.com to create it all. It allows export of content as html for saving later.
@sadlerjw You've certainly found a few of the remaining pain points within the broader community and specifically with WordPress. There are obviously some UI bits like properly threaded conversations across multiple syndicated silos that could be better. I've written a tad about how threaded comments work between sites using WordPress, though didn't touch on the idea of doing so also using Twitter or micro.blog: http:/
Ideally in the end, everything would support Webmention and needing to syndicate to outside services would be somewhat moot.
As long as the conversation for something on micro.blog starts on your own site, the replies that occur there will generally flow back to your site via Webmention, but sadly one needs to use some manual chicanery to get a similar back and forth effect with other services like Twitter.
I suspect that in the coming months/year(s) things on this end will improve as the community marches forward.
Either way, congratulations on what you've done with you're site! Hope to see you around either via reader or micro.blog.
The magic is likely courtesy of the fact that my post has a meta tag for og:image that includes (or transcludes) that image from Naughton's website. It's something I added in for syndicating to sites like Twitter or Facebook to add a little visual interest. I suspect that whatever you're using to unfurl the page on your site is picking up that data to display it as context for your like. You'll notice that the same photo appears on Twitter as well: https:/
I'm currently doing this with fields in the All In One SEO plugin for WordPress, though I suspect that Yoast and other Open Graph meta related plugins will do it as well. More often than not I use the functionality to force particular photos to be shown in syndicated services. Usually I'll also transclude the photo in my own post, so in most cases you probably wouldn't have guessed. Sharp eye for having noticed here Jeremy.
Anyone who didn't get enough of Open Domains Lab this afternoon is more than welcome to join in on the #IndieWeb chat to continue conversing and building their website. #DoOO
https:/
https:/
@spigot It's not Brid.gy, instead it looks like it's caused by the microformats and their placement in your particular theme. https:/
You can find a preview of what Bridgy will publish at https:/
@jonudell @aaronpk @schmarty and other media fragments people may appreciate this a tad. https:/