Telegram Tumblr Bot

Tumblr for telegram

I have recently decided to start my development blogging. Not just the typical tutorial posts and promotional posts that I have been writing, but more of the everyday kind of development postings.

I have picked tumblr, as it is fairly mature (stable services), and the casual nature of tumblr makes it easier for me to write freely. It takes off the stress of having to produce good, easy-to-read pieces. It will just be a place where I post whatever comes along.

However, I do not want to have to download the tumblr app just to do my random journal entries. Most tumblr app is built more for viewing tumblr stream, which I have little interest as of now. I have tried other apps, but most of them follow the same nature of using tumblr as a information stream.

Convenient postings

I have tried email posting, but because the emails are sent out as text, it screws up the formating of the posts (fixed newlines). Hence I came up with the idea of sending the posts to telegram and then let telegram do all the posting, some like a “email posting 2.0”.

Tumblr for telegram

I have invested quite abit of time on the design of the app workflow. Learning from the previous telegram app, which was quite difficult to use (according to feedback). I have added useful guides along the way to help people more easily get started.

Try it out at @tumblr_pbot


Dissembling Kairui Hair Clipper

I have a old hair clipper lying around. And I have some free time. Hence, dissembling…

This is a fairly simple machine. There isn’t much complex mechanims in there. But still there are some pretty cool working to learn from.

Later plugin – Export

Later is a issue tracker that I have been working on for some time now. This time round, I am creating a plugin to export all the issue data.

For the plugin, I have decided to export it as JSON, as its would make easy import for other plugins that I might write in the future. There were 2 design options when exporting the data — design based on relational database, or flatfile style.

Flatfile style will be easier to read of course, but I went more on the databased design in the end because this data export was not really meant for reading.

Export plugin

Later export plugin

Later is an issue tracker that I have been working on. This time, I created a plugin that exports the data as a JSON file. The design of the output takes after a relational database design.

Design of JSON data

            "rev": "rev1",
            "reported":["guid1", "guid2"],
            "confiremd":["guid3", "guid4"],
            "closed:["guid5", "guid6"]

Export plugin for later