Russell (zimzat) wrote,
Russell
zimzat

  • Mood:
  • Music:

Bot Procedures

From: Zimzat
To: LiveJournal
Sent: Tuesday, June 22, 2004 1:03 AM

I'm considering making a meme which will look into a person's friend list
then download the interest list of all their friends. It'll then compare all
the lists and analyze who has what in common. I actually have the code for
this completed already and tried it out on a couple of people.

Another meme I got the idea for from that is a "unique or common" one where
it only looks at the one person's friend list and analyzes how many
interests they have that a lot of people have, or few people have.

Anyway, the reason I'm emailing you is because I'd like to know what kind of
programming procedures there are for this kind of thing. For example, how
long I should hold things cached before casually refreshing them or doing a
forceed refresh, or how to send identifier tags to the server (the
well-formed user agent thing) from within a PHP enviroment.

I would just like to make sure I'm not screwing over the server and, should
I decide to go live with one or more of these memes, that I'll have it as
optimized as possible.

Right now I have the first meme set to allow a force refresh no sooner than
an hour after it's last update, and it will automatically grab new
information after 24 hours.

Thank you in advance.

Sincerely,
Russell



From: Brad Fitzpatrick
To: Zimzat
Sent: Tuesday, June 22, 2004 1:16 AM


Cache for 24 hours and you should be good.

Just make sure your useragent string has your meme's URL and your email in
it, in case we need to contact you about a better way to do things.

I don't know PHP enough to tell you how to do that, but the API docs in
PHP should say.

- Brad

http://www.livejournal.com/support/see_request.bml?id=299433
Subscribe
  • Post a new comment

    Error

    default userpic

    Your reply will be screened

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.
  • 3 comments