Registered Member
|
Running Kopete in KDE 3.5.10, on Slackware 12.2.
Yesterday Yahoo Messenger ran just fine while chatting with a friend. When I fired it up this morning, and each time thereafter, I get a message from Yahoo Administration telling my I'm using a Obsolete version of Yahoo Messenger and I have to upgrade. Along this same line, ICQ quit working weeks ago. Is there a patch for Kopete? Thanks.
Slackware64 with "True Multilib."
|
Administrator
|
Unfortunately this means you now need to upgrade to the KDE 4.3 or higher release of KDE in order to get the newer version of Kopete that uses Yahoo's newer protocols. ICQ will likely be fixed by doing the same.
This is because the KDE 3.x release is not likely to recieve any further new changes and I believe Kopete has been changed significantly meaning patches cannot be directly ported from KDE 4.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
uote] Sorry, but KDE 4.xx is NOT an upgrade. It is pretty, but it is not as functional or configurable as its predecessor, 3.5.x. I ran KDE 4.xx for 6 months before finally moving back to 3.5.10, and found it lacking in everything but appearance. I have yet to read a rational explanation as to why I would want to take a step backwards now, when I need a working desktop, to possibly have at SOMETIME IN THE FUTURE, BUT NOT NOW, a working desktop with KDE 4.xx. KDE 4.xx should NOT have been released until it was as capable as 3.5.10. I'll have to use a different messenger product and/or find another desktop.
Slackware64 with "True Multilib."
|
Administrator
|
Note that it is possible in most distributions to have KDE 3 applications and KDE 4 applications installed alongside each other, so you may be able to use Kopete from KDE 4, while still using KDE 3.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Never mind, "Less functional". That's just rubbish. There's hundreds of features in KDE 4 that aren't in KDE 3 and vice versa.
Madman, proud to be a member of KDE forums since 2008-Oct.
|
Administrator
|
Also note that it is virtually near impossible for developers to fix these "lack of functionalities" without feature requests being made.
Note that KDE 3.0 and KDE 4.0 is more comparable than KDE 3.5.10 and KDE 4.3.0
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
That just has to be purely subjective and just plain nonsense. Name them. Name one thing that make a user more productive?
Slackware64 with "True Multilib."
|
Registered Member
|
With all due respect, WHY would a good working desktop be thrown out the window so the developers can start all over again building a "new one" that, so far, really doesn't bring much of anything other than eye candy to the table? As I said before, the "next generation" in this case, 4.x, should not have been released until it and its applications were as functional and configurable as the previous release, regardless of its number, be it 2.x, 3.x, or, in this case. 3.5.10. Just baffles the mind... Currently I'm experimenting with Xfce and, to be quite frank, it does all I need, and, since it doesn't have the overhead, it is noticeably faster than KDE, and mine is not a slow computer. This whole thing reminds me, for some reason, of Desqview of 20+ years ago. Great product. It had a calculator, an appointment book and calendar, and could remember macros (key strokes), but what it did really well was to allow you to multi-task your DOS applications. All you needed was a 286 with 2 Megabytes of RAM (megs. not gigs.) and you could multi-task WordPerfect, Lotus 123, a comm application like Qmodem (this was before the Internet), your favorite database program, and maybe, another comm program that gave you stock quotes via a special modem on a different comm port. It worked. I miss those days and don't see much need for all the nonsense that has become the GUIs of today.
Slackware64 with "True Multilib."
|
Administrator
|
The whole desktop wasn't "thrown out the window", most applications were directly ported ( such as Konqueror, Help Center, etc )
Unfortunately for some components such as Kicker and KDesktop, they had reached the end of their extensible life, and their code was riddled with bugs, workarounds, hacks, etc which made fixing bugs even more harder. In addition, for those features lost in applications such as Konqueror, this was due to them being part of extensible "plugins" which were unmaintained.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Only one? I'm disappointed. Folder view peeking in Plasma 4.3.
Madman, proud to be a member of KDE forums since 2008-Oct.
|
Registered Member
|
Not sure I know exactly what you mean, but if you are talking about "mouseovers" KDE 3.5.10 has it. KDE 4.2.1, the last version of 4.x I've used, did not.
Slackware64 with "True Multilib."
|
Administrator
|
Reintroduced with 4.3, but nevertheless, this is getting OT
|
Registered Member
|
OK, to get back on topic I was discussing this problem on another board and one of the members had this to say in regard to Yahoo changing their protocol,
"This is nothing new. It's happened several times before. Yahoo wants you to use their IM client so they get the ad revenue from making you look at all the ads. You can't really blame them, they are a business after all. However, ever since alternate 3rd party IM clients started appearing which allow users to avoid Yahoo's ads then that presents Yahoo with a problem. So, every so often they change the protocols in one way or another in an attempt to break the 3rd party clients. Of course, the 3rd party client developers soon catch up and bring out a new release, but it usually takes a little time and is an inconvenience to the users. Yahoo hopes that this will make the users turn back to their official client and restore their ad revenue. If the KDE guys had anything about them, they should expect Yahoo to change the protocol from time to time and design the app accordingly by abstracting the protocol related code into an independently update-able plug-in module. Requiring users to upgrade not only the IM client, but also the entire Desktop environment just because Yahoo change the IM protocol is just bad design. Of course, it's far easier to criticize and say how it should be done than to actually do it, but the point still stands." He does make good sense.
Slackware64 with "True Multilib."
|
Registered Member
|
So now if we can really get back to the topic, lemme see if I can summarize where we are at: * Yahoo changed their authentication protocols, which broke Pidgin, Kopete and a host of other clients * The Pidgin team were able to figure out the issue, patch Pidgin to verify it works, then roll a new version with the Yahoo fix. * According to the bug filed for Kopete, a patch was released and should've been backported. * Currently, Kopete 0.70.90 Using KDE 4.3.1 (KDE 4.3.1) will not connect to Yahoo (Kopete shows that the account is "Connecting" but never progresses from there). Is that the current state of things? Am I missing anything? Is there a way that I can get Yahoo support working correctly? |
Registered Member
|
When you say, "Won't connect", do you mean, "Kopete shows me as offline", or, "Kopete shows me as online but doesn't show any of my Yahoo contacts"?
Because Kopete shows my Yahoo account as being online: I had to use my user-name alone, not my full E-mail address. The full E-mail address didn't work.
Madman, proud to be a member of KDE forums since 2008-Oct.
|
Registered users: Bing [Bot], Google [Bot], Sogou [Bot]