Marti Admin 9 Feb Re: @hklene: Now I found a way to pacify those warnings Probably in relation to Licensing enforcement (comment). If you could please have a look? That server is returning something bizarre for the url at the @icon check. See #1323. I have temporarily suspended the automatic @icon check... this does still mean that if we see abuse with huge @icon values above and beyond the 256x256 resolution the default TOS action will apply... e.g. one risks their script and account termination. I put in the rejection so it didn't have to resort to this. Thanks for the bug report... next time if you notice you are tripping the server please post on Development so it can be addressed quicker. Your current @icon fails to load client side as well.