in reply to A new chatterbox flavour

It has a weird quirk. It logs you in cloaked, always, even if the browser was already logged in as a normal user before. So, if you're using http://www.perlmonks.org to access this site, and then you log in with this Chatterbox client (either you log in, or you can't use it to speak), your continued visit will now happen under a cloak. You can see that marked by a "#" symbol next to your login name in the top navigation section of any normal node page.

The following symptoms will now happen:

All not too desirable, and I'm quite sure Aristotle will find a permanent solution in a short time — checking at startup if a permanent cookie was set, and if so, just leave it, that would be a start. But, for now, the best advice I can give you is: if you wish to keep using this chatterbox client, and don't want your normal visits here to be cloaked, use a different root URL for your normal visit, and for this client. In short: don't visit via http://www.perlmonks.org. Use, for example, http://perlmonks.org.

Replies are listed 'Best First'.
Re^2: A new chatterbox flavour
by Aristotle (Chancellor) on Jan 14, 2005 at 07:08 UTC

    Logging in cloaked was by design, but I suppose it's counterproductive for people who just want to use the client, rather than hack on it. Since so many people complained about that I've commented out the parameter which tells PM to cloak the login, so download the code again and you should be good to go.

    I cannot use an existing PM cookie; it is a security feature of JS to prevent you from reading the cookies set by other sites. The plan was and is to eventually have a copy of this hosted on PM, so a separate login won't be necessary. I just need the tuits to implement the bits that will be difficult to do in JS (interpret markup) and those I don't have any personal need for (private messages).

    Makeshifts last the longest.

[reply]
      So if you can't read the cookie, perhaps there's a simple way to ask the site who you are? Maybe by parsing the Login Page, it has a fixed format and contains your user name — take the print version, and what you're after is in the first link in the DIV with the id "content".Or maybe there's even a ticker that's even better suited.

      I like the idea of combining a cloaked chatterbox while browsing the site logged in normally. If your browsing and the chatterbox are on the same domain, you can't have that. Not like this.

      Is there something we're overlooking? Some parameter for the request which would make this single request cloaked, leaving the cookie intact?

[reply]

        I like the idea of combining a cloaked chatterbox while browsing the site logged in normally.

        Well, what is the purpose?

        In any case, the login stuff was cruft added for the interim. I don't plan on adding even more cruft to better support a scenario that's only temporary…

        Makeshifts last the longest.

[reply]

In Section Perl Monks Discussion