aMSN Forums
February 19, 2020, 10:50:07 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: New forum for aMSN !!
  Home Help Search Login Register  
  Show Posts
Pages: [1] 2 3 ... 630
1  Development / Amsn development related issues / Re: aMSN/WLM Diehards read this! on: January 13, 2013, 10:45:03 pm
yes, you're not the first person to suggest this and no, it won't happen...
1 - there is no time or motivation to reverse engineer the server side or to implement it (with databases and all that, instead of just 'a client').
2 - servers cost a lot of money
3 - people online on this 'new msn' will only be those connected to that server, which will be very small...
4 - there's XMPP which is much better if that's what you want, just move to xmpp/jabber and you're done, you can run your own server at home, protocol is open, and the server will interact with other xmpp servers so you can see everyone online
2  Other Languages / Français / Re: 0.98.9 : retour à la v. 0.98.4 ! on: June 15, 2012, 11:02:11 pm
1) ca devrait plus le faire (mais ceux sur 0.98.4 n'auront plus la notification non plus), malheureusement on a fait une erreur dans la release 0.98.9
2) ouch, bug stupide, ca a ete corrige dans la version SVN.
3) ca j'ai pas trop compris ce que tu veux dire.

Si vous voulez une aide pour corriger le 2eme point et retourner a la version 0.98.9, faites le moi savoir, je vous donnerais quoi changer.

@Couin, si t'aime pas cette version "pourrie", t'a qu'a ne plus l'utiliser.
3  aMSN Support / Macintosh / Re: Voice Clips on: June 15, 2012, 10:51:47 pm
could you be more precise in how you "have trouble" receiving voice clips? A detailed explanation of the problem is needed before we could help.
4  aMSN Support / Windows / Re: Problems with 0.98.9 on: June 15, 2012, 10:47:15 pm
The 1st and 2nd errors seem to be related, but without the detailed error, we can't really fix it.
The 3rd one is known and it's because of a typo, we can't fix it without releasing a new version, so we've reset the server to not notify of the new version (even to those on 0.98.4).
If you can reinstall 0.98.9 and retry, and give the exact error you get (click details and paste the whole thing), we might be able to fix it for the next release.
5  Development / Amsn development related issues / MOVED: Voice Clips on: June 15, 2012, 10:17:42 pm
This topic has been moved to Macintosh.
6  Development / aMSN2 / Re: What is done? on: December 21, 2011, 01:15:00 am
not dead.. just developers have moved on and it's waiting for new people who would like to contribute to it... amsn2 is still the future, amsn 0.99 is still being worked on.. but at a very slow rate, that's all...
7  Development / aMSN2 / Re: AttributeError on: October 12, 2011, 04:16:30 am
Please send a patch to those fixes at least, it might help someone else move ahead with the code (I might look at it later)
8  aMSN Support / Other OSes / Re: aMSN on WeTab on: August 14, 2011, 01:30:34 am
note, you need to install gcc-c++ not gcc-g++ since that package doesn't exist...
9  The Community / Feedback and Suggestions / Re: msn work better with ... on: July 02, 2011, 01:39:56 am
We know emesene, they were supposed to merge with aMSN for the aMSN2 project but they never did...
I suggest you read the amsn2 announcement to know what the future of aMSN is :
10  The Community / Feedback and Suggestions / Re: maybe no on: July 02, 2011, 01:37:56 am
OK, I can understand the need for income (and I probably would pay something for a clean installer if it came to that)... But adding this sort of crapware to the installer is really a bad move.

Firstly, anyone with a clue will skip that step in setup.
Second, so many AV programs are detecting aMSN's installer now that it will be hard to download (or worse, waste people's bandwidth as they re-download the file their AV keeps deleting).
Third, the few people stupid enough to blindly click to install whatever rubbish Opencandy supply are also stupid enough to simply jump out and claim aMSN is a virus, and loudly spread the word that it is.

Moving along, I know it's your forum, but the swearing seems unnecessary. I'm a fairly long time aMSN user (I vaguely remember version 0.6 being exciting), and have promoted it endlessly to anyone who ever says bad words about any other MSN client...
I'm fairly offended that the author of the software would stoop to the lows of name calling and swearing just because someone dared to question possible malware being distributed with the installer. I know he/she was blunt and a bit rude, but a rant with Tourette syndrome seems a little

Personally, I'm fine with skipping the suggested rubbish and getting on with things. In fact, I did ages ago without even noticing. The only reason I'm here now is because my AV software said the installer I still had sitting on a server was infected (it saw it when I was browsing that folder for the first time in months).
First, OpenCandy isn't "crapware", there were other propositions for an installer partnership which we refused and decided to choose opencandy (even if it gave less revenue) because we think it's a good project. The 'recommended apps' that are shown in the installer were chosen by us, anything we didn't like, we removed from the selection, so it's not them suggestion 'anything' to you. Secondly, even if it means roughly 5 times less revenue, we made the installer with opt-in instead of opt-out (by default it doesn't select "install").

Also, like you said, anyone with a clue will skip that step (and you didn't even notice it).. good for them, how is it an issue then if you can just simply skip it? I don't see an issue with that personally.  As for the 'virus' issues, opencandy was never considered a virus and it doesn't make you install adware/spyware (only useful apps that we chose ourselves), but a few months ago there was an issue when the microsoft defender decided to flag opencandy as a virus, and opencandy have been very responsive with us and they got in contact with microsoft, figured out what microsoft didn't like, fixed their SDK, redeployed, we recreated the installer, they did the QA of the installer and we rereleased a new installer, and it was all during a few days (less than a week if I remember correctly).
Stuff like that happens, and you got your AV to flag it only because you had the old installer and an updated virus definition. This also has little to do with OpenCandy itself since I believe it happened twice before that amsn.exe itself was flagged as a virus for no reason until the AV programs fixed that false positive.

About the 'Tourette syndrome', you're saying that you're offended, in which case I apologize to you, however, you have to put yourself in my shoes, you need to understand that after giving support for 10 years to the millions of users that we have, my temper got short, and I have absolutely no tolerance for people who are rude! The original post wasn't about OpenCandy and being flagged as a virus, it wasn't about "why is it there?" it was some random guy giving us an order, thinking he's superior to us and that we must comply to his wishes simply because he says so. I would have taken a completely different tone if there was a single "please" or "could you..?" in his post, but there weren't, it was an ultimatum: "If this is not removed soon I going to use the official msn.", it was a threat! I believe that he deserved far worse than what I replied to him with, as I don't like being threatened.
You don't go to someone's house after they invite you for dinner and then you threaten them to bring you some champagne or you're going to leave... then complain if they tell you "well then, get the fuck out of my house".
So like I said, I didn't swear because he "dared to question possible malware being distributed", I sweared because of his assertions and threat and completely rude attitude. I believe that someone who does not respect me does not deserve respect in return.

Hope that answers your questions!
11  Development / Amsn development related issues / Re: Audio/Video conversation on: July 02, 2011, 01:13:06 am
So what is needed in order to bring us forward to MSNP18? I may be willing to do some work on this.

Would it be possible to build a protocol on top of the MSN protocol for usage in amsn to amsn conversions, or amsn to pidgin conversions? With that we would not be as pressed to keep up with Microsoft's changes in the protocol. Instead we could just implement something that are stable, but incompatible with their clients.

For MSNP18, we need P2PV2 support, we already refactored the P2P stack in order to more easily allow P2Pv2 implementation but it hasn't been done yet.
For a non-MSN protocol, etc.. just use XMPP, it's an open standard IM/VoIP protocol, so just use that if you want (that's what Jabber, google talk and facebook chat uses).
12  Development / Amsn development related issues / Re: bug with amsn svn version on: March 23, 2011, 07:52:01 am
The svn version shown in the about page is basically "svn version of the last modified .tcl file".. if a non .tcl file is modified (a .dll, or the makefile, or an image of the skin, or something in another branch and not the trunk, main development branch), then the svn version will be incremented but not the one in the about page.
13  Other Languages / Français / Re: Horodatage des logs en format "unix", comment traduire ? on: March 04, 2011, 12:30:59 am
Moi je ferais directement dans un terminal :
echo "puts [clock format 1297511628]" | tclsh
14  aMSN Support / Macintosh / Re: Deleting some of my cache of profile pictures? on: March 03, 2011, 09:56:34 am
On Mac, it's in your Home -> Library -> Application Support -> aMSN
15  aMSN Support / Macintosh / Re: WRONG USER NAME OR PASSWORD on: March 03, 2011, 09:55:29 am
Try with a clean configuration.. go to your Home directory then Library -> Application Support -> amsn
and rename that amsn directory into something else..
Pages: [1] 2 3 ... 630
Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!