it's funny because the modern expectation is OpenID Connect (i believe so anyway), which is based on OAuth 2.0, but is completely separate from OpenID Authentication 2.0, which is what you'd have to implement, or try to, as even OpenID says that OID2 had a lot of implementation quirks to deal with.

i mean it could also be "vtable passed in by reference set by a constructor which sets the reference which is set by another classes constructor after it sets it to a purecall holding table for a reference"

Or, you know, there is always COM/OLE Automation if you want more references to references.

This works normally if you go out of your way to use OS-specific title bars.

Oh wait no that's an "unintended feature" and "doing it wrong" ignore I said anything before you get asked "use case?".

Judging from the implementation, I can only assume this is deliberate.

(setx GTK_CSD=0)

Nothing too bad, just the team has been quiet for a while, and was wondering what has happened since.

I'm a bit concerned with the terms of "some help from Escargot" for various reasons, can you elaborate?

I'm going to assume it's for patching MSIDCRL40 in a way that doesn't break it, or RST implementation details.

0.32? Why?

「0.32」しかし、なぜ？

Probably just use 'corepack yarn'...

おそらく使うだけ「corepack yarn」その代わり

oh so that's why it's in the context menu now

@messenger.hotmail.com @muser.messenger.hotmail.com where yo tcp 1863's at

My (least) favourite past-time is figuring this endless crap out, regardless of public documentation or not.

SOAP might of been a footnote on XML history if it wasn't for Microsoft's (ab)use of it in the early 2000s.

They also shoved XML in all the wrong places, regardless of SOAPification or not

That's vile, and I never want to read this again.

Imagine a namespace for every verb.

... To be honest some people would do that, which may be worse.

It's probably more reasonable with actions instead of dedicated namespaces.

I'm aware MSNPiki has some werid names for things, but even then I haven't found their source.

Though for a lot of things MSNPiki has... I like to call them "problems with giving original context to commands" (Great example: SBS)

It's the main reason I started my own place for documenting MSNP.

funny how you mention msidcrl, when that only became important with MSN Messenger 7.5, which introduced SOAP authentication (some call it passport 3.0 for, some reason? I haven't found why, probably old forum stuff)

Before this point you'd have to change wininet.dll. Good luck with protected DLLs!

HTTP/2 undefined header translation moment

... That is the issue, Cloudflare (in almost all cases) requires HTTP/2. It's easier to just patch the function that reads the header or change the bytes in the binary directly.

trust me I've written things to generate those XMLs, they're not fun.

Even worse is Address Book Service (abservice). That thing is stupid. I've documented it, to my dismay, but it seriously breaks markdown with the layering I do.

yellows111.darkok.xyz/msnp/service...

you still have to deal with Passport 1.4 which is a whole can of worms of "documented until it isn't"

trust me you don't know what your asking for

- resident MSNP expert who answered this same question a few weeks ago

WAITER! Another 10 XML namespaces in the soap:Envelope please!

[xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"]

That's hilarious in a bad way, had these not been flash ROMs I may of considered that every one of these on the market has a dead BootROM.

Not saying "buy more and hope you find one that works". I wouldn't believe that yours is the only one with such corruption either.

gotta love x86 network appliances, one of my favourite types of devices

That being said, basically anything about AOLTV, except that it exists, is undocumented, which is so funny.