Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #32810 > unrolled thread

Re: Coordination between developers in the Python project

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Coordination between developers in the Python project Chris Angelico <rosuav@gmail.com> - 2012-11-06 19:59 +1100

#32810 — Re: Coordination between developers in the Python project

On Tue, Nov 6, 2012 at 7:49 PM, Ian Kelly <ian.g.kelly@gmail.com> wrote:
> On Mon, Nov 5, 2012 at 3:01 PM, Chris Angelico <rosuav@gmail.com> wrote:
>> By "URL unshortening service" you mean a simple HTTP request to
>> bit.ly:80, right? :) Though I admit there aren't many easy and
>> convenient ways to do that without immediately following the 301
>> redirect.
>
> That's one way to do it.  Although I find it a bit easier to just use
> something like unshorten.com, which is the first Google hit for "url
> unshortener".  Assuming that you trust that site to not be hosting
> malware itself. :-)

A few years ago, I found myself bugged by URLs getting broken across
multiple lines when shared across a MUD communication channel
(80-character lines, with a header on each line, so there'd be between
65 and 75 usable characters per line), so I wrote a feature into my
MUD client that would auto-shorten long URLs by passing them to
tinyurl.com, and also "render" them on the other side - if it started
http://tinyurl.com/ then the client would, on request, query tinyurl
and snag the returned URL back into the display.

For some reason it never occurred to me to do it any way other than
direct socket operations in C.

ChrisA

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web