Re: Twitter image encoding challenge: URL fix
- From: Brian Campbell <unlambda@xxxxxxxxx>
- Date: Wed, 27 May 2009 08:56:18 -0700 (PDT)
On May 27, 9:13 am, "Duplic" <dub...@xxxxxxxxxxxxx> wrote:
There's some horrible character restrictions on that messy page, and 4 days
is not really enough unless people can put full time work into it perhaps..
And how do you quantify the image 'closeness' to the original? - Stand back
and squint?
Yeah, I didn't think of posting it here until about halfway through
the challenge; sorry about that. It was 9 days originally. I think
that 4 days isn't too unreasonable for a little toy problem like this;
the ICFP contest is a 3 day long contest with a challenge that is
generally much larger in scope (though it is usually solved by a team
with a bit more advance organization, not a single person).
The messiness is because I've been tweaking the rules and guidelines
slightly as issues come up, and wanted to make it clear what had
changed to people who have seen earlier versions. The only real
restriction is that it be compressed into 140 Unicode characters; the
issues is that then I needed to be more specific about defining a
valid Unicode character. If you think it'll help, I will try and
reorganize the rules to make them more readable, though it may be a
bit late for that at this point.
Basically, this was a very off the cuff kind of thing, that I set up
because I saw someone do something neat, and a lot of people offering
suggestions for how it could be done better, so I wanted to see if
they could put their money where their mouth is and implement it.
After a few days of getting a lot of interest from people who want to
see the results, but a fairly low number of submissions, I decided to
see if I could find anywhere where there would be people with more
experience in compression who might have some good ideas, so I posted
this here and on comp.compression. This is entirely just for fun, so I
apologize if it seems a bit hurried, I just wanted to get it out there
and see what people can come up with.
Also, perhaps I should explain how StackOverflow works. It's a
question and answer forum, with voting to help separate the wheat from
the chaff. Anyone with an account and more than 15 reputation can vote
answers (and questions) up, to indicate what they like. The person who
submitted a question can also choose an accepted answer, which is what
they deem the best answer for the problem they posted. The submitter
can also choose to offer a bounty, which I have done, to give extra
incentive for people to answer their question. So, there are really
two ways you're being evaluated; by votes from the community, and by
my judgement of the best answer. I gave a basic rubric of
approximately how I'll be ranking answers; I will make a subjective,
aesthetic judgement of what I feel makes the most accurate and best
looking image (so yes, "stand back and squint", plus "does it do
anything aesthetically interesting"), and I will also give
consideration to clever algorithms, neat encoding schemes, and the
like. The community is welcome to vote however they feel. And even if
you miss the bounty deadline, you can still submit answers, and may
get voted by the community higher than the accepted solution if your
solution is good enough.
Anyhow, this was intended to be a light, fun little challenge. It
turned out to be a bit larger in scope than I expected, but I hope
people can still have fun with it. Let me know if you have any more
questions.
-- Brian
.
- References:
- Twitter image encoding challenge
- From: Brian Campbell
- Re: Twitter image encoding challenge: URL fix
- From: Jerry Avins
- Re: Twitter image encoding challenge: URL fix
- From: Duplic
- Twitter image encoding challenge
- Prev by Date: Affliction Mens T-shirts & Affliction Tee
- Next by Date: Re: DTMF decoding
- Previous by thread: Re: Twitter image encoding challenge: URL fix
- Next by thread: Re: Twitter image encoding challenge
- Index(es):
Relevant Pages
|
