no_identd

You might want to add @jansc's https://github.com/jansc/tmjs

@alranel @lordofhyphens @foreachthing @henrikbrixandersen @hroncok @ntfshard @platsch @Samir55 @xoan there's MULTIPLE active, fully disclosed vulnerabilities in slic3r & libslic3r (note: I'm well aware *some* of these *might* be bullshit "vulnerabilities"...

Any update on this? #51 seems done, via https://github.com/haskell/win32/pull/70

I also would strongly recommend avoiding exposing CreateProcess at all. Instead, explicitly bind to CreateProcessW (Unicode version), and maybe CreateProcessA (ANSI version). (the win32 package does seem to only expose...

@Syonyk: As far as I know, H.264 can also support SVC.

No, because it ain't fast enough yet for the horrible abuse to which I wanna subject it, much worse than what you do here. :p I don't have a lot...

#3 seems like an outstanding step, if you want to take a stab, @WolfieWerewolf 😇

See also: https://techcommunity.microsoft.com/t5/exchange-team-blog/announcing-oauth-2-0-support-for-imap-and-smtp-auth-protocols-in/ba-p/1330432 And: https://techcommunity.microsoft.com/t5/exchange-team-blog/announcing-oauth-support-for-pop-in-exchange-online/ba-p/1406600 Albeit full Microsoft Modern Authentication would probably require a whole additional library at the very least, and it's probably not an exact fit for this...

I was just about to ask about conditional access policy support. I figure it probably requires AzureAD app registration & MFA support, and supplying the device ID?

> using the AD groups as contact groups - that makes a lot of sense! I'd guess that's what the Lync/Skype for Business developers thought, too, when they made that...