Timeline for Offer an XMPP method for chat
Current License: CC BY-SA 2.5
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 7 at 14:39 | comment | added | The Unhandled Exception | I have long since abandoned this project (last work I did was 14 years ago!) but as I remember the transport would intercept an XMPP message with the fkey and cookie and store them in memory. The user sent them as an XMPP message (a message to the chat in their client) but they were never actually posted to Stack Exchange. (The “chat” was a virtual XMPP construct created by the transport) | |
| Aug 7 at 7:46 | comment | added | The Empty String Photographer | @TheUnhandledException Does that seem like a big security issue with everyone able to see your chat login details or am I misunderstanding your comment about sending the fkey and cookie to the chat? | |
| Nov 14, 2010 at 21:36 | comment | added | The Unhandled Exception |
Sorry Jeff, -1 now that I have XMPP write support working. It handles authentication by the user sending the fkey and cookie to the chat
|
|
| Oct 27, 2010 at 3:10 | comment | added | Gnome | @Greg: FWIW, even in IRC identity is not anarchy: the protocol allows specifying a password with your chosen nick and it's up to the server how to handle that. The tradition is to allow unauthenticated users and then use NickServ to identify known users, but there's nothing that says you can't refuse unauthed connections and prevent changing nicks. | |
| Sep 1, 2010 at 21:46 | comment | added | The Unhandled Exception | @Jeff, this could be done in a variety of ways. XMPP supports components which could authenticate the user first, and then allow the user to chat. This could be like a bot -- when you join the chat, the component emails you a link to a web interface where you log in, and that sends a token to the component. I'm thinking of writing something like that this weekend; I've toyed with XMPP components before. | |
| Aug 6, 2010 at 15:39 | comment | added | Jaykul | I'm with Greg on this. You already support multiple OpenIDs, and you ask me for my email address even though you don't need it. XMPP IDs are basically the same as emails (in fact, in my case they ARE the same, but nevermind that) and no less valid as an identifier than OpenID... | |
| Jul 17, 2010 at 5:22 | comment | added | Greg Hewgill | You're dismissing this as a non-starter too quickly. If there were an XMPP interface, then everything else would work today just as it already does, including the one-click OpenID authentication. If a user wants to set up XMPP, then they would have to fill in their XMPP identifier in their profile. This is exactly the same as if they want email to work - you can't email to an OpenID, so the user has to enter their email address. | |
| Jul 17, 2010 at 4:49 | comment | added | Jeff Atwood | @greg there is already a field in the user profile for their OpenID identifier -- that's what needs to work here. If it can't, this is a non-starter. | |
| Jul 17, 2010 at 2:20 | comment | added | Greg Hewgill | Easy; add a field in the user profile for the user's XMPP identifier. Unlike IRC, identity in XMPP is not anarchy, and users can choose an XMPP host such that they can be sure others can't impersonate them. | |
| Jul 16, 2010 at 21:39 | history | edited | Jeff Atwood | CC BY-SA 2.5 |
added 111 characters in body
|
| Jul 16, 2010 at 21:13 | history | answered | Jeff Atwood | CC BY-SA 2.5 |