wes
/
TweetLog
1
0
Fork 0
Code Issues 1 Pull Requests 1 Projects Releases Wiki Activity
A Simple Tool To Archive Twitter Threads
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
17 Commits
2 Branches
0 Tags
138 KiB
 
 
Tree: ed6bf0ddf9
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'ed6bf0ddf9'
${ noResults }
Wesley Kerfoot ed6bf0ddf9
use code blocks in readme 		4 years ago
src write proper help message 4 years ago
tests initial commit 4 years ago
.gitignore initial commit 4 years ago
README.md use code blocks in readme 4 years ago
config.nims initial commit 4 years ago
twit2blog.nimble initial commit 4 years ago

README.md

Twit2Blog

A simple tool to help make it easier to turn your tweet rants into real blog posts

Building

nimble build is all you'll need at this point.

Usage

Requires TWITTER_CONSUMER_KEY and TWITTER_CONSUMER_SECRET, both of which you can only get if you have a registered developer account and an application created for twitter.

Usage: twit2blog [opts]

Options:
  -u, --user   The screen name of the twitter user. E.g. If your twitter is https://twitter.com/foobar, then `foobar`.
  -t, --thread The ID of the last tweet in your thread. E.g. 12345.

For more information read the Github readme:
  https://github.com/weskerfoot/Twit2Blog#readme

Example: twit2blog -t:1234 -u:alice | pandoc --from=markdown --to=html > thread.html

You must provide the ID of the last tweet from the thread you want rendered. E.g. https://twitter.com/weskerfoot/status/1199466868953759750 is the last tweet in one of my threads. The reason for this is that the twitter API does not provide an easy way to search for replies to a given tweet.

You can see the output generated from it here