View Single Post
Old 12-07-2021, 04:52 AM   #76
Leseratte_10
Groupie
Leseratte_10 ought to be getting tired of karma fortunes by now.Leseratte_10 ought to be getting tired of karma fortunes by now.Leseratte_10 ought to be getting tired of karma fortunes by now.Leseratte_10 ought to be getting tired of karma fortunes by now.Leseratte_10 ought to be getting tired of karma fortunes by now.Leseratte_10 ought to be getting tired of karma fortunes by now.Leseratte_10 ought to be getting tired of karma fortunes by now.Leseratte_10 ought to be getting tired of karma fortunes by now.Leseratte_10 ought to be getting tired of karma fortunes by now.Leseratte_10 ought to be getting tired of karma fortunes by now.Leseratte_10 ought to be getting tired of karma fortunes by now.
 
Posts: 183
Karma: 3587000
Join Date: Sep 2021
Device: PB Era, PB InkPad 3 Pro
I took a look at the MacOS versions of ADE over the last couple days, and I don't think it's worth it to try to emulate a MacOS ADE as well. If it was similar to how it works on Windows, I would have just made the plugin emulate a MacOS ADE when importing an authorization on MacOS, and a Windows ADE otherwise, but the MacOS versions send way more information (exact ADE build version, exact MacOS version, ...) to the servers, and they also do it in a different way than Windows.

So without me having access to a Mac, and analyzing all the available ADE versions, I doubt I could get the communication by the plugin to look 100% exactly like ADE on MacOS - so "switching" a MacOS authorization to Windows by importing it into the plugin probably has a way lower chance of Adobe detecting this than me trying to botch emulation of the MacOS ADE requests.

It's probably fine either way, but if you want to decrease the chances of Adobe detecting that you're using this plugin, don't import an authorization on MacOS.
Leseratte_10 is offline   Reply With Quote