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.

Chrome display issue in Refreshed CSS · Issue #12 · indieweb/chat.indieweb.org https://github.com/indieweb/chat.indieweb.org/issues/12

Per our conversation here's a screenshot of what's happening:

Essentially the bar on the left is covering up most of the chat commentary, which needs to be shifted over. Doesn't seem to be happening on any of the other browsers I tested -- only chrome.

Sounds like a reasonable solution. I'd imagine that in most cases (to be safe) that if there's not a featured image, then posts to twitter would generally be just the text update as that's how most people typically use twitter.

Is it looking for photo related microformats with regard to identifying/pulling photos? I actually thought it was interesting/relatively nice that it automatically pulled the three photos and laid them out that way, but in that case I'd have done higher res photos for better clarity. The "indieweb mini-logo" is a really small icon way down in the footer of my page and I was most shocked that it popped up on the post.

I typically have been using SNAP for POSSE, but as I've been watching your work recently, I felt compelled to test out Bridgy Publish to give you some feedback about UX/UI as well as bang on things for bugs in general.

I remember looking at Rebelmouse and thinking it was very interesting, but I was doing so probably at just about the same time I was getting into the IndieWeb concept and that killed it all for me.

Sorry to hear that it's all going down as I know how much you've invested in it. Plans to build a replacement? ;) I've been doing some thinking about how to better/more easily do content curation in an IndieWeb forward manner, but yet to have work out a complete workflow for it.

Like you, I usually don't worry too much about SEO either, particularly for my personal site.

The IndieWeb community has recently been moving domains from IndieWebCamp.com to IndieWeb.org, so there have been some relatively big changes there which have thrown some functionality off. In particular, one used to be able to jump into the chat directly from the web-based chat logs, but that has been turned off (temporarily, I hope). If you don't want to set up an IRC client [details and suggestions are given at https://indieweb.org/IRC], you can also use the more friendly Slack channel as well since the IRC chat is bridged to Slack. Just click on the link on the IRC page to sign up. (I've never been a big IRC fan either, and the fewer chat clients, text messengers, etc. I can have, all the better!)

If you've managed to get WordPress installed, then you've already done the lion's share of the hard work! Most of the rest of "IndieWeb-ification" is done with simple plugins and minimal amounts of configuration. There shouldn't be anything too much more difficult (unless you want to get your hands dirty and do some hardcore coding.)

My main www.boffosocko.com site is a WordPress install, which I usually use for longer form (more interesting??) posts. stream.boffosocko.com is more quick hit content: status updates, checkins, and some photos. I also find it's a bit easier to use on my cell phone than WordPress is. It's built on the Known platform which was built from the ground up in part to support IndieWeb protocols.

If you'd like to join a small group of us in Pasadena on Wednesday night, I'm walking a few new people through some IndieWeb stuff: https://indieweb.org/events/2016-07-27-homebrew-website-club (Facebook copy at https://www.facebook.com/events/1176904038997597/). We can help you walk through the process on your site if you'd like.

I hope to have monthly meetings through the end of the year in the LA area, and there's a bigger IndieWebCamp in Santa Monica in November (https://indieweb.org/2016/LA)

I have just gone through the process of setting up Medium's plugin, so I'm giving that a spin for a couple weeks prior to kicking the tires of SNAP's integration. SNAP has done an excellent job on other platforms, so I'm guessing they're using all the available features there and probably have a stronger 1-1 mapping of data from one platform to the other, particularly as Medium is aiming at WordPress directly first. The one thing you might want to be careful about with Medium is making sure you don't have a "rel=canonical" tag [https://indieweb.org/rel-canonical] showing up on your Medium post, otherwise you might be getting docked by Google and others with respect to SEO. I know the Medium plugin handles this well, but haven't checked on how IFTTT or SNAP handle this yet.

I'm curious what specifically you found confusing about IndieWeb? Some of us in the WordPress group have been trying to make the value proposition and workflow better, particularly over the past several months. (Admittedly, before about April, the onboarding process was MUCH messier and the end user had to do a lot more reading/discovery and work to set things up, but I think the hurdle has moved much lower since then.) If you take a look at it again, I'd love to know where you experience problems/issues, so we can make things better for others. If you need help, there are many of us on IRC [https://indieweb.org/IRC] who can often help in real time.

As for privacy, in general, Facebook, Google+, et all are all public facing networks, so people posting there are really posting for everyone to see in the first place. If they're posting privately, I believe that the IndieWeb protocols respect that and don't import private webmentions. Most of the rest is about data ownership for you and your blog as well as trying to maintain a central repository for your blogs posts of all the conversation taking place around what you're posting. Part of the downfall of social media is that it can often fragment conversations. In some sense IndieWeb helps glue them all back together.

On your last point, I had a bit of cognitive dissonance with this as well when I started into IndieWeb, but I've just streamlined my workflow significantly (and for the better). I've turned off all the emails and notifications from individual social media platforms (at least as they relate to my content) and I rely on my WordPress install to do all the notifications. This way, for example, when someone replies to one of my posts on Facebook, I see the webmention via WordPress, and then use that to click on the contained link to the reply on Facebook. I'll then reply natively on Facebook so the other party sees it there (typically by Facebook notification), but then the IndieWeb backend ports over my comment back to the comments section of my own blog. My "audience" can follow me on their platform of choice, and I can still interact, but I still own all the resulting data: Win-win-win!

Five out of Five Stars! Own All of Your Instagram Data

This plugin is fantastic and thorough in the sheer quantity of data that it will export out of Instagram for you. It has a simple and relatively elegant interface to help you display and format your post(s) automatically including all the meta data, post types, tags, categories, etc. They truly have thought of everything in making a spectacular little plugin!

I use this in combination with Brid.gy and some IndieWeb.org related WordPress plugins which also allows me to backport all of the likes and comments from Instagram as well, and between the two, Instagram could go down tomorrow and I would own all of the data I've put into the service. DsgnWrks has literally done all of the heavy lifting.