adium
Evaluate and Update or Remove apparently obsolete services
AIM, possibly others.
- determine which are obsolete
- remove from code
- ensure code still works
[Edited by @RobFog] List of services to consider removing:
- AIM (see also #20)
- MSN
- GoogleTalk (?) (see also #1)
- Yahoo! and Yahoo! Japen
- LiveJournal
- MobileMe
Please dont remove aim. I actually just made a feature request for a modification to it to make it useful (before seeing this issue).
I am skeptical that there are good reasons to keep AIM for AIM Phoenix. Let's discuss AIM at #20, the issue you opened.
Other services to remove would be:
- MSN
- GoogleTalk (?)
- Yahoo! and Yahoo! Japen
- LiveJournal
- MobileMe
Facebook cut off access to their messenger API quite a while back because it was undermining exposure to ads.
At some point, I noticed it happened to be working again. I don't think it was a policy reversal on their part, so I'm not sure what the resulting state was.
Anyone know?
I'm sure Adium's current Facebook implementation doesn't work. This libpurple plugin does and is being actively developed: https://github.com/dequis/purple-facebook works. We should consider removing built-in support and pointing to the plugin instead.
I'm sorry but I don't understand the question. MSN has been dead for a long time: https://en.wikipedia.org/wiki/Windows_Live_Messenger
A bunch of this is done in my fork here: https://github.com/jas8522/adium
But I'm stuck where the main project is stuck: I can't tell the results of my changes without being able to compile it.
@RobFog you are correct. In the Discontinuation section of that article, it says:
On the same day [February 15 2013], Microsoft announced its plans to phase out Messenger: The process would start on April 8, 2013, with English users and would end on April 30, 2013.
It needs to be dropped.
Also, at https://en.wikipedia.org/wiki/Yahoo!_Messenger#Adoption it says that:
At the time of Yahoo! Messenger's closure in 2018, it remained popular in Vietnam.
What are the implications of that?
I'm sure Adium's current Facebook implementation doesn't work. This libpurple plugin does and is being actively developed: https://github.com/dequis/purple-facebook works. We should consider removing built-in support and pointing to the plugin instead.
Shall we create a separate issue to track that move to use FB messenger with libpurple?
I think we need to have a general discussion about which services to support etc. It might be better to leave that discussion for until we have released the minor update with build fixes and the scrolling bug fix.
https://en.wikipedia.org/wiki/Yahoo!_Messenger#Adoption
Also, at https://en.wikipedia.org/wiki/Yahoo!_Messenger#Adoption it says that:
At the time of Yahoo! Messenger's closure in 2018, it remained popular in Vietnam.
What are the implications of that?
None. It's dead.
I think that Google Talk always works, no? The only point is that Google Talk has disabled the XMPP Federation when:
May 19, 2014 - permanent upgrade to encrypted network, coinciding with Open Discussion Day:
- http://opendiscussionday.org/
I don't understand @Neustradamus . By the way @RobFog , what do you mean by the "scrolling bug"?
MSN/WLM -> Escargot : https://escargot.log1p.xyz/ + https://escargot.log1p.xyz/news + https://gitlab.com/escargot-chat AIM/Yahoo/ICQ -> http://iwarg.ddns.net/phoenix/ + http://iwarg.ddns.net/phoenix/index.php?action=faqpage + https://www.phoenix.wildman-productions.org/
Neustradamus - could you assemble details on current working state / updates required to work on either of those platforms?
As @RobFog said:
List of services to consider removing:
- AIM (see also #20)
- MSN
- GoogleTalk (?) (see also #1)
- Yahoo! [Messenger] and Yahoo! Japan
- LiveJournal
- MobileMe
We haven't discussed LiveJournal and MobileMe yet. We have discussed:
- AIM (see also #20)
- MSN
- GoogleTalk (?) (see also #1)
- Yahoo! [Messenger] and Yahoo! Japan
The general opinion is that these should be removed. @Asher- can you evaluate the status of the other ones?
@Asher- is busy with other things. I would suggest someone else handle reviewing each protocol for removal or not. Once a full list of the protocols with justification for each modification or keeping them is taken care of, it'll be easier for him or someone else to make a determination on the how if everyone on the agrees on the what.
So if something like this were filled out by someone it would be helpful:
| Service | Officially Supported | prpl status | Proposed Action | Reason |
|---|---|---|---|---|
| AIM | No | something | Hold | No official support, there are some unofficial servers which require investigation |
| MSN | No | something else | Remove | Some reason |
| IRC | Yes | prpl is currently being updated | Keep | Something else |
This table is just an example. We can comment back and forth on each protocol individually if this doesn't make sense, but it would be more organized to get a summary table together showing the whole picture in one easy to use table.
@estella144 and @Neustradamus if you would like this might be up your alley but it's just a thought.
@ChrisForsythe I am quite interested, but I think this should be done by 2 people. @Neustradamus are you interested?
| Service | Officially Supported | prpl status | Proposed action | Reason |
|---|---|---|---|---|
| AIM | No | [To be filled in] | Remove | Dead for a long time |
| MSN | No | [To be filled in] | Remove | Dead for a long time |
| IRC | Yes | [To be filled in] | Keep | Still active (many servers, we use it) |
| No | API disabled | Remove | API has been disabled by Facebook | |
| XMPP | Yes | [To be filled in] | Keep |
@Asher- hg? I can't install hg.
hg is mercurial. Really you just need to know what a prpl is and then how to check the status. A prpl is a pidgin protocol library. So aim would have one, irc, etc etc.
Finding out the status might be as simple as loading up pidgin and seeing what it offers, can connect, etc. rather than going through the mercurial repository. It could be handing that off to someone else while checking for official service statuses on each available protocol.
About AIM/Yahoo/ICQ and MSN, I do not use but there are supported servers... Maybe good to keep, maybe a little change is needed... It will be bad to remove it...
- https://github.com/adium/adium/issues/18#issuecomment-795291127
I will try to contact users...
I do not use IRC, I use XMPP, example Pidgin MUC Room is: xmpp:[email protected]?join
Recently, Pidgin has launched a PidginChat: https://pidgin.im/about/pidginchat/ It is XMPP service without the XMPP Federation.
We definitely should not remove support for MSN, AIM, or Yahoo, as new servers and services have been developed which support these protocols, so Adium users need support for these protocols to connect to these services.
Escargot supports Yahoo and MSN:
https://escargot.log1p.xyz/
AIM Phoenix supports AIM: http://iwarg.ddns.net/phoenix/index.php
That these new implementations of these protocols exist means Adium users can benefit from the continued support for these protocols to connect to these servers.
Also Google Talk is working fine. All Google Talk is, is an XMPP service anyway.
@toeserve seems reasonable to me, particularly for AIM / Phoenix.
Generally: wasn't Yahoo/MSN already removed a while ago? I don't see it in the list Adium presents to me when trying to add a new account.
- MobileMe: I can't see any reason why this should still exist
- Google Talk: may as well remain while it continues to work (I kinda thought it would be dead by now). Perhaps it should be rebranded to Google Hangouts or Google Hangouts Chat? It would make sense given that Wikipedia says the following which implies it only works with Google Hangouts: "The Google Talk App for Android and the Google Chat tool in Gmail were discontinued on June 26, 2017 and no longer function. Users may still continue to use third-party XMPP clients to connect to the legacy Google talk server, but only for 1-on-1 chat with Hangouts users."
- Facebook: As this issue is to track removal of services, I still think we should create a new issue to track the replacement of the existing implementation (which people have indicated above does not work) with the working purple-facebook library here, as @RobFog indicated above.