@MailChimp @MailChimpStatus @MailChimp_API @MailChimpUX Can you help WordPress community out here with a response? https://github.com/crowdfavorite/wp-social/issues/213#issuecomment-282094259

I'm not seeing the HTML export on the desktop version of Kindle (from 2015) on my work laptop at the moment, but I'm positive it's hiding somewhere on my desktop machine, which is currently out of commission for some quirky problems. When I get it running, I'll try to document the feature as I don't think I've seen it mentioned anywhere else and it was tremendously easy and helpful.

I hadn't tried Bookcision as I'd stumbled across what I supposed was an easy answer, but there are a few edge cases for non-Amazon books in my collection that might benefit from using it as Amazon doesn't always play well with content that doesn't originate from the "mothership".

A while back, I'd bookmarked http://the-digital-reader.com/2015/02/21/how-to-download-your-kindle-notes-and-highlights-and-export-them/ as one of the better articles explaining most of the pathways currently available. If I remember the comments were relatively helpful as well.

For general file conversion you might appreciate Pandoc: http://pandoc.org/

There are also some in the community who have tools (like Kevin Marks' http://www.unmung.com/ ) which can do inter-conversion. I can't recall specifics at the moment, but someone in the chat will likely know of the others, or you can search github to find some of the opensource ones https://github.com/search?q=indieweb&ref=opensearch (it can be an interesting browse in general for things you didn't know you needed/wanted).

Finally, I liked the teleprompter.css hint for marked2, but if you've not come across it, I often read newspaper, magazine articles, and fiction on my mobile using RSVP-related technology (Rapid Serial Visual Presentation) which has been patented (though I'm not so sure it's enforcable) by http://spritzinc.com/get-spritz and for which there are multiple apps floating around for multiple platforms. My favorite thus far is Balto-reader which I think may only be available in the Amazon store, but it's one of the few I've found that can break through Amazon's encryption to allow using Spritz-like technology on my Kindle Fire or Android Phones. I don't recommend using it to read technical documents or passages which require more thought, but it's lovely on mobile and has a nice bookmarklet for reading web-based articles quickly. If it's something you think you'd use, but you can't find something that can access Amazon books, let me know and I can suggest some workarounds that will allow Amazon book access.

Eric, You'll get used to it all pretty quickly. Feel free to use my site to ping against if you want to test things out without annoying someone.

If you want a potential set up for using it with your mobile phone, try: http://stream.boffosocko.com/2016/sharing-from-the-indieweb-on-mobile-android-with-apps-and

It looks like you're using the hosted version of Known, but it you ever self-host, there's lots of additional goodies at: http://docs.withknown.com/en/latest/plugins/community/

@dagutierrez With interests in this area, you might appreciate some of what the #Indieweb community is doing: http://indieweb.org

@pfefferle And there in a small nutshell is both the power and the drawback of part of the movement, particularly on a platform that powers 25% of the internet. I'm in the same boat with you (though my coding skills are far behind), but I thought I'd write down the blue sky idea as a potential target for the future. Perhaps we should follow Manton Reece's lead and create a Kickstarter campaign to fund such a thing? (_Said in half-jest/half-seriousness_).

I suppose the thing to continue focusing on is steady improvement of what already exists. Eventually a group of developers will join us all and separately or together we'll have the free time to bundle it all up the way we all imagine it sould be done on a salaried basis.

If I (or we, speaking on behalf of the rest of the community) don't say it often enough, **THANK YOU** again @pfefferle and @dshanske for your heroic efforts on behalf of the IndieWeb within WordPress.

Jeremy, Like you, I had some of the same issues and questions when I first started. I'd had a primary website for a while that was a bit more blog-ish on WordPress with a few other subsidiary sites for work related things. When I got into IndieWeb, WithKnown had a great plug-and play set up for almost everything, so for me, it made a nice easy place to start. I also wanted to play with Known and use it to get my feet wet. I was particularly interested in owning a lot of the shorter form posting/microblogging like Twitter without overwhelming my prior subscribers on my WordPress blog with a lot of shorter "fluff". Once I'd gotten a few things working, Known was also incredibly good at quick short posts using bookmarklets (or this mobile solution I'd come up with: http://stream.boffosocko.com/2016/sharing-from-the-indieweb-on-mobile-android-with-apps-and ). Initially the big difference between my sites was where I stored longer form content and shorter form.

Slowly over time, as I've been adding bits and pieces here and there to my WordPress set up, it has been owning more and more while somewhat less lives on my Known Install. There's also been a huge amount of community development on the WordPress side, so that it's tremendously better now than it was when I started and continues to grow. I think I hit a bigger turning point after IndieWebCamp LA when I was able to work out a bit more about how I want to own and syndicate things from my primary hub (on WordPress). (See also: http://boffosocko.com/2016/12/18/rss-feeds-a-follow-up-on-my-indieweb-commitment-2017/ which has some thoughts about adding RSS feeds from one site to cover multiple other sites). The nice part about owning your own site is that you get to figure out what to do with it and you can literally do almost anything. For example, very shortly I'm about to attempt to own all of my checkins on my WordPress site instead of on Known as I've got almost all the moving pieces to do it in a way I like.

Ultimately, I'd recommend doing what works best for you at the moment as there are literally hundreds/thousands of ways to pull it off. Do things one at a time in small bite-sized chunks until you have it the way you want it. There's no reason to do everything all at once. Sometimes I've found that creating posts literally by hand in raw html has been a great way to start to see both how it looks/works, and then use that experience to figure out how to best/most easily automate it going forward.

I'll also note that my coding skills were old and rusty and have been slowly getting better over time as each piece evolves. Another nice part of the process is that you'll have a chance to see how others are doing things with examples from the wiki to help you figure out what might work best for you. Over the process I've also seen others stop, change gears, and even platforms, and try out something totally different. The key seems to be to start with something you know and begin working from there based on your particular "itches" and needs [http://indieweb.org/itches]. Document in the wiki pages what works for you and what doesn't and why to help others along the way. What works for you won't necessarily be the best solution for others and vice-versa, but there's lots of examples out there to work off of.

Your post was certainly a good start for taking stock of what you've got and where you might like to go. Now just make a list of your itches and do things a step at a time. I know there's an IndieWeb Cat [https://indiewebcat.com/] and an IndieWeb Library [http://boffosocko.com/2016/07/16/the-indieweb-ified-library/], so I'm glad to think that there might be some IndieWeb bread out there soon too. (This reminds me that I want to get back to microformats for recipes again in relation to JetPack's shortcode work: https://jetpack.com/support/shortcode-embeds/).

Good luck!

The errors can sometimes be a result of which version of PHP you're running. Double check that, though I'm not sure what the minimum threshold Known requires at the moment. Usually these days v5.6 is a good sweet spot. Versions under 5.5 may cause errors like what you saw and I know my stupid host often defaults new installs to 5.4 for some reason.

You can also check to see if it's a known issue in the open or closed queues at the github repo: https://github.com/kylewm/KnownReactions/issues

Otherwise cut/paste the error(s) into the issue queue in the repo to see what what others in the community think it could be.

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

@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.