When I try AOL Keyword Mefi, nothing happens.

January 10, 2002 6:34 AM

When I try AOL Keyword Mefi, nothing happens. (more inside).


posted by ParisParamus to Bugs at 6:34 AM (13 comments total)

Actually, that was just an attention-grabbing intro having nothing to do with my question, which asks why is it that often, when I go to Metafilter, the "New Comments" feature indicates that all posts in a thread or new, and stays that way. And then, suddenly, without explanation, after many minutes have gone by, the "new" number resumes working.
posted by ParisParamus at 6:35 AM on January 10, 2002

...wishing for a killfile right about now...
posted by NortonDC at 6:43 AM on January 10, 2002

When I try AOL Keyword 'Stupid FFP', I am directed to this page
posted by chrisroberts at 7:34 AM on January 10, 2002

* hears twangy music in the distance *
-- starts clapping and stomping foot --

weellllll she'll be comin' round the mountian when she comes
she'll be comin' round the mountain when she comes
she'll be comin round the mountain
she'll be comin round the mountain
she'll be comin round the mountain when she coommmeesss

-- stops clapping and stomping foot --
* music fades *

*bow*
posted by chrisroberts at 7:51 AM on January 10, 2002

*pushes bales of hay out of sight, thus returning thread to original topic*

Despite poor delivery, Paris' question has merit: In MeTa, the new comments number resets with each page reload. In MeFi, the new comments number is sticky as all get out. Is there a reason for this?
posted by iceberg273 at 8:06 AM on January 10, 2002

FWIW, I've had this problem, but only when viewing with MSIE. If I'm using NS6.0, the new message count resets with each page load.
posted by elfgirl at 9:46 AM on January 10, 2002

FWIW, I've had this problem, but only when viewing with MSIE. If I'm using NS6.0, the new message count resets with each page load.

Well, I'm using IE5/Win2K. So that's consistent.
posted by iceberg273 at 9:52 AM on January 10, 2002

It may have to do with the way requests are sent and what info is cached. I imagine running a new request for info each time a page is loaded for MetaTalk is much less detrimental to the server than requiring MetaFilter to refresh upon every load.
posted by Hankins at 10:00 AM on January 10, 2002

There's something different going on with the session management in MetaTalk vs. MetaFilter and I have to find the bug and fix it. It would probably take an afternoon to do, since the code is pretty complex.

But, I'm working on several freelance projects (that take up a lot of my time and don't pay all that well) and writing a chapter for an upcoming book (that is due at the end of the month), and I'm really busy, so please bear with the new-link-indicators-that-don't-work-too-well-on-metatalk for now.
posted by mathowie (staff) at 10:21 AM on January 10, 2002

...wishing for a killfile right about now...

Hey. Humor which induces cringing, especially without being gross, is an art. I am very proud of that intro. Moreover, as a still practicing attorney, Mefi is one of the few outlets for creativity I have, so please be compassionate.

posted by ParisParamus at 10:24 AM on January 10, 2002

Yes, clearly lawyers do need more opportunities to be cringe inducing.
posted by NortonDC at 10:40 AM on January 10, 2002

Whatever the problem is, it also manifests itself in Metatalk. At least for me.

By the way, AOL Keyword Metatalk does work, so I really don't think my intro was that outrageous.
posted by ParisParamus at 1:51 PM on January 10, 2002

for my money, it's one of the best MeTa FPPs ever.
posted by rebeccablood at 9:14 PM on January 10, 2002