@amichaelberman It would be interesting to use that data to indicate verified Twitter accounts...

@khurtwilliams A bunch of us are working on making it all easier in steps, but we're also doing it on a volunteer basis. Some of the key is knowing what it all comprises from a top-down perspective, then knowing what each of the individual pieces are and how they work. Nearly every week there's something new and cool. The key is to figure out which things you find the most useful and valuable and work on those one at a time.

It's a LOT easier now that it was even 8 months ago and will be measurably easier as time goes by. I'm currently writing a book on how to do it all at the level of "IndieWeb with WordPress for Dummies". Ideally it'll be as easy to do as signing up for a Twitter or Facebook account and just going, but we're not quite there yet, but it's getting easier to do the set up without knowing a lot of (or any) code. Hoping into the chat, going to a Homebrew Website Club or IndieWebCamp can be immeasurably helpful as well.

Again, if you want to do a quick conference call/video chat, I'm happy to help you out.

@khurtwilliams POSSE for WordPress can be tricky in part because, compared to most other IndieWeb pieces for WordPress, there are multiple different and varying ways to do it. Using one method could potentially conflict with another depending on how you set things up, though I think these are relatively few.

Your best bet is to hop into the #WordPress channel of the IndieWeb chat https://indieweb.org/discuss and ask for help, particularly to discuss the specifics of what you'd like to do and what you expect.

In general, the more control and flexibility you want over the display of your POSSE posts, the more set up and work you have to put into it (e.g. SNAP), while the less control you have the more simple the set up (e.g. JetPack Publicize).

Things like Brid.gy publish functionality (or via the Brid.gy Publish plugin) can be more finicky for POSSE copies to silos because Brid.gy is parsing your site for the proper data to publish. (It does have a preview button built in to do manual tests if you need to.) This means that if your WordPress theme doesn't have the correct microformats markup (and often they don't), then you can get spurious results, particularly when it comes to crossposting photos.

Most of the main POSSE plugins and tech are very stable in fact, but they do require that you do a bit of reading and understanding what they do and don't do and what you can and can't control with them. Most all of them have GitHub repositories that you can post issues to and almost all the devs, maintainers, and community are happy to help you out and/or make changes to make the UI and documentation better.

As for backfeed from Brid.gy, it generally requires that the URLs of your post and the syndicated post have matching permalinks to be able to match the two up to send you the webmentions properly. You may have changed your settings, but one piece you appear to be missing is the Syndication Links Plugin which allows you to add u-syndication links to your posts so that Brid.gy knows which ones to send your responses to. Much of this is documented at https://indieweb.org/WordPress_with_Bridgy It also looks like you don't have either an h-card or the appropriate rel-me links on your pages for Twitter, Facebook, et al. Brid.gy is pretty well documented, so you may want to take a look at some of the options there directly. https://brid.gy/about If it helps, you can do a lot of interactive stuff with Bridgy by manually creating posts with specific html in your posts directly. Understanding how to do this can be helpful later when you switch to using a plugin to help automate part of those processes.

I'm sure I've got a few odd posts from ages ago when I tested things out, but when you say "I can also see from some of the failed posts on your website that you may experience the same issues." I'm curious which particular posts you mean? To my knowledge things I intend to syndicate out are currently working as I expect them to (aside from one quirk that occasionally spams the Indieweb chat with micropubbed posts which continually redirect, but that's specific only to me because of some experimental code I've been running). It is the case that I don't always syndicate everything to each and every silo target I could. I do very much pick and choose which things to syndicate to particular networks.

We'll help you get there yet!

@benwerd Was just wondering the same thing--in relation to the NYC incident. There's no link, but if you click, it goes to Twitter Moments.

There had been an interesting work around to fool Twitter, but they closed that loophole pretty quickly. Links found through here: http://boffosocko.com/2017/10/18/heres-a-hack-so-you-can-tweet-with-280-characters-right-now-the-verge/

@moorehn @NYFarmer Besides @herdyshepherd1 and @shaunthesheep, who really needs anything else on Twitter??