@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://indieweb.org/Indieweb_for_Education page and subsection them out as they grow in size and scope? If there are consuming applications for differing types of metadata, let's list those. The best answer may be to begin documenting pieces of what are out there and then figuring out a way to create more IndieWeb or decentralized and open versions of them. Having an editable, but centralized source of information can certainly be helpful. (Unless you know of another that already exists?)

Photography, Graves Disease, Insulin pumps and a lot of other things

Improving the h-card in Grav

I spent a little time fixing up the way this site presents my h-card on the summary of blog posts. In case you're wondering, an h-card is a way of presenting information about yourself or your organisation on your website that makes it easy for other websites to identify you with your work, for example in webmentions. More this way ...
There is also the counterpart: 'untag-of' posts (https://indieweb.org/untag) which are more of a brainstorm at this point, but I figured worth pointing out as a future enhancement, in case that helps generalize the code for 'tag-of' support.

Problem: currently you have to use Github’s web UI to remove a label from an issue.

If you could post an 'untag-of' response to a GitHub issue, and Bridgy Publish recognized that, it could call the GitHub API to (attempt to) remove the respective label from that issue.

The current brainstormed markup is similar to that for a 'tag-of' post, but with class name 'untag-of' instead.

Feedback and contributions welcome on https://indieweb.org/untag

Also reasonable to consider 'untag-of' support a potential future separate issue rather than as part of implementing 'tag-of' support.

Enhancement: Bridgy Publish to GitHub should POSSE tag-of posts to add labels to issues

@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...
Reminder! @oktadev is buying drinks at tonight's Homebrew Microblog Meetup! 🍻🔜 https://indieweb.org/events/2018-04-18-homebrew-microblog Looking forward to meeting everyone tonight!
@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://boffosocko.com/2017/12/15/threaded-replies-with-webmentions-in-wordpress/

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.

An Introduction to the IndieWeb

A thorough run-down of the whys and wherefores of being part of the indie web, from Chris.

#indieweb #personal #publishing #ownership #silos #control #freedom #posse
Upon reconsideration, I retract my suggestion in https://github.com/microformats/microformats2-parsing/issues/10#issuecomment-331511675 that "this issue's resolution should depend on resolving #9 first", and commented on how to orthogonally resolve issue #9 (http://tantek.com/2018/107/t1).

As promised in https://github.com/microformats/microformats2-parsing/issues/10#issuecomment-331499024, I’ve added PROPOSED text inline in the u-* parsing section per the proposal of this issue: http://microformats.org/wiki/index.php?title=microformats2-parsing&diff=66782&oldid=66724.

I see github.com/aaronpk’s agreement with this proposal, and would like to see at least one, preferably 2-3, more parser developer(s) explicitly agreeing as well.

We also need to see this proposed change prototyped in at least one parser to make sure it is implementable (seems like it) and to see if there are any unintended consequences.

My micropub client works for the actual note, but location data isn’t being sent with the request. ☹️

I really enjoy these development logs. I think you’ve inspired me to start doing them for my own app, Indigenous, which is more IndieWeb focused but will support micro.blog kind of as a sibling relationship.

Episode 1: Leaving Facebook?

“the Twitter system doesn’t recognize that it’s encouraging people to follow additional extremist accounts, and Facebook’s Groups engine doesn’t understand why directing conspiracy theorists to new conspiracy communities is possibly a bad idea.” https://www.wired.com/story/creating-ethical-recommendation-engines/ #Indieweb

An indie reader (I probably shouldn’t have used caps. Haha) is an attempt at getting the Facebook/Twitter like experience into feed readers. So that one can control what content they read and yet enjoy the reply/like/save functionality that exists in modern social media. This page provides some additional info: https://indieweb.org/reader

I found that I have so many channels in my IndieReader that it was starting to create stress when I opened it. So I’m testing out viewing only channels with new content. Eventually this will be a filter setting you can quickly switch back and forth between
#indieweb #reader #microsub

FYI in terms of easy and iOS. One option on Jekyll or Wordpress is Micropub (https://indieweb.org/Micropub). Wordpress has plugins and Jekyll has options (https://indieweb.org/Jekyll). Then you can use Indigenous (https://indieweb.org/Indigenous_for_iOS) to post

By replying on my site, I am using @schnarfed's service to collect tweeted responses, then both his service and my site have cached copies of the reply and the name photo and url of the responder. @ade_oshineye could do that with webmention.herokuapp.com on his static site too.

It’s a Journey

Awesome! Those are some great updates! Especially the automatic webmentions (something I want to do soon) and the h-card embedded of person tags.