My favorites | Sign in
Project Home Downloads Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 109: Send authorization request only when requested from the client
2 people starred this issue and may be notified of changes. Back to list
 
Reported by jadest...@gmail.com, Dec 15, 2007
 Posted by guest at 2006-03-19 13:43:08

Is this possible?

I decided to move away from ICQ clients and use my ICQ account through a jabber
transport, but I have the problem that I have a lot of people in my
"Awaiting authorization" list, and when I tried it for the first time
(It was 0.6 version) they were flooded with auth requests. As of 0.6, even
those
that were accepted continued to be in the "Awaiting authorization"
list on the server.

I got the SVN version for other bugs, but it seems that this hasn't changed, so
I submit this request So far, the best way to stop the transport from flooding
many people is to comment out the lines that send the auth requests.

Posted by jadestorm at 2006-03-19 17:36:59

If you don't allow the reception of the auth requests, then lots of things are
not going to work right with pyicq.  The jabber side has to know about the
people in question.  The initial flood of auth requests is, sadly, a fact of
life.  There's not really any good official mechanisms of handling such
instances.  James submitted roster-subsync, but it was rejected.  There's
something else but I'm not aware of clients that really support it.  James
wrote
a "webreg" thing that you can find at msn-transport.jabberstudio.org
that will handle all of the auth requests though.  Basically if you use the
webreg tool to register with the transport, it'll handle all of the requests
itself.

Or are you referring to a reverse scenario?  Why don't the people on the other
end just authorize you?  =D  I'm confused.

Posted by guest at 2006-03-20 17:28:56

Hm, well, can't the transport get list of people in question without the
initial
flood?

And can't the transport send an authorization request only when I send an
authorization request from the client?


>  Why don't the people on the other end just authorize you?

I'm having trouble with this one. Because of the bugs with the ICQ client I'm
using, sometimes I remain unauthorized by them. The same was true about the old
version of pyicq-t, if this is fixed in the SVN it'll do, but I'm still scared
of the initial flood and I'm not sure if I want to try.

And there are lots of people that I don't want authorization from (or won't
give
me), who I don't want to flood, I could delete some of them, but that is not an
easy task.

Posted by jadestorm at 2006-03-21 13:14:32

I think we may be having a miscommunication about this.  Perhaps we can chat
about this "live" (via jabber) instead?


Aug 1, 2009
#1 goose...@quantentunnel.de
Sorry to dig out this issue again, but i want to know if there is any solution?

I've recently switched from openfire to ejabberd. It seems the only transport out
there for ejabberd is pyicqt, so I've installed it and registered witm my ICQ ID.

With openfire the ICQ contacts where simply added to the roster. Pyicqt wants me to
approve/auth all of my 150 ICQ contacts.

Is there any way to integrate pyicqt with ejabberd so it does not need this approval?
I don't want the users of my jabber server to reauthorize each and every contact.
Aug 7, 2009
Project Member #2 r000ns...@gmail.com
Psi have option "Auto-authorize contacts". Gajim do it automatically. Not sure about
other clients.
Owner: r000nster
Aug 8, 2009
#3 Mur...@gmail.com
When I turn on the "Auto-authorize contacts" option in Psi, all my contacts receives
the message "You have added" from me every time when I adding pyicqt to roster.
This is not so good, I think must be an option in pyicqt to request or no-request
autorization when adding contact.

Powered by Google Project Hosting