catfish.man at gmail.com
Mon Jan 5 22:37:31 UTC 2009
On Jan 5, 2009, at 8:43 AM, Evan Schoenberg wrote:
> Facebook + Safari is nasty, because the shared cookie storage leads
> us to continually be logged out and for Safari's Facebook to be, as
> I spent yesterday evening and this morning working on "AICookieJar",
> an attempt at manually managing cookies independent of the
> systemwide storage.
> The success: I can make a WebKit window pass a simple cookie test as
> in http://www.tempesttech.com/cookies/cookietest1.asp while using
> our own cookie storage.
> The failure: Facebook doesn't work with it. I don't understand why,
> as at this point I am doing, at our level, exactly what the working
> Pidgin Facebook plugin does as far as I can tell. I think it's
> possible that -[NSMutableURLRequest setHTTPShouldHandleCookies:NO]
> doesn't just disable the "default cookie handling" as the
> documentation says but actively forces it to strip out outgoing
> one solution would be to just switch to the Pidgin Facebook plugin,
> since it implements its own HTTP stack and gets us completely away
> from whatever weird internals are messing this up. It' s a pretty
> easy switch, and as far as I know it's feature equivalent. It's sad
> to me to see my rather elegant (if I say so myself) Facebook
> implementation get trashed...but that's no reason not to do it.
Random possibility would be to check that we aren't somehow disabling
cookies for Adium via a preference we set on one of our webviews.
Other than that, I like the idea of less code to compile/maintain, and
fixing bugs "for free", but I reaaaaaally wish facebook would get off
their butts and get that xmpp server working so we could drop the
More information about the Adium-devl