Updated README.md to reflect the state of the project.

Corrects the path given in README.md.

.gitignore

@@ -9,3 +9,8 @@ data/
 src/main/main.iml
 cache4.*
 src/test/test.iml
+dev/
+todo
+deploy.secret.sh
+release_notes.txt
+out

.travis.yml

@@ -0,0 +1,13 @@
+language: java
+
+branches:
+  only:
+    - master
+before_cache:
+  - rm -f  $HOME/.gradle/caches/modules-2/modules-2.lock
+  - rm -fr $HOME/.gradle/caches/*/plugin-resolution/
+
+cache:
+  directories:
+    - $HOME/.gradle/caches/
+    - $HOME/.gradle/wrapper/

DEPLOY.md

@@ -0,0 +1,12 @@
+# Deploying a new version
+
+* Update the version in the Dockerfile to the coming version.
+* Commit the new Dockerfile.
+* Merge into stable: `git checkout stable && git merge --no-ff master`
+* Create a new tag for the new version: `git tag -a <version>`.
+* Push everything to github: `git push --all && git push --tags`.
+* Build it: `gradle build`.
+* Create a new release on github for this version. 'Release title' has to be just the version string. Attach the newly built `telegram-backup.jar`.
+* Build the docker image: `docker build -t fabianonline/telegram_backup:<version> -t fabianonline/telegram_backup:latest - < DOCKERFILE`.
+* Push the docker image: `docker push fabianonline/telegram_backup`.
+* Post a message into the telegram_backup users group.

Dockerfile

@@ -0,0 +1,15 @@
+FROM openjdk:8
+
+ENV JAR_VERSION 1.1.3
+ENV JAR_DOWNLOAD_URL https://github.com/fabianonline/telegram_backup/releases/download/${JAR_VERSION}/telegram_backup.jar
+
+RUN apt-get update -y && \
+	apt-get install --no-install-recommends -y curl && \
+    curl -L "https://github.com/Yelp/dumb-init/releases/download/v1.1.3/dumb-init_1.1.3_amd64" -o /bin/dumb-init && \
+    curl -L $JAR_DOWNLOAD_URL -o telegram_backup.jar && mkdir /data/ && \
+    chmod +x /bin/dumb-init && \
+    apt-get remove -y curl && \
+    apt-get autoremove -y && \
+    rm -rf /var/lib/apt/lists/*
+
+ENTRYPOINT ["/bin/dumb-init", "--", "java", "-jar", "telegram_backup.jar", "--target", "/data/"]

README.md

@@ -2,6 +2,16 @@
 Copyright 2016 Fabian Schlenz  
 Licensed under GPLv3
 
+## State of this project
+The tool is working, but not really as intended: Media files in most cases can't be downloaded, message downloads are hit with 30 second delays after every 200 messages. Some users reported getting banned by Telegram without reason after using this tool (with many users not getting banned at the same time, so this could theoretically just be a coincidence).
+
+At the same time, the official Telegram client has an official way to download one's data, which is a) officially supported and b) much, much, much faster than this tool.
+
+Fixing this tool to at least get it to work again as planned would require more or less a complete rewrite of this code. Since I'm quite happy with the possibilities given by the official clients and don't have enough free time to spare to continue developing this project, I've decided to officially archive this tool. This is not an easy step for me, because this was my most used project and quite a lot of people wrote me nice messages and thanked me. But just keeping the user's hopes up for an update without really being able to do something doesn't seem fair. So...
+
+So long, and thanks for all the fish. ;-) \
+Fabian
+
 ## Description
 This is a small Java app that allows you to download all your history from
 Telegram's servers and keep a local copy of them.
@@ -18,16 +28,13 @@ You can find the whole app packed into one fat jar file under
   only.
 * Incremental backups - if you run the tool at a later time, it will only
   download new messages / media.
-* You will be able to use an HTML exporter to create static HTML files
-  containing your chats. This feature is still in the works.
 
 ## Limitations
-This tool relies on Telegram's API. Apparently they don't like people who
-download lots of media files, so this app gets blocked after about 2000
-downloaded media files. This is nothing bad; the app detects this and waits
-the necessary amount of time as dictated by Telegram. Since this delay can
-be quite large (I've seen 50 minutes), downloading lots and lots of media
-can take some time.
+This tool relies on Telegram's API. They started rate limiting the calls
+made by this tool some time ago. As of February 2017, downloading messages
+is limited to 400 messages every 30 seconds, resulting in 48,000 messages
+per hour. Media download is not throttled right now, so it should be a lot
+quicker.
 
 But since this tool is designed to be able to continue it's work at any
 time, you can just abort the download and continue it later - that way,
@@ -44,6 +51,15 @@ Basically, you have to call it with `--login` first to login to your telegram ac
 call it again with `--account <phone>` to use this account and download all
 it's history. If you have just one account, you can omit this parameter.
 
+Use `--with-supergroups` and / or `--with-channels` to also download all
+messages from the supergroups / channels you have joined that have been
+active in the last time.
+
+After making a backup, call it again with `--export html` to create a few
+more-or-less nice to look at HTML files containing all your chats. They will
+be created in the subfolder `files` of your backup. You can just open the
+file index.html in your browser to look at the files.
+
 ## Donations
 I've put quite some time into this tool. If you want to donate a small
 amount, you can send it via Bitcoin to *1CofYzS88iEngxMu4NqQeohWDBUHv9CNDJ* or via PayPal to
@@ -55,6 +71,11 @@ link](https://www.amazon.de/ref=as_li_ss_tl?ie=UTF8&linkCode=ll2&tag=telegrambac
 pay any more, but I will get a few percent of your purchase's worth from
 amazon.
 
+## Contact
+If you have questions or comments or need help, you can join the
+[telegram_backup Development group](https://t.me/joinchat/CXFirQenTSeGWhxnikd8tg)
+at Telegram.
+
 ## Frequently asked questions
 ### Why do I see error messages?
 The library I'm using to access Telegram has some small bugs. One of those
@@ -74,7 +95,7 @@ this will be detected at the next run of this program and then tried again.
 The files are being saved in your User directory in a folder named
 `telegram_backup`. Under windows, this would typically be under
 `C:\Users\<username>\telegram_backup`. Linux users should look unter
-`/home/<username>/telegram_backup`.
+`/home/<username>/.telegram_backup`.
 
 You can change this directory by supplying `--target <dir>` when calling
 Telegram_Backup.
@@ -90,6 +111,15 @@ containing all your messages and other data. The folder `files` contains all
 media files, named after the ID of the message they belong to. Last but not
 least the folder `export` contains exported data.
 
+### What are EmptyMessages? Why are there so many messages?
+If you are a member of a normal group (non-supergroup), all messages sent to
+that group are being copied to your personal messages at Telegram's servers.
+
+If you later leave this group, those messages are being deleted at Telegram,
+but since all messages are continuously numbered, you can't simply delete
+them because that would leave a hole in your message numbers. So these
+messages are instead replaced by EmptyMessages - those things contain zero
+information, they are just saying "here was a message but it was deleted".
 
 ## Attribution
 This tool uses libraries from other developers which are covered by other licenses,

build.gradle

@@ -1,24 +1,46 @@
 apply plugin: 'java'
 apply plugin: 'application'
 
-mainClassName= 'de.fabianonline.telegram_backup.CommandLineRunner'
+mainClassName= 'de.fabianonline.telegram_backup.CommandLineRunnerKt'
 
 repositories {
 	mavenCentral()
 	maven { 
 		url "https://jitpack.io"
 	}
+	jcenter()
 }
 
+buildscript {
+	ext.kotlin_version = '1.2.0'
+	
+	repositories {
+		mavenCentral()
+	}
+	
+	dependencies {
+		classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
+	}
+}
+
+apply plugin: 'kotlin'
+
+compileKotlin {
+	kotlinOptions.apiVersion = "1.0"
+}
+		
+
 dependencies {
 	compile('com.github.badoualy:kotlogram:666a81ef9d6707f117a3fecc2d21c91d51c7d075') {
 		exclude module: 'slf4j-simple'
 	}
-	compile 'org.xerial:sqlite-jdbc:3.8.11.2'
-	compile 'com.github.spullara.mustache.java:compiler:0.8.18'
+	compile 'org.xerial:sqlite-jdbc:3.16.1'
+	compile 'com.github.spullara.mustache.java:compiler:0.9.5'
 	compile 'org.slf4j:slf4j-api:1.7.21'
 	compile 'ch.qos.logback:logback-classic:1.1.7'
-	compile 'com.google.code.gson:gson:2.5'
+	compile 'com.google.code.gson:gson:2.8.0'
+	compile 'com.github.salomonbrys.kotson:kotson:2.5.0'
+	compile 'com.github.kittinunf.fuel:fuel:1.12.0'
 	
 	testCompile 'junit:junit:4.12'
 }
@@ -33,7 +55,9 @@ def getVersionName= { ->
 		commandLine 'git', 'describe', '--tags', '--dirty'
 		standardOutput = stdout
 	}
-	return stdout.toString().trim()
+	def version = stdout.toString().trim()
+	logger.lifecycle("Version $version")
+	return version
 }
 
 ant.propertyfile(file: "$project.rootDir/build/resources/main/build.properties") {