The reply to site won't be visible to most as it was a private message, but someone asked about how to get started on building their own Little Free Library branch. My reply:

I wrote a little bit about my building process here: http://lfl8424.boffosocko.com/our-story-history-and-building-process/

You can find most of the details for set up and registry on http://www.littlefreelibrary.org. (They actually just updated their website over the weekend.) They have libraries that you can buy and they'll ship to you, though part of the movement is encouraging people to be creative in building and designing their own. I'm happy to help give you some ideas if you need the help, but their website and examples they have on their Facebook & Pinterest sites will surely help too. Visiting a few in the Glendale & Pasadena Areas might help as well - you can find a map at http://littlefreelibrary.org/ourmap/. I notice that several of the Glendale City LFL's aren't on the map, but can be found by googling "Glendale" and "Little Free Library" where you'll find the city's Library, Art and Culture page with addresses for all of them. There are several at nearby city parks as well as at city hall.

There's also a nice little book about building and hosting your own as well. You can find it on Amazon at http://amzn.to/1gtCPKP

The BookCrossing.com and GoodReads.com portion I've integrated into mine are unrelated websites that are used for releasing and tracking books out in the wild, but that both work with the LFL concept really well.

I've done a lot of research on the upfront side, so I do know quite a lot about the overall concepts, but obviously have only just opened my own. I'm happy to provide as much or as little help as you might need, just let me know.

Best,
Chris

#LittleFreeLibrary #LFL8424

+1 from me on this feature request. (It would be cool to see an awesome theme like this also support microformats v2 as well. Sempress is the only theme out there that does this already see: https://github.com/pfefferle/SemPress, so it would certainly set the theme apart.)

@raumzeit77 As a temporary fix for the IndieAuth piece, you could add a text widget to your site that helps you get compliance with some of the IndieWeb Specs. You can also repeat some of the social icons with "invisible" links so that they don't actually display on the page, but are machine readable for IndieWeb purposes. It's not the best fix/workaround as you'll need to remember that the "invisible" code is there at some later date, but it should get you over the hump. Keep in mind that not all providers work with IndieAuth, though platforms like Twitter and GitHub do.
Try putting the following into a text widget (some portions will be visible others, link tags for example, will not):

<pre><code>
&lt;div class="h-card"&gt;
&lt;link href="https://facebook.com/USERNAME" rel="me"&gt;
&lt;link href="https://twitter.com/USERNAME" rel="me"&gt;
&lt;link href="https://plus.google.com/+USERNAME1/posts" rel="me"&gt;
&lt;link href="https://www.pinterest.com/USERNAME/" rel="me"&gt;
&lt;link href="sms:+12125551212" rel="me"&gt;
&lt;link href="mailto:me@emailaddress.com" rel="me"&gt;
&lt;br/&gt;&lt;br/&gt;
&lt;img rel="me" class="u-photo" src="http://domainname.com/site_icon.png" alt="" width="200" height="200" /&gt;&lt;br/&gt;&lt;br/&gt;
email: &lt;a class="u-email" href="mailto:me@emailaddress.com"&gt;me@emailaddress.com&lt;/a&gt;&lt;br/&gt;
phone:&lt;span class="p-tel"&gt;&lt;a rel="me" href="tel:+12125551212" &gt;+12125551212&lt;/a&gt;&lt;/span&gt;&lt;br/&gt;
&lt;p class="p-note"&gt;
&lt;span class="p-job-title"&gt;President&lt;/span&gt; and &lt;span class="p-role"&gt;CEO&lt;/span&gt; at &lt;a class="p-org" href="http://domainname.com" target="blank" &gt;Company Name&lt;/a&gt;; &lt;br/&gt;
&lt;span class="p-locality"&gt;ANYWHERE, NY &lt;/span&gt;&lt;span class="p-country-name"&gt;United States&lt;/span&gt;&lt;/p&gt;
&lt;/div&gt;
</code></pre>

Some of the code will also qualify you for some additional levels within the IndieWeb identification space relating to h-card.

#IndieWeb

My @Quora answer to Is there a quick way to republish Twitter updates onto a blog? http://www.quora.com/Is-there-a-quick-way-to-republish-Twitter-updates-onto-a-blog/answer/Chris-Aldrich?srid=qkX

There are a small variety of answers here some of which (including Ashton Kutcher's suggestion of the formerly awesome ping.fm) are already defunct in less than a year or two, which indicates the fickle and rapidly changing nature of the internet.

I'll start by not accepting the premise of the question, but modifying the conceptualization to something more interesting and robust. Since there are hundreds upon hundreds of defunct web services many of which have died with little to no advance warning and which more often than not were information silos that didn't allow their users to export their data (see: site-deaths - IndieWebCamp [http://indiewebcamp.com/site_deaths]), I would highly recommend asking the following question instead:
"Is there a quick way to cross-publish or syndicate my content to Twitter?"

The hidden sentiment of the original question: "how can I easily keep my own data in the eventuality that Twitter disappears?" is really the root of the problem and is one which the IndieWeb movement has been diligently working on for several years. I'll let them speak for themselves:

Your content is yours
When you post something on the web, it should belong to you, not a corporation. Too many companies have gone out of business and lost all of their users’ data. By joining the IndieWeb, your content stays yours and in your control.

You are better connected
Your articles and status messages can go to all services, not just one, allowing you to engage with everyone. Even replies and likes on other services can come back to your sites o they’re all in one place.

You are in control
You can post anything you want, in any format you want, with no one monitoring you. In addition, you share simple readable links such as Page on example.com. These links arepermanent and will always work.
-- Source: IndieWebCamp [http://indiewebcamp.com/]

The general philosophy is that it is easy enough to own your own site, own your own data, and then syndicate it out to any of the variety of content silos that exist (while sucking additionally created follow-on data, such as comments, likes, etc. back into your own site), so that you can simultaneously take advantage of the network effects of these silos while still owning everything and not chancing that it will disappear without warning. I'd highly recommend surfing around the IndieWebCamp site for a bit, but I imagine that most will find it actually describes the way many wished the internet worked.

Now that we've got the background philosophy of the question sorted out, let's take a look at the semantics of the solution. The question is essentially asking about the IndieWeb concept of Publish (on your) Own Site, Syndicate Elsewhere (aka POSSE [http://indiewebcamp.com/POSSE]). The mechanics are somewhat different depending on the home platform on which one builds one's site, but almost all platforms allow one to at least post the "headline" of their post along with a permalink manually. IndieWeb forward platforms like Wordpress, Tumblr, Drupal, and WithKnown either have the functionality to cross-post to twitter automatically or do so fairly easily with simple and free plugins (e.g.: WordPress's ubiquitous plugin has a "publicize" functionality that allows crossposting to major silos like Facebook, Twitter, Google+, Tumblr, and LinkedIn among others). Most of these also have either built in or plugin functionality to pull comments, likes, and reshares from the specific silo back to the original content, so that all of it is memorialized in the same place. For those that need it, the POSSE page at IndieWebCamp (linked above) has a variety of ideas and resources for a variety of platforms.