[Pidgin] #5486: "Not Authorized" on some xmpp servers
Pidgin
trac at pidgin.im
Thu Apr 10 12:09:28 EDT 2008
#5486: "Not Authorized" on some xmpp servers
---------------------------+------------------------------------------------
Reporter: swgoddess | Owner: lschiere
Type: defect | Status: closed
Priority: minor | Milestone:
Component: unclassified | Version: 2.4.1
Resolution: duplicate | Keywords:
Pending: 0 |
---------------------------+------------------------------------------------
Comment (by swgoddess):
Well, I did actually put the IP in as the connect server and it took some
playing around and googling for ideas to get it to work. But get it to
work I did.
I did not assume idiocy, btw. I don't do networking stuff for a living, I
assumed you'd all actually know how it works and be able to actually
provide concrete help for those of us that don't deal with server level
stuff every day. XMPP is outside my area of expertise and I don't really
want it inside my area of expertise. I just do real time embedded control
systems (hardware/firmware) and I'm used to having to design for the
idiots. That was more my point. Some of us are fairly ignorant and need to
be accounted for. When it came to looking for already entered bug reports
even after reading about how to set up a custom query I did not find the
closed defect that I was duplicating, and once you all pointed it out to
me and doing what it had said to do I still couldn't get things working
and I can read government rfp's and understand them, so I'm not quite a
moron (although with govt docs and specifications it would probably help).
I'm very computer literate, I could design you one from the mobo up, I'm
just not into the client/server thing. That's what you guys do (and I use
guys generically, it's not an assumption of maleness, hell, as a female
electrical engineer I'm quite used to being called dude). I expect you to
know how.
Keep in mind that old is a way of life out here. I do read release notes,
and they gave me no clue whatsoever about what was going on. Some people
are hesitant to upgrade anything because it always causes a compatibility
nightmare with other things. Admins as well as users. Yeah, the tech
community has a tendency to jump on all things new and shiny, but some of
us are old and not as willing to live with the nightmare of conflicting
versions of x, y, and z as we used to be. Life is increasing ly short.
Anyway, that's my form of an apology with a caveat. :) You try being in
the middle of updating corporate design process and procedures that has
been going on for 6 months while your newly developed hardware sits and
waits for your priorities to be revised again. It makes for a bad mood.
--
Ticket URL: <http://developer.pidgin.im/ticket/5486#comment:5>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list