-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restrictions on interest group JS processing power/memory usages #132
Comments
Buyers can prioritize their interest groups statically (e.g. |
The interest group preloaded JavaScript code has many purposes such as:
This means that, even with the help of trusted servers, this bundle could very quickly be extremely large, even without accounting for CPU usages.
This seems infeasible, especially as we expect every browser to have multiple interest group (in the order of thousands, maybe more).
What constraints does Chrome envision for these JS bundles? Size? Maximum computing power? Number of JS bundles per owner?
How will they be enforced (first come, first served?)?
The text was updated successfully, but these errors were encountered: