3 ms·
Thanks for hijacking my thread! ;) Seriously, though, how would your library work for twitter? It seems that the encoding process creates texts much, much lar
by dpapathanasiou 13y ago
Thanks for hijacking my thread! ;)
Seriously, though, how would your library work for twitter?
It seems that the encoding process creates texts much, much larger than the original message.
- rw 13y agoTweetFS uses the SeqTweet library, which takes care of sequencing the tweets for you. Specifically, see the _list_to_twitter method: https://github.com/workmajj/seqtweet/blob/master/seqtweet/seqtweet.py#L36 https://github.com/workmajj/seqtweet/blob/master/seqtweet/se... One of the use cases of TweetFS is to use Twitter as a 'dead drop'. You'll generate a lot of tweets by doing that, but there's no harm done. I don't think I hijacked your thread. The other comments also discuss textual steganography.
- dpapathanasiou 13y agoThanks I'll look more into how TweetFS works. I was just kidding about the hijiacking comment; don't people know how to interpret emoticons anymore? :D
- epaga 13y agoI think the problem is that unlike ":)", too often people use passive-aggressive ";)"s, not meaning them in the friendly way they were originally intended but with a slightly bitter aftertaste. But this is getting a bit off-topic I suppose... :)