speck - a micro.blog CLI
speck is a command line tool for managing a micro.blog account.
You can install
in two easy steps
(given that you have Homebrew installed):
- Add my tap:
brew tap fiskeben/homebrew-tap
brew install speck
Don't forget to read the paragraph about configuration below.
Building and installing manually
The tool is written in Go and currently requires you to have Go installed in order to build the binary.
make build will build the binary and put it in this folder.
make install to install
speck. This will create an executable
speck and add it to your Go bin folder.
Add the folder to your
$PATH if you want.
You need a token from micro.blog to use the tool.
Create a new token here
and put it in a file called
along with your username, like this:
--- username: your-micro-blog-username token: your-token
Save the file to either your home directory or current working directory.
Usage and features
speck is very limited.
It can retrieve your timeline and create new posts.
speck without any parameters to get your timeline.
Pipe the output to
less to better read it.
speck post to create a new post.
This will open your
vi if it's not set)
and you can write your post there. When you save and exit the editor
the post will be created on your micro blog.
If what you wrote is longer than 280 characters, your editor will repoen and you need to make it shorter.
It's also possible to post something you already have on file,
speck post <path/to/file>
TODO and upcoming features
These are some of the features I want to add soon:
- Pass a file to
speck postso that you can write posts independently from posting.
- Post display:
- Parsing/stripping HTML
- Limiting output width to avoid super long lines of text
- URL to photos.
- Adding help text to the editor (like
- Save the post locally as well as posting it to micro.blog.
- Multiple accounts.
- Setup command that writes the
- Implement more of the features from the API such as
(un)following, reading users' timelines etc.
- Open user's micro.blog profile/timeline in a browser.
- Don't be an "app" with lots of friendly, formatted output. Output should be possible to pipe to another program.
stdinas source for post text.
- Some sort of CI/CD and
Homebrew cask for easy installation.