Bug 221537

Summary:	kopete skype protocol does not show contacts avatars
Product:	[Unmaintained] kopete	Reporter:	Alin M Elena <alinm.elena>
Component:	general	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	wishlist	CC:	ict, igor.poboiko
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Alin M Elena 2010-01-06 15:42:23 UTC

Version:           0.99.80 (using 4.3.86 (KDE 4.3.86 (KDE 4.4 >= 20091231)) "release 7", KDE:KDE4:UNSTABLE:Desktop / openSUSE_11.2)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.31.8-0.1-desktop

kopete skype protocol does not show contacts avatars

I had fast look through the API and I still do not know if is an API limitation or a TODO for kopete.

Alin

Comment 1 Alin M Elena 2010-01-19 22:27:39 UTC

api limitation

Comment 2 Störm Poorun 2010-09-16 19:51:04 UTC

Please reopen: as Pidgin now supports avatars via Skype, so there has been some API change, or another mechanism to access the avatars.

See: http://forum.skype.com/index.php?showtopic=99471&view=findpost&p=1523411&s=dc2e0739f24d84a78318d1f062255c94

Comment 3 Igor Poboiko 2010-09-16 22:58:23 UTC

According to pidgin's plugin source code:
http://code.google.com/p/skype4pidgin/source/browse/trunk/libskype.c
it goes to ~/.Skype/accountName/*.ddb and gets avatars from these files. 

After sending messages like 
"GET USER %user% AVATAR 1 /tmp/kde-eol/kopeteV13983.png"
skype answers:
"ERROR 1 General syntax error"
as described in link you post here. So there is still no correct API mechanism to get avatars.

Comment 4 Störm Poorun 2010-09-17 00:03:50 UTC

Thanks for looking into that source.

How feasible would it be for someone to apply a mechanism in Kopete, similar to the one used by the Pidgin plugin?

I am willing to help, albeit with my limited skills in this area.

I agree with your conclusions about the current state of the Skype API.


However, I still submit this bug should be reopened, with this workaround mechanism in mind (and in the long term with the improved API in mind).