570 karma · joined November 23, 2019
35Mbps down (steady)
3Mbps up (decays quickly suggesting shown upload is "boost" / "burst" speeds or possibly throttled heavily in some other manner)
- Company doesn't follow security practices and leaks data
- Feds get notified if it's a big enough breach. Btw, this is from the good will of the company
- Data Brokers...erm, Credit Agencies, then monitor for the data...i guess the insurance company sent it to them too, so they know what to look for?
- I don't know who pays for this (originating company, tax payers, etc)
- Credit Agencies now get to monitor you. Watch what you do under the guise of protecting you. While still building your credit score.
- Hopefully the info leaked and being used is accurate. If not, the Credit Agency has no obligation to fix it unless you say so and even then it can take a long time to remedy.
This just seems fucked.
Yeah, ok. They literally sent victims to a DATA BROKER to "protect" them. The very same people who would buy up that leaked data that came the "hack." What fucking world do we live in??
Edit: ...
Perhaps faster means fewer instructions in this instance? Considering number of instructions is what has been discussed.
(IANAL, these are my admittedly simple and probably naïve assumptions)
Edit: words
Any company can set cap limits and wait limits. "Sorry, we're booked out 1 month, check back soon." (Don't major restaurants do this?) More people want to visit than cap or time allows, open more locations. &c.
> I’m not sure this is a bad thing and might actually make the trip to Disney all that more special.
Exclusivity makes for an air of "special"-ness, absolutely, but the line of division doesn't necessarily have to be a monetary one. (I have a complaint with no answer, but we're a smart group, lets find one).
Edit: ninjas and typos
> 4) Apple incurred damages […] from expenses related to mitigating the hacking of their users.
This sounds like no one should be a security researcher for they risk paying companies to implement the security the company should have implemented anyway. Put another way, that also sounds like the corporate open source push, "We love open source because we don't have to support it, the community will!"
"4)" says the community will pay for/support security, just wait for the hack and make 'em clean it up. Mitigation costs shouldn't be a recoverable damage, they should be doubled and paid out to the victims...maybe that'll incentivise better security over dollar dollar bills y'all.
This all maybe moot because this was a B2B action and I'm thinking from a non-monied, single user/security researcher perspective. What if the company was a non-profit security research group? Perhaps this is what the 90day grace periods are for when dealing with responsible disclosure?
Anyhow, my ignorance must be showing at this point.