#urlteam 2013-02-16,Sat

↑back Search

Time Nickname Message
01:38 πŸ”— GitHub77 [tinyback] soult pushed 1 new commit to master: https://github.com/soult/tinyback/commit/48a7ce565dbdb7267ab554a7e386156ad06a5f97
01:38 πŸ”— GitHub77 tinyback/master 48a7ce5 David Triendl: Set default sleep time to 300 seconds / 5 minutes
02:17 πŸ”— soultcer post.ly: Game on
02:41 πŸ”— GitHub157 [tinyback] soult pushed 2 new commits to master: https://github.com/soult/tinyback/compare/48a7ce565dbd...1b014bf6ba54
02:41 πŸ”— GitHub157 tinyback/master 1b014bf David Triendl: Bump version to 2.6
02:41 πŸ”— GitHub157 tinyback/master 7322687 David Triendl: services: Add "Postly"
03:06 πŸ”— soultcer everyone please do a git pull if you are not using the warrior
22:20 πŸ”— soultcer 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 πŸ”— ersi 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 πŸ”— ersi How do you usually go about finding out the charset of a shortener?
22:29 πŸ”— soultcer 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 πŸ”— ersi ah
22:29 πŸ”— soultcer Then you can easily discover what characters are allowed and also if it is sequential or not
22:30 πŸ”— soultcer And even what the order of the sequence is (e.g. posterous has uppercase letters before lowercase letters)
22:38 πŸ”— ersi That's totally not dumb
22:40 πŸ”— soultcer 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 πŸ”— ersi 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 πŸ”— ersi It seems like all content created (each post) gets a shortening on their shortener
22:42 πŸ”— soultcer Go for it
22:44 πŸ”— ersi will do
22:52 πŸ”— GitHub50 [tinyback] ersi pushed 1 new commit to master: https://github.com/soult/tinyback/commit/f44a063284c0e513560f350eb5848540c56cefa0
22:52 πŸ”— GitHub50 tinyback/master f44a063 Erik SimmesgΓƒΒ₯rd: Adding Wp.me service
22:54 πŸ”— soultcer That was fast
22:55 πŸ”— ersi indeed :p
22:56 πŸ”— GitHub103 [tinyback] soult pushed 1 new commit to master: https://github.com/soult/tinyback/commit/b79c41e39764cecd21c461e0804928d10e5d523a
22:56 πŸ”— GitHub103 tinyback/master b79c41e David Triendl: services: typofix
22:56 πŸ”— ersi I havn't tested it though, and it's just a "very basic" addition based on what I've seen so far
22:56 πŸ”— ersi oops :)
22:56 πŸ”— soultcer If you push to master, you have to always be careful because the warriors will update within seconds
22:56 πŸ”— soultcer If you break it, then all warriors running the urlteam tasks break too
22:57 πŸ”— soultcer Well, the warrior won't break, but it won't do any more urlteam tasks
22:57 πŸ”— * ersi nods
22:58 πŸ”— soultcer I'll run some wp.me tasks on a test machine to see what will happen
22:59 πŸ”— ersi I usually do things in a feature branch and do a pull request. I think I'll continue doing it like that :-)
23:02 πŸ”— soultcer btw, if you look at the wp.me urls
23:02 πŸ”— soultcer they are always ABCDEF-GHIJ
23:02 πŸ”— soultcer The first 6 characters are some kind of id for the blog
23:02 πŸ”— soultcer And the remaining 4 characters are for a specific post
23:03 πŸ”— ersi Yeah, I did however assume that was because of how high the 'numbers' were for the ones I've seen recently
23:04 πŸ”— ersi but that makes sense - since code "123" with delimiters like -_#!"#% have the same location:
23:05 πŸ”— soultcer So wp.me/s1a leads to a blog
23:06 πŸ”— * ersi nods
23:06 πŸ”— soultcer wp.me/ps1a-XXX leads to a specific blog post
23:06 πŸ”— ersi not too bad layout
23:08 πŸ”— soultcer And the XXX is sequential
23:09 πŸ”— soultcer First blog post = 1, second = 2, 10th = a, 16th = g etc.
23:12 πŸ”— soultcer This will make it easy to scrape
23:13 πŸ”— ersi That's *always* good news :-)
23:13 πŸ”— soultcer I think the blog ids might also be sequential
23:15 πŸ”— ersi would make sense, less hassle to organize for 'em

irclogger-viewer