Your third paragraph was enlightening and explained your position reasonably well. I'm not sure I'm convinced, but it seems like an interesting discussion. I feel obliged to downvote you because of the first two…
Hmmph, I see what you're saying, that sounds like it could work. I think the tab flashing is the critical detail, otherwise you would be confused why things are deadlocking.
I'm not following your argument, do you agree that there are resources that cannot be saved in a shared cache?
Then you would need to know the (dynamically generated) contents in advance?
Yes, private doesn't necessarily mean authenticated, it just means shouldn't be saved in a shared cache. For example, "weather_at_your_geoip.js".
I don't know if there are any good Linux GUI debuggers, but gdb is a comprehensive debugger and can do something similar with the skip command. Any gui debugger for Linux is probably a frontend to gdb, so as long as it…
Not a windows user, but the same applies to gdb. What is your proposal? If you're currently debugging a thread, breakpoints are disabled for other threads? That really doesn't seem like what people would expect by…
I think you're forgetting that resources cannot be shared if they're marked private. You cannot get account_statement.js from your shared cache, it has to be unique to you. There is no easy fix to this.
I don't understand the question, it's either cached or not. If it's not cached, then it has to be fetched synchronously for anything depending on its value to work - so it's slow. If it is cached, then the cached value…
I'm not a privacy defeatist, but I am a fingerprinting defeatist. Here's why: I don't think it's realistic for caching and anti-fingerprinting to co-exist, and given those two options users will always pick the former…
Your third paragraph was enlightening and explained your position reasonably well. I'm not sure I'm convinced, but it seems like an interesting discussion. I feel obliged to downvote you because of the first two…
Hmmph, I see what you're saying, that sounds like it could work. I think the tab flashing is the critical detail, otherwise you would be confused why things are deadlocking.
I'm not following your argument, do you agree that there are resources that cannot be saved in a shared cache?
Then you would need to know the (dynamically generated) contents in advance?
Yes, private doesn't necessarily mean authenticated, it just means shouldn't be saved in a shared cache. For example, "weather_at_your_geoip.js".
I don't know if there are any good Linux GUI debuggers, but gdb is a comprehensive debugger and can do something similar with the skip command. Any gui debugger for Linux is probably a frontend to gdb, so as long as it…
Not a windows user, but the same applies to gdb. What is your proposal? If you're currently debugging a thread, breakpoints are disabled for other threads? That really doesn't seem like what people would expect by…
I think you're forgetting that resources cannot be shared if they're marked private. You cannot get account_statement.js from your shared cache, it has to be unique to you. There is no easy fix to this.
I don't understand the question, it's either cached or not. If it's not cached, then it has to be fetched synchronously for anything depending on its value to work - so it's slow. If it is cached, then the cached value…
I'm not a privacy defeatist, but I am a fingerprinting defeatist. Here's why: I don't think it's realistic for caching and anti-fingerprinting to co-exist, and given those two options users will always pick the former…