@MarinaSGerner I liked your work (and your website) so much, I had to write about it: http://boffosocko.com/2017/01/13/the-indieweb-and-journalism/

Rob, there's a plugin for that! You can find a bunch of extensions in http://docs.withknown.com/en/latest/plugins/community/

For likes and reposts, you'll want Kyle Mahan's "Reactions" plugin.

Once that's done, if you want to add a mobile option you might take a look at http://stream.boffosocko.com/2016/sharing-from-the-indieweb-on-mobile-android-with-apps-and

@clacke, I think @marcoarment was refering to @manton2's effort here https://marco.org/2017/01/07/indie-microblogging-kickstarter; it does sound like @withknown
w/ a reader-first perspective and using IndieWeb principles [http://indieweb.org]. Based on what I've read there will be a hosted version with great export, but with self-hosting available for those who'd like to truly own their own data.

@realkimhansen @kevinmarks May need to dust off my signal processing skills and do something about that to add to http://indieweb.org/podcast

@cswordpress I hadn't run across the keyboard issue with the bookmarklet yet, but I'm glad you're taking a look at fixing it. If you get some time, feel free to add your fix and links to the code at http://indieweb.org/accessibility so that others can benefit from your expertise. I know there was some significant discussion about accessibility at one of the early IndieWebCamps in 2016, but I don't remember which.

Several of us in the WordPress IndieWeb "camp" have been pushing to have more microformats2 compatible themes available to increase the selection. If you can push the Genesis framework project to include them, that would be phenomenal! Some of the notes on this work can be found and added to at https://indieweb.org/WordPress/Development#Brainstorming

@cswordpress @webrocker I'd noticed that WP-Social quit support a while back, but didn't know why; sorry to hear it. I wrote some thoughts here [https://github.com/crowdfavorite/wp-social/issues/213] for those who need alternatives and IndieWeb tech is a great solution in my opinion.

If you go the route of API's you're on the hook for maintenance which can be troublesome at best. If you want a PESOS solution there are a few options listed on https://indieweb.org/WordPress/Plugins. I've tried Ozh's version which is pretty good. I've used DsgnWrks Instagram importer before, but not the Twitter one, so I know his code is pretty solid.

If you have a few minutes, you might find that POSSE is a better/more robust method, in which case you could set up the basic IndieWeb Plugin and use JetPack's Publicize (or SNAP or something similar) to syndicate your status updates to twitter. https://indieweb.org/Getting_Started_on_WordPress

I'd be happy to help you if you have questions. Many of the developers of these plugins spend time in the Indieweb Chat [http://indieweb.org/IRC] and are happy to help with questions, problems, or take feedback to improve the tools.

@cswordpress @redcrew Thanks for the recommendation Amanda!
I'm guessing you installed PressForward directly on your production server without using a test environment? I can tell because all of your posts are trying to redirect, but are redirecting to themselves! It's a known bug I mentioned here: http://boffosocko.com/2016/12/31/pressforward-as-an-indieweb-wordpress-based-rss-feed-reader-pocketinstapaper-replacement/#run+across+an+issue+with+the+automatic+redirect that Aram has apparently fixed in the Github repo and will push with the next update. https://github.com/PressForward/pressforward/issues/878

Until then you may want to go to the settings and set the redirect time to "0" which will prevent all of your pages from continually re-loading OR you could uninstall it from your production site and run on a test server.

I've been loving it since I installed and can't wait for the forthcoming patch. I'm curious what others think of it for the off-label use I've proposed.

@ivasef85 @lukashmayyn @Anthony I also have @mentions on my site courtesy of an Webmention implementation. https://indieweb.org/webmention

@Nasharchy @tauriqmoosa I'm betting that efforts like http://indieweb.org or @manton2's https://www.kickstarter.com/projects/manton/indie-microblogging-owning-your-short-form-writing may help

It's called PressForward. I wrote up some more details here: http://boffosocko.com/2016/12/31/pressforward-as-an-indieweb-wordpress-based-rss-feed-reader-pocketinstapaper-replacement/

@aaronpk @indiescripter Another option to encourage others to post their replies on their own sites rather than directly on yours, you could provide a URL box and details for people to webmention you indirectly (especially if they don't support Webmention yet). See the comment section at the bottom of http://boffosocko.com/2016/12/28/homebrew-website-club-los-angeles-notes-december-28-2016/ for an example or see https://github.com/pfefferle/wordpress-webmention-form for some sample code. I think I've yet to have someone take advantage of the option, but my IndieWeb heart feels warm for providing it as an encouraging option.

For additional ideas, see: http://indieweb.org/web_actions

@indiescripter I think you've probably got a pretty good start on the IndieWeb philosophy. And an even better start in that you're writing your thoughts on your own website first and then syndicating them to silos like Twitter.

I think that part of what you're missing about being able to reply to Aaron's original post is that his site both sends and accepts a new web protocol known as Webmention (http://indieweb.org/webmention). Thus on his original post, you'll see that I've "liked" it by making a post on my own site (http://stream.boffosocko.com/2016/liked-aaron-pareckis-100-days-of-indieweb-147eda7b83), and then in the background sending a webmention from my server to his to notify him about it. He can then decide whether or not to accept and/or display it (in this case mine appears next to his star icon at the bottom of the post). For the likes and comments/replies on his post, you can hover and find the permalinks for all of the responses on other people's originating sites. I'm sure yours would have shown up too, but I suspect that your site isn't sending webmentions yet, so his site is unaware that your post exists. I'm sure he'll have seen the Twitter response you gave though.

I know Aaron also often syndicates copies of his posts to Twitter. There's another IndieWeb related service known as Brid.gy which bootstraps webmentions onto Twitter (in addition to other social silos) so that replies or comments to the copy that got syndicated to Twitter also send copies to the original post. In this case, he only syndicated it to news.indieweb.org, so it was less simple for you to have interacted with his post because there wasn't a Twitter version for you to interact with.

You'll find that within the broader community that different members will support varying levels of functionality (based mostly on what they're interested in), so someone like Tantek (tantek.com) will post on his own site and syndicate to Twitter, but he doesn't yet display webmentions. You can, however, post your replies to him on your own site and syndicate them to Twitter (perhaps using Brid.gy publish?) to reply to his syndicated copy on Twitter where he'll see the notification of your reply. You yourself serve as another example as you don't (yet?) offer a comment field on your own post. Perhaps you may never, but that's your choice. (I'll mention incidentally that many static website owners are using Aaron's Webmention.io for sending/receiving webmentions, see also: https://indieweb.org/webmention.io.)

I think that a lot of the goal is to not only have fun with what you're doing on your own website, but do things which you find interesting/useful for yourself. Are you interested in locations/check-ins [http://indieweb.org/location]? Reading related posts [http://indieweb.org/read]? Maybe other types of status updates [http://indieweb.org/posts]? Always work on your own itches [http://indieweb.org/itch] first.

Just be careful, because lurking in IRC or browsing the IndieWeb wiki for a while and seeing what others are working on or doing can make you very "itchy". Though the reverse is true that seeing what others have done (even how silos have done things in the past) can make it easier for you to build it not only better, but perhaps more quickly. Perhaps the CMS or language you're using is being used by others in the community [http://indieweb.org/projects]? This may make it easier for you to go farther/faster by using their opensource code, or perhaps make it better by contributing some of your own thoughts/feedback/code?

Keep up the search, and let us know if we can be of further help/assistance.