| Commit message (Collapse) | Author | Age | Lines |
... | |
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Sometimes skyped exits on startup because of the failure of some
underlying C lib (ie we get no expections), that's not something I want
to care about.
|
| | |\ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When TUNNELED_MODE=yes, TUNNEL_SCRIPT (when set) is used to establish a
tunnel. This allows to run skyped.py on a differnt host than the skype.c
bitlbee plugin.
|
| | | | | | |
|
| | | | | | |
|
| | |/ / / |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
So in case a user was not part of a group and it becomes (using Skype
UI), then BitlBee is now aware of this.
NOTE: current it seems the Skype part of this is broken. Use case: adding a
user to group #16 which already has a user.
<< GROUP 16 NROFUSERS 2
>> GET GROUP 16 NROFUSERS
<< GROUP 16 NROFUSERS 0
So it notifies about the number of users changed but I can't query the user
list as the number of users is then 0 - till Skype is not restarted.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
What works: if you have a few buddies in <group>, then /j &<group> will
show just those buddies.
What does not:
- If you later move buddies using Skype UI, BitlBee is not yet notified.
- You cannot move buddies using /invite yet.
What won't work in the near future: only the first group of each buddy
is parsed.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is just the begining, we do not
- store it
- store the list of users in a group nor the name of the group
- track changes after the user logged in
- don't write this info
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
On my setup (Skype 5.0.0.152), echo123 doesn't answer any chat
attempts: even if I use the official client, I get no answer, so
this test fails but not for a reason linked to the bitlbee-skype
plugin.
|
| | | | | |
|
| | | | | |
|
| | |\ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When the user disconnects from bitlbee (either by quitting or by
logging out "account skype off"), skyped should close its connection
and wait for a new connection.
This change is useful to make the test cases pass as otherwise,
skyped would not notice that the first test was done and that the
second test was trying to connect, thus leading to a failure in
the second test.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Since another thread might close the socket, make sure after the
lock is acquired that the connection is still valid.
Add global declaration for completeness
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The Skype API calls the OnNotify callback in a separate thread: see
http://skype4py.sourceforge.net/doc/html/Skype4Py.utils.EventHandlingBase-class.html
Tested informally (chatting with another person for > 15 min)
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
socket for exceptional situations
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Now skyped.py detects broken sockets and restarts itself waiting
for a new connection: this sould help with passing the tests
(see branch NetBSD-test-suite)
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is a restart of the windows-skyped branch based on the updated
bitlbee-skype using the builtin SSL libs of Python.
This version connects, but hangs for long times... to be continued
|
| | |/ / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
it is great !!! thank you so much :)
being able to run skype on a server relieves me from that virtual
machine pain :p
i run bitbee with your module on my openbsd laptop and it works nicely.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This results in shorter code and is available on Windows as well.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | |\ \ \ |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Hi,
when the skype plugin fails to connect to skyped,
it crashes. Not crashing is nicer, because that
results in an neat error message that connecting
to the server failed (and subsequent retries).
The attached patch fixes this crash.
|
| | |/ / / |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
can be useful for openssl-1.0 users where i don't know what cmdline to
suggest atm
|
| | | | | |
|