|Jabber LJ_Bot client feature request - gmail interface!
||[Jul. 10th, 2007|03:55 pm]
LiveJournal Client Discussions
So I don't quite know if this should be posted here or if this should be posted in lj_dev, so sorry if it's wrong.|
I don't quite know how the lj_bot is implemented and how neccessary it is to run on it's own server, however, it would seem to me that if we could provide a setting in our lj profiles for a gchat id, then if the lj_bot were to connect to gchat, it could verify that setting, and authenticate a gmail user as the equivalent lj_user and implement all the same functionality it already has. I'd love to be able to make posts from my gmail account on the run.
[Mid Writing Edit] It looks like you can add Frank to your gmail buddylist, you just: [16:06:41] LJ Bot (Frank) (bot): Can't post from non-LiveJournal Jabber addresses yet. [/Mid Writing Edit]
Is there any update on the schedule for this feature?
2007-07-10 07:58 pm (UTC)
LJ profiles already have spaces to fill in a GChat and/or generic Jabber ID. So it seems all that's missing is the logic for the lj_bot to validate an incoming Jabber IM from a different server by verifying that the Jabber address is listed in the journal owner's profile.
I personally haven't delved into LJ's codebase very much, but if someone could let me know whether that feature is assigned to someone who is actively working on it, or where specifically I would look in the codebase to make the changes [what's the repository path], I could take a look. To me it seems pretty simple:
- Examine incoming e-mail address and host,
- Search for a user via the field matching the domain for the client
- If there is a match, give @gmail account ability to act just like @livejournal profile that was found.
- And finally return to existing code for the rest of the processing.
Issues that would have to be resolved: what happens if a user wants to be able to post to multiple accounts from the same gmail address, and how do you verify that e-mail address really belongs to the user at the time they put it in. Those issues can be resolved at the time they enter the e-mail address into their profile via a challenge response situation, and by adding to the lj_bot syntax, maybe with a simple change to the regex already in use. post: @journal_name@ [subject] postbody...
Should this all be in lj_dev?
Actually, that syntax could actually solve the problem across the board. Require @journal_name@ for every foreign jabber post, and then that simplifies the search, because the server just needs to look up that specific journal and check it's settings... since you can't currently use jabber to post to communities, it's not even a problem for those! If you want to enable community support you can just fallback to the other behavior I described, it would be slower, but workable nonetheless.
2007-07-10 10:07 pm (UTC)
Yes, you need to take this to ljdev. They don't read this community.
Sadly enough, my post was too verbose or something, because it was not passed through moderation to appear on the lj_dev page. I didn't get any reason for it, but now it's been a solid 2 weeks and some and in the meantime several new entries have been posted. What should I do, give up?