]> git.madduck.net Git - code/twitter-archiver.git/blob - README.md

madduck's git repository

Every one of the projects in this repository is available at the canonical URL git://git.madduck.net/madduck/pub/<projectpath> — see each project's metadata for the exact URL.

All patches and comments are welcome. Please squash your changes to logical commits before using git-format-patch and git-send-email to patches@git.madduck.net. If you'd read over the Git project's submission guidelines and adhered to them, I'd be especially grateful.

SSH access, as well as push access can be individually arranged.

If you use my repositories frequently, consider adding the following snippet to ~/.gitconfig and using the third clone URL listed for each project:

[url "git://git.madduck.net/madduck/"]
  insteadOf = madduck:

README updates
[code/twitter-archiver.git] / README.md
1 # Archiving Twitter
2
3 These are a set of scripts allowing you to keep a copy of your Twitter life:
4
5 1. Dumping followers, optionally sending changes to you by e-mail at regular
6    intervals (using cron).
7
8 2. Archiving all your tweets as they come in, both their raw data, as well as
9    an HTML dump the way Twitter would dump it at the time.
10
11 All of this is very hackish, but if it's of any use to you, then great!
12
13 ## Getting started
14
15 I think it's just running the scripts. For instance, I have the following
16 entries in crontab:
17
18 ```
19 */6 * * * * $HOME/twitter/fetch_tweets.sh 2>/dev/null
20 */15 * * * * $HOME/twitter/track_followers.sh >/dev/null
21 2 7 * * * $HOME/twitter/report_followers.sh
22 ```
23
24 Warning: I have not tested this as a means to extract past tweets. You might
25 well hit limits of Twitter. However, Twitter does let you export your entire
26 history to a Zip file. I've done that, and so should you. Then please write
27 a translator to squeeze all those data into the archive created with my
28 scripts, and submit a patch.
29
30 ## Patches
31
32 Speaking of: patches welcome, please send them to madduck@madduck.net using
33 git-format-patch and git-send-email.
34
35 ## Wishlist
36
37 0. Setup instructions
38 1. Better handling of target directories, i.e. don't make them subdirectories
39 2. Exporting parameters (such as email address) to configuration
40 3. Dumping favourites/starred tweets
41 4. Dumping bookmarks
42
43 ## Copyright
44
45 Copyright © 2017–2019 by martin f. krafft <madduck@madduck.net>
46 and released under the terms of the Artistic Licence 2.0.
47
48 If you need it under another licence, let me know.