[01:38] [tinyback] soult pushed 1 new commit to master: https://github.com/soult/tinyback/commit/48a7ce565dbdb7267ab554a7e386156ad06a5f97 [01:38] tinyback/master 48a7ce5 David Triendl: Set default sleep time to 300 seconds / 5 minutes [02:17] post.ly: Game on [02:41] [tinyback] soult pushed 2 new commits to master: https://github.com/soult/tinyback/compare/48a7ce565dbd...1b014bf6ba54 [02:41] tinyback/master 1b014bf David Triendl: Bump version to 2.6 [02:41] tinyback/master 7322687 David Triendl: services: Add "Postly" [03:06] everyone please do a git pull if you are not using the warrior [22:20] I always figured those "official" shorteners like post.ly or youtu.be are the least important to back up because they will exist as long as the company that uses them exists [22:21] I figure those are the 'cheapest ones' to get, since they got a lot of infra - and a lot of user data. So it's basically a pre-fail crawl :) [22:28] How do you usually go about finding out the charset of a shortener? [22:29] Since post.ly was a shortener mostly used to send posterous posts to twitter, I simply did a twitter search for post.ly [22:29] ah [22:29] Then you can easily discover what characters are allowed and also if it is sequential or not [22:30] And even what the order of the sequence is (e.g. posterous has uppercase letters before lowercase letters) [22:38] That's totally not dumb [22:40] It works well in this case because post.ly only lets you shorten an url if you log in via twitter and then automatically posts the shortened url [22:41] I'm a bit interested in adding wp.me actually. Not that I think they'll go under any time soon, just.. Interested. [22:41] It seems like all content created (each post) gets a shortening on their shortener [22:42] Go for it [22:44] will do [22:52] [tinyback] ersi pushed 1 new commit to master: https://github.com/soult/tinyback/commit/f44a063284c0e513560f350eb5848540c56cefa0 [22:52] tinyback/master f44a063 Erik SimmesgÃ¥rd: Adding Wp.me service [22:54] That was fast [22:55] indeed :p [22:56] [tinyback] soult pushed 1 new commit to master: https://github.com/soult/tinyback/commit/b79c41e39764cecd21c461e0804928d10e5d523a [22:56] tinyback/master b79c41e David Triendl: services: typofix [22:56] I havn't tested it though, and it's just a "very basic" addition based on what I've seen so far [22:56] oops :) [22:56] If you push to master, you have to always be careful because the warriors will update within seconds [22:56] If you break it, then all warriors running the urlteam tasks break too [22:57] Well, the warrior won't break, but it won't do any more urlteam tasks [22:57] * ersi nods [22:58] I'll run some wp.me tasks on a test machine to see what will happen [22:59] I usually do things in a feature branch and do a pull request. I think I'll continue doing it like that :-) [23:02] btw, if you look at the wp.me urls [23:02] they are always ABCDEF-GHIJ [23:02] The first 6 characters are some kind of id for the blog [23:02] And the remaining 4 characters are for a specific post [23:03] Yeah, I did however assume that was because of how high the 'numbers' were for the ones I've seen recently [23:04] but that makes sense - since code "123" with delimiters like -_#!"#% have the same location: [23:05] So wp.me/s1a leads to a blog [23:06] * ersi nods [23:06] wp.me/ps1a-XXX leads to a specific blog post [23:06] not too bad layout [23:08] And the XXX is sequential [23:09] First blog post = 1, second = 2, 10th = a, 16th = g etc. [23:12] This will make it easy to scrape [23:13] That's *always* good news :-) [23:13] I think the blog ids might also be sequential [23:15] would make sense, less hassle to organize for 'em