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
@anildash Fantastic article. There is an errant $ on ##10 causing a formatting error though. Perhaps a translation error when you moved to Ghost? I like the new look.
@anildash Fantastic article. There is an errant $ on ##10 causing a formatting error though. Perhaps a translation error when you moved to Ghost? I like the new look.
@bupk_es The only surety is that definitely need to occur after both second breakfast and elevenses.
@cathieleblanc @jgmac1106 I notice you've already got your own website, so you've already got a major head start. If any of us can be of help as you improve it, do let us know.
@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.
@jgmac1106 I've often wondered about potential expanded vocabularies for microformats within the educational space. I know many use a variety of other metadata including schema and dublin core, but I've never really come across any application which consume these or do anything useful for them other than add an administrative tax to the user who are doing them. Perhaps we should begin documenting some of them to build a more long term valuable solution?
@jgmac1106 Perhaps we might create and use a corner of the IndieWeb wiki to begin documenting the use of these types of things? We could start on the https:/
@jgmac1106 @ottonomy Are there any actual consuming use cases for metadata in the #OER space or are pelple putting in metadata for the extra admin tax? I'm curious what those are and what they're doing with the metadata. I've not personally run across any.
@kimberlyhirsh I'm almost tempted to create bumper stickers: "Daniel Tiger is my co-parent". And now I'll have the songs "If you have to go potty, stop! and go right away." and "Grownups come back" running through my head for the rest of the day.
@EatPodcast Thanks Jeremy, I've had a bear of a time with webmentions from pages, and in particular that one which has some issues with the nesting of author tags, thus making the webmentions appear to be coming from other people. Sorry to get your hopes up...
@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.
@stevenstrogatz @TEDTalks. @rmathematicus @viktorblasjo @MBarany This seems like the sort of thing that @edscheinerman would be aware of.
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.
Jeremy, if you haven't tried it before, take a look at Ryan Barrett's Instagram Atom Feeds tool https:/
As for extracting your own photo data, I've heard this week that although Instagram is cutting off more and more API access, while confronting the Facebook problem lately and the looming GDPR, they've apparently enabled the ability to download all of your photos. I haven't tried it yet to see what the data looks like or the quality of the images is, but it's a tiny step forward for data freedom that they didn't have before.