issues
search
w3c
/
compute-pressure
A web API proposal that provides information about available compute capacity
https://www.w3.org/TR/compute-pressure/
Other
69
stars
10
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Sampling interval instead of sampling rate
#253
foolip
closed
8 months ago
8
Expand discussion about timing vs external pressure
#252
kenchris
closed
8 months ago
0
Add info about another attack type
#251
kenchris
closed
8 months ago
1
Combine Compute Pressure API with WebRTC features
#250
MatanYemini
opened
9 months ago
2
Energy measurement: Track energy consumption for a tab
#249
arskama
opened
10 months ago
1
Update OT token
#248
kenchris
closed
10 months ago
1
Add Accessibility considerations
#247
anssiko
closed
11 months ago
1
Exposing low-level metrics via permissions
#246
DenizUgur
opened
11 months ago
2
Update security and privacy self assesment documents
#245
arskama
closed
11 months ago
0
Use right notation for default allowlist value.
#244
arskama
closed
1 year ago
0
Permission policy needs to be checked when owner set changes
#243
kenchris
closed
4 days ago
0
Add user interactions to use-cases
#242
kenchris
closed
1 year ago
1
Provide guidelines for mitigation algorithms
#241
arskama
closed
1 year ago
5
Provide better timing guidelines for mitigation algorithms.
#240
arskama
closed
1 year ago
0
Require all owning documents to have permission policy enabled
#239
kenchris
closed
1 year ago
1
Support workers in privacy algos
#238
kenchris
closed
1 year ago
9
Demo rework
#237
kenchris
closed
1 year ago
1
Use same origin checks instead of same origin-domain ones
#236
arskama
closed
1 year ago
3
Use-case: For improving interactivity
#235
nhelfman
opened
1 year ago
3
editorial: Do not use unordered list in "passes privacy test" steps
#234
rakuco
closed
1 year ago
1
Use-case: Analytics / RUM
#233
nicjansma
opened
1 year ago
2
Fix another reference for "map/exists"
#232
arskama
closed
1 year ago
0
Fix reference to map/exists.
#231
arskama
closed
1 year ago
0
Fix penalty algorithm
#230
arskama
closed
1 year ago
6
Data delivery and mitigation penalty algorithm issue.
#229
arskama
closed
1 year ago
3
Does compute pressure reflect OS-level speed limit changes due to throttling?
#228
brycepj
opened
1 year ago
10
Fix definition of ChangesCountMap
#227
arskama
closed
1 year ago
0
Fix definition of ChangesCountMap
#226
arskama
closed
1 year ago
0
Break calibration
#225
kenchris
closed
1 year ago
0
Note TAG guidance on private browsing modes in mitigations
#224
anssiko
closed
1 year ago
5
Add rate obfuscation test requirement
#223
kenchris
closed
1 year ago
0
Fix 'declared policy' reference
#222
anssiko
closed
1 year ago
1
fix anchor for declared-policy
#221
arskama
closed
1 year ago
0
Broken references in Compute Pressure Level 1
#220
dontcallmedom-bot
closed
1 year ago
0
Add proposed Cross-site covert channel attack description
#219
anssiko
closed
1 year ago
1
Improve User notifications section
#218
anssiko
closed
1 year ago
0
Fix 'declared policy' reference
#217
anssiko
closed
1 year ago
0
Reorganize Security and privacy considerations
#216
anssiko
closed
1 year ago
4
Same-origin check for workers
#215
anssiko
closed
1 year ago
1
Update demo for OT
#214
kenchris
closed
1 year ago
0
Allow an array of sources
#213
tomayac
opened
1 year ago
1
Fix example 5
#212
anssiko
closed
1 year ago
1
Use-case: Automated performance regression testing in Utopia
#211
Rheeseyb
opened
1 year ago
1
Adding Wei and Raphael to contributors list
#210
arskama
closed
1 year ago
0
Add ack to the PING for their great privacy review and feedback
#209
kenchris
closed
1 year ago
0
Fix typo in "Contributing Factors" section.
#208
rakuco
closed
1 year ago
1
Update S&P section to reflect rest of spec
#207
kenchris
closed
1 year ago
0
"first party context" section concerns
#206
pes10k
closed
1 year ago
3
"no side channels" subsection issues
#205
pes10k
closed
1 year ago
2
Specify what kind of attacks are considered and addressed
#204
pes10k
closed
1 year ago
2
Previous
Next