ohhihohello57
|
After hearing numerous mentions of AIM having "public chatrooms," I was lost on exactly what people meant by that. Were they talking about the private group chats AIM provided, or did AIM have predefined chatrooms way back when? I was thinking that if it was the first option, then listing them on the site would be some sort of privacy breach. Turns out, after some searching around on Google, that it was the latter.
Basically, AIM had their own public chatrooms that were listed on its site (http://web.archive.org/web/20071001010941/http://www.aim.com:80/community/chats.adp). When you joined one, you were amongst other AIM users, and you could message any people from the roster like in a regular group chat.
From playing around with the URI associated with these chats (aim:gochat), they seem to be based on group chats, and I'm wondering if these specialized rooms are being planned to make a comeback. And if they are, then definitely add a section to the site with links to these chatrooms that use the "gochat" action in the AIM URI for easy access. It'd be nice to add, and Tony's dream of Phoenix bringing back the "meet new people" aspect of AIM will come true, which would be something I'd look forward to. :p
BTW, merry christmas! :)
if (Nerd->Personality == (NERD_PERSON_FRONTFACING + NERD_PERSON_SMARTALEC)) { return; }
|
comeaheadback
|
This would honestly be really awesome. But you'd probably be scaling up the resources required for this tbh. I'm not sure if the devs will pursue it.
|
v3l0
|
If anything, they should have a list of hosting mirrors that can be used for the public rooms. If only hosting wasn't so hard with the American ISPs.
|
Tara2
|
A very intrinsic part of the aim experience was the chat rooms. If there was any way to bring them into phoenix I'd hope it was a goal. I'd also piss myself.
|
tonyshowoff
|
I'm not sure if iWarg has plans for that exactly, but I can say that chat is the least documented and most insane aspect of AIM. It's difficult to get working correctly because it relies on several things to happen, in a certain order, with certain information sometimes fairly different between AIM versions and almost none of this was documented by third parties.
Essentially it just takes insider knowledge to do it or the various countless pieces of documentation and their updates and other information about undocumented aspects.
|
drwolf72
|
You guys have to realize that this is a Reboot of the AIM client, although i applaud the developers who made this possible, it will never be the same as the original version.
I, having used it from 1998-2017 (i imagine that most of the new people here even born prior to 1998), saw everything, the chat rooms, meeting people by location, interest, etc.. etc.. Right now unfortunately since facebook took over the instant chat platform, most people wont come back to AIM, so the chat rooms, although i applaud it, probably wont be the place to be
Dont know how much longer i'll be around. If you wanna talk.. will be @Gopher184
|
tonyshowoff
|
>> You guys have to realize that this is a Reboot of the AIM client
Um, no, it's not, it's the server. What the hell would be the point of rebooting the AIM client when services are shutdown? The reason though that iWarg created too an AIM client is to keep development of it going.
>> although i applaud the developers who made this possible, it will never be the same as the original version.
True but it can get close.
>> I, having used it from 1998-2017 (i imagine that most of the new people here even born prior to 1998)
There's a lot of young people indeed, but I personally actually worked on the AIM project in the late 90s.
>> Right now unfortunately since facebook took over the instant chat platform, most people wont come back to AIM, so the chat rooms, although i applaud it, probably wont be the place to be
Facebook isn't the same sort of chat though and while it won't be is big, who cares? There's no reason to think it matters if some people enjoy it, even if it's not a large amount of people.
|
|
![[Reply]](img/forum/topicreply2.png)