Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Colin Barrett <timber@la...> - 2005-11-17 21:50:06
On Nov 17 2005, Greg Hudson wrote:
> I'm not sure what your argument is here. I'm saying that in a more
> perfect past, the JID spec would have been
> Then a string with no "@" sign would not be a valid JID, and a client
> could append "@default-domain" to it with no fear of corrupting a valid
> JID. The parser would not "fall apart because the node is empty"
> because the spec would allow for it.
> Obviously, in the world we actually live in, we're pretty much stuck
> with a JID syntax which accepts bare words and treats them as domains
> (not node names as I would prefer), but I was very clearly talking about
> a hypothetical.
Honestly, this sounds like something you should take up with the Jabber
folks; Gaim is just adhering to the Jabber specifications. My
reommendation? File a JEP for this and see what happens.
From: Christopher (siege) O'Brien <siege@pr...> - 2005-11-18 04:50:51
On Thu, 2005-11-17 at 23:34 -0500, Luke Schierer wrote:
> This is exactly my own concern. I want our users to be able to use
> gaim, but I also want them to learn where it is necessary.
I'm not sure if it's applicable, but with the Sametime bits the addition
of a user is intercepted and checked against a server-provided resolve
service. The resolve service will do things like find near-matches for
both the user ID and possibly the full name. If more than one result is
found (or if the result is not identical to the given ID), Gaim then
prompts the user with the results.
Is it possible to attempt to look up both a domain and a local buddy and
determine if one is invalid? If so, it seems that turning around and
prompting the user with a "Did you mean... ?" dialog in the event of
ambiguity might be an easy solution.
Christopher (siege) O'Brien <siege@...>