5 ms·
> I don't really speak legalese, but does permit include having to then make all of your own users agree not to to avoid a penalty? As a service provider, you
by terminalcommand 8y ago
> I don't really speak legalese, but does permit include having to then make all of your own users agree not to to avoid a penalty?
As a service provider, you will need to inform your existing users about this restriction and put the restriction in your user agreement for new users. After that you can relax, if any of your users publish benchmarks, you'll have to warn the user and then take the benchmarks out. You don't have to actively search for violations, but if you notice one on your own, or you get notified (for example via email), you'll need to take it down.
If we're not allowed to share the results of benchmarks and comparisons, the only action that comes to my mind is:
1) Never buy Intel again, if presented with a viable choice!
2) Prepare and share ready-made benchmarking live USBs/utilities, so people can see the horrors Intel has caused them without violating the license.
3) Dump benchmarking results online from countries, where the Delaware courts mentioned in the article has no jurisdiction upon.
4) Get every copy of this microcode license prepared for different countries, sue the license in each of them, and have Intel struggle with it.
- harry8 8y ago5) Publish the benchmarks, dare Intel to sue. Make fun of them for publicity. May be a reasonable and cheap way to get some publicity for a startup. Obviously requires a deeper assessment due anyone looking into it...