> that would be great if it was integrated into plasma / KDE in general Perhaps, for mtrack that is however the job of the integrator, which in this case are the distros. So distros would have to ship mtrack by default and would have to ship a sensible config and someone would most probably need to write a runtime config because tinkering with xorg.conf and seeing changes only on X restart is not ideal :) I'm not aware if this all would be possible with synaptics though, which is in most cases shipped as default and has quite some extensive runtime config. But I agree that we could/should spend some time playing with the default touchpad config we ship and perhaps offer better usage of the advanced features that are available today.

Ok, thanks a lot, pushed all the things except the "sm_open_session", which I don't understand enough to make a qualified decision about.

Damn good job, thanks a lot! If you'll send me your email address to mklapetek at kde.org I'll push the remaining changes with your name.

Thanks; I've pushed the env var changes to both kwallet and kwallet-pam as well as the socket name prefix. I'm afraid I don't know too much about kwallet internals though, so I cannot comment on why the wallet wouldn't open. I'll try to send the kwallet guys here.

The location of kdewallet.salt is actually a composed path, which you can set using the kdehome= PAM param. It defaults to ~/.local but if you or your distro use ~/.local/share as $XDG_DATA_HOME, you should set the PAM config as such, eg. auth optional pam_kwallet5.so kdehome=.local/share then it will look in ~/.local/share/kwalletd. As for the PAM_KWALLET_LOGIN, I'll have a look (I admit I haven't tested the kwallet4 much).

Yes. The only thing not compatible are the applets, which is why this one exists.

"After April 30th, 2015 apps will no longer be able to access the service or API. This includes both access to chat.facebook.com and the xmpp_login permission." https://developers.facebook.com/docs/chat ...that is all I can say to that :)

15.04. Kubuntu 15.04, ironically, ships only the 0.9.0 as it was not released in time to be included in new Kubuntu.

Right, you can actually get a numeric id _if_ you know the userid (that's what all the services are about) which you'd have to input manually for every single of your Facebook friends. Technically that /could/ work, indeed, but very inconvenient. Other thing would be knowing their chat presence (eg. if they are online or not). ...actually, scratch all that. The Messaging API does _not_ allow sending messages. So...bummer.

@Jacob - I'm not sure what you're replying to, but if it is about the missing contacts - I'm not sure if Facebook lets you search for contacts through the API. And you kinda cannot just guess the user id (it's a loooong number). Plus this would be local only and things like that tend to be very...fragile.

@A_marschke - yes, you can. If you know your friend's id, which you won't because as I mentioned in the text, Facebook won't return all of your contacts :) It could be sort of harvested from user feeds and recent messages and other stuff but this would still give you probably about 75% of all the contacts at best.

@Sudhir - not for the upcoming release, but yes, it's something that should happen. I did raise the issue of naming many times (at least 4 afair), but it always was met with either people not caring or people claiming naming is not important, so I gave up, really... @Buchar - thanks!

@Jacob - the problem with that is that it's something that most if not all distros will be quite unwilling to ship as it will not be exactly legal (though I may be wrong). Personally I don't think there will be much of a demand (among real hackers) to do this, but by all means! @Mikel - yes, I mention all that in the post :) Also, replied to you on the mailing list (not going to copy it here).

@Craig - yes, creating new AIM account is currently not supported in the beta, it misses some config files and it cannot be added because of how late in the development cycle we are. I'll try to figure out a way around this. AIM itself is however still supported by KDE Telepathy. @Reinhard - I strongly suggest sending a mail to [email protected] (subscribe first). Thanks.

Unfortunately no and there will not be (well at least not by me). All focus is now on KF5 version.

Not directly, no. KAccounts is still however storing passwords with KWallet if you have signon-plugin-kwallet installed.

@Sudhir Khanger - There is a connection manager written, but I don't use Telegram myself and really have no clue what's it's status. It's in KDE's git called telepathy-morse if you're interested. @Marko Kivinen - You do have things a bit mixed up, I suggest to read https://dot.kde.org/2013/09/04/kde-release-structure-evolves ...and no, Canonical does not own KDE and in fact, does not even officially sponsor any of it. @spartan - As the blogpost says, bugs should go to bugs.kde.org. That said, you're missing signon-plugin-oauth2 package.