@jdblundell @photomatt @WordPress @automattic In fact, if anything Akismet is actually even more aggressive than it ought to be for webmentions. #indieweb
With #indieweb webmentions, @wordpress @automattic @photomatt could easily replace Facebook and Twitter http:/
Remember WordPress' Pingbacks? The W3C wants us to use them across the whole web http:/
#indieweb @kevinmarks @t: And as @jeffjarvis notes, it's subtitling that helps to drive engagement when autoplay of videos is silent.
@alexishope @joegoldbeck In fact, here's a great example of being a canary in the coal mine from last night: http:/
Going Silo-Private to Prefer the #IndieWeb, Leave Silo Publics, and Pioneer Privacy http:/
I'm still mostly relying on native WordPress Post Formats, though I'm leaning toward switching completely to post kinds (or figuring out how to straddle the two.) Though for the IndieWeb noobs, I'll mention what appears to be an odd conflict(?) between the two worlds.
Since the last one or two updates of Post-Kinds, there's a snippet of code somewhere that's adding an additional grey bar between the title and the content on them, specifically in WordPress "Pages", which probably shouldn't be happening as the native theme is more likely than not handling that output. See picture below:
https:/
Deactivating Post-Kinds removes the additional bar ( an hr tag?), so it's definitely coming from code within the plugin. It appears to me to be hiding within:
div class="e-content"
div class="h-cite response "
/div
div class="entry-meta"
The line doesn't appear to show up on blog posts marked as "article", "notes" or "photos", but does show up (with the appropriate icon) for posts marked as bookmark, favorite, like, listen, play, read, etc. (which is what I and others would presumably expect) Ex: http:/
As most wouldn't expect it to show up on Pages, you might consider removing it from them in the next iteration.
In case it's necessary for troubleshooting purposes, I'm using Version 2.3.1 and in the settings I've not checked "Disable Post Formats".
Matrix (chatserver) and #IndieWeb: A match made in heaven? 👼 http:/
Not getting enough #indieweb after Homebrew is over? Try this list for later: https:/
@kevinmarks @benwerd: #indieweb Is there really no @wordnik or @imdb on the web but for jokes including attribution and tags? #startupidea
.@christi3k Throw in some #indieweb goodness and you also get notifications/pings that @Medium doesn't have either http:/
#phdchat #digitalhumanities #highered Helping physicist John Baez transition: G+ -> #indieweb @WordPress; see notes https:/
Running a catblog must be a great way to #dogfood your #indieweb development work. https:/
If you're going to have an awesome cat blog, make sure your cat owns its own data! #indieweb @indiewebcat https:/
WordPress › Support » Some excellent changes this week
https:/
It's some of the recent changes that are starting to make me use it more, almost to the point that I'm ready to throw WP's built-in post-formats out and rely solely on Indieweb Post Kinds.
Watching your evolving work and some of the others within the Indieweb/WP group makes me want to go back and brush up on my terribly old/rusty programming skills -- it's just taking me longer than I'd like with my current work schedule -- particularly as this seems to me to be the right way to run the web.
Keep up the great work!!