ttytter - Command-Line Twitter Client
||openSUSE Leap 42.2
||openSUSE Network Utilities all
Noooo, not another Twitter client! Yes, another Twitter client. The difference
here is that you're dealing with a multi-functional, fully 100% text, Perl
command line client.
* In interactive mode, it is a fully interactive client with asynchronous
background updates and commands. Use it over telnet, ssh or even a dummy
terminal. Supports ANSI colour, UTF-8, hashtags and Twitter Search!
* Works within your favourite environment: modify prompt and input methods for
many popular window and session managers, or use a compatible readline
library. Or don't: basic editing and screen management features built-in.
* From the command line, use it to update your Twitter in shell scripts, from
cron, and so on.
* Notification support with Growl and libnotify (and extendable to others via
* Security: Supports Twitter OAuth and HTTP Basic Authentication, and SSL where
supported by your user agent.
* Supports Twitter-alike APIs such as StatusNet and Identi.ca.
* Supports standard timelines and automatically fetches direct messages, and
optionally replies/mentions, and runs queries against the Search API and
incorporates them into your timeline as well.
* Write and use your own custom extensions!
* Run detached in -daemon mode, and make your own Twitter bot!
- Add the openSUSE Network Utilities repository:
# zypper addrepo http://ftp.gwdg.de/pub/opensuse/repositories/network:/utilities/openSUSE_Leap_42.2/ opensuse-network-utilities
- Install ttytter rpm package:
# zypper install ttytter
2015-07-06 - email@example.com
- build for openSUSE version 2.1.0:
- Full compliance with Twitter API 1.1, including TOS limitations and rate limits.
- Commands that accept menu codes can now also accept tweet or DM IDs, perfect for all you command-line jockeys.
- New /replyall command (thanks @FunnelFiasco).
- New /del command.
- User filtering (with new -filter* options).
- Better description of the full range of streaming events (thanks @RealIvanSanchez).
- /push now works with non-Boolean options, simply pushing them to the stack (it still sets Booleans to true when pushed).
- Geolocation now looks at and processes place ID, country code, name and place type, and tweets with a place ID will also be considered to have geolocation information (thanks @RealIvanSanchez).
2010-09-15 - firstname.lastname@example.org
- initial version 1.1.05