-
Notifications
You must be signed in to change notification settings - Fork 288
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kopete replaced by KDE Telepathy #939
Comments
I think KDE Telepathy doesn’t support OTR (yet). That’s why I am still using Kopete. http://community.kde.org/KTp/RepeatedDiscussions/OTR |
@Sami-Perkele Keep using kopete is unsafe, it's an abandoned project, and is almost official that is left without maintenance.
Remember, Unmaintained = Insecure You might want to take a chance on Jitsi, works great on Kubuntu 13.10 without problems. |
But still KDE Telepathy IS NOT Kopete and https://prism-break.org/en/projects/kde-telepathy/ now falsely indicates that it supports OTR. It does not support OTR. |
Do we know if the Without encryption options I feel like it should not be on PRISM Break. |
https://bugs.freedesktop.org/show_bug.cgi?id=16891 It doesn't look like it's supported right now. We can remove it for the time being. |
Kopete/KDE Telepathy are now removed, good decision. Because security is not a priority in them. |
XMPP client without OTR in 2014 is not a valid candidate for default messaging application in any distro. |
KDE Telepathy now has OTR support since version 0.9. |
@Zegnat have you or someone checked if OTR is good, but PGP is necessary too. |
I don’t know. I use neither Kopete nor Telepathy, nor do I use IM services in general. If someone knows Telepathy to support OTR/PGP I urge them to make a pull request and get it on PRISM Break again that way. |
I haven't checked but I can almost guarantee you can't.
|
Kopete is being replaced by KDE Telepathy.
Name should be updated.
Links:
Oficial Site: http://userbase.kde.org/Telepathy
Wikipedia: https://en.wikipedia.org/wiki/KDE_Telepathy
The text was updated successfully, but these errors were encountered: