An application for turning your tweetstorms into blog posts.
Ruby HTML Other
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
app TimelineUpdater now asks for 200 tweets (instead of the default 20), … Oct 19, 2016
db Now you can hide a tweetstorm on the index page if you've already led… Jan 20, 2016
public rails new embloggen Jan 17, 2016
spec TimelineUpdater now asks for 200 tweets (instead of the default 20), … Oct 19, 2016
vendor/assets rails new embloggen Jan 17, 2016
.rspec Add a contributor code of conduct. Thx @coralineada :) Jan 19, 2016
Gemfile You can now connect to the twitter API to get tweets that are newer t… Jan 18, 2016
Gemfile.lock MIT baby Jan 18, 2016


A Rails application for turning your tweetstorms into blog posts.

How to get it going locally

  1. Download your tweet archive from Twitter from Account Settings. You'll need the tweets.csv file that comes in that package.
  2. Clone the repo.
  3. Install Ruby 2.2.3.
  4. Install postgresql.
  5. gem install bundler
  6. bundle install
  7. Edit config/database.yml if you don't want to use the default pg user & password.
  8. rake db:create
  9. rake db:migrate
  10. rake import_tweets['path/to/tweets.csv'] replacing 'path/to/tweets.csv' with the actual path to the CSV file.
  11. rails server
  12. Visit http://localhost:3000 to see a list of all the roots of your tweetstorms. Roots are defined as tweets that are:
    • from you
    • not in reply to another tweet
    • that you replied to
  13. Choose a tweetstorm and select "See whole storm" to see the reply chain rooted at that tweet.
  14. From that page, select "Make a draft" at the bottom. This puts all the tweets in that storm into a textbox, separated by newlines, where they can be copied out into a real editor somewhere.

If you'd like to be able to add tweets that are newer than your archive to the database, you'll additionally need to do the following:

  1. Go to to make a new twitter app for your local version of Embloggen. You don't need to give it a real website and you can leave callback URL blank.
  2. Once you've created an app, you'll see its consumer key and consumer secret. Copy those into your ~/.bash-profile:
export EMBLOGGEN_TWITTER_CONSUMER_KEY="your consumer key here"
export EMBLOGGEN_TWITTER_CONSUMER_SECRET="your consumer secret here"
  1. Lower down on the management page you'll see a way to create an access token and access token secret. Do that and then copy them into your ~/.bash-profile too:
export EMBLOGGEN_TWITTER_ACCESS_TOKEN="your access token here"
export EMBLOGGEN_TWITTER_ACCESS_TOKEN_SECRET="your access token secret here"
  1. You may need to open a new shell to get those exports. Once you have them though you'll be able to use the "Refresh my thoughts" link on the homepage to fetch new tweets.

Wish List

  1. Less ugly.
  2. Mark tweetstorms Not Interested or "I've already led those thoughts", so they don't show up in the list anymore.
  3. Save/edit a draft attached to a storm.
  4. See back versions of a saved draft.
  5. Connect to Medium to create a draft there.
  6. Connect to Wordpress to make a draft there.
  7. Update the archive via API.
  8. Import /update through the UI.
  9. See other people's recent tweetstorms via API.
  10. See mentions (from other people) alongside the tweetstorm, via API.
  11. Support multiple users?


MIT - see

Code of Conduct

The project has one! Please see for details. By participating in this project, you agree to abide by its terms.