yeah, i remember that lol, it’s something i’ve been wanting to do since 2019 but since i was a dumb kid in 2019 who barely knew how to make node.js console log “hello world” i wasn’t gonna go far
and since i’ve been coding in node since 2021 i thought now would be the right moment to try this again, i’m still not an expert in node and honestly my code is pretty ugly to look at but with time it’ll get better
that was very random & quite rude? i’ve always said lol i don’t get why it’s a problem, i’m not trying to be “gangster” i’m just a flaming homosexual that’s it
well, it was kinda like 11pm-1am in my time, and i was really asleep saying random things at the afternoon. But let’s just forget about this, i really like your project. You have great future about this, keep it up.
and then login(net.passport.com|.live.com)/RST.srf has to be it’s own can of worms…
Fun fact: 8.0.0562 seems to be the easiest client to try and work with MSNP13, considering it uses the same RST1 request that the release version does, and doesn’t automatically disconnect if there’s an ABCH error.
MSPAuth in MSNP13 is derived from passport’s t=, and MSPProf is p=. MSPProf worked like this before MSNP13, but just saying the field in the initial profile isn’t used for ABCH requests in MSNP13 clients.
if i do figure out how windows live contacts work i could probably help you for sure, however i need to first look into windows live contacts & how it works as i’ve not adventured it yet
Bit of forewarning: Messenger 8.0+ doesn’t use the MSPAuth: “header” from the initial profile, at least for talking to ABCH. It derives the MSPAuth from the passport response’s t parameter (t=MSPAuth&p=MSPProf).
I really need to document more of the stuff I’m researching. Oh well. Most of it is too haphazard and theory-based anyway. I have a working INF for Messenger 1 Beta 2, but whatever, this is an MSNP server development thread, not a “OMG I HAVE BETA WORKING” thread. Nor do I want to make such a thread.