lurker456

Yes, it's been part of the regulations in the EU, even before GDPR. Being forced to disclose in a timely manner ensures it can't be swept under the rug because they squint at the logs just right.

The QA team got folded into the main org a while ago. I'd be surprised if the person today in charge of the full test coverage has anywhere near the resources or weight to make an impact.

If your password is leaked, then you can still reset it. If your fingerprint signature leaks, you're out of options.

HANA in memory database that can serve both OLTP and OLAP workloads with sub second response times. The cost of the server is dwarfed by the licence cost.

It may be a GDPR violation (insufficient consent), we'll need a ruling to be certain. It may also be an antitrust violation (chrome is close to 60% market share in the EU).

To make this worse, in all likelihood the scalper was fake and it was not sold out. Ticketmaster will routinely pretend a venue is sold out when it's not and they're not shy of impersonating a third party either.

You should, because anyone that can compromise your phone will be able to get into your email.

From there it's a small step to reset passwords (SMS 2FA won't help here, as they also have your phone) to all online services you signed up for with that email.

The cynic in me thinks this is in anticipation of GDPR related challenges. Users that accepted a TOS are easier to track (at least, it's easier to mount a legal argument that some tracking and profile linking is ok) compared to users that never accepted anything at all.

next up: push for new standards that favor chrome over other browsers.

That would make some key stakeholders (in the military and govt) quite unhappy, leading to difficulties staying in control, leading to prison or worse for the top. It's gotten to the point that they need to cling to power.

For the same reasons the european powers were unable to prevent IP theft by the US earlier in history - not enough reach and power.

They could, but they don't. Why is a bit of a mystery because in the long run this is destructive and it can't be that profitable.

I don't see any mention of security or legal concerns. Not all bugs can be identified by exceptions, exception frequency is not an indication of their impact, and in some cases stability is less important then correctness. Using bugs per session as the (only?) metric is a horrible way of doing product management.

That's only if UK's debt is in pounds and without provisions for currency fluctuations.

"The Miami-Dade Office of Consumer Protection said that as of July 1, 2017 it no longer “regulates complaints against transportation services such as Uber or Lyft,” and that any complaints should be addressed to the Florida Department of Agriculture and Consumer Services.

The state consumer affairs department said it was not aware of the change and declined an interview request."

That's to access AMT. AMT is a module running on top of ME and is disabled by default.

Does this affect ME or ME with AMT enabled ? The article talks about ME but it's AMT that runs the http server.

Join a SAP customer or SAP integrator. At a customer you'll normally get sent on several multi week training sessions. At integrators you'll get some PDF's and be thrown in the deep immediately. As a junior, the pay is bad, so be sure to move on quickly, don't stick around at the same position (this is the norm). After 5 years or so you should have multiple certifications, a few war stories to tell and the contacts to become independent.

The IT part of SAP is quite small and easy to grok if you have CS training, what you will learn is mostly SAP specific terminology, the details of the business process(es) you're working with, learning to work with outdated software packages and learning to work around people in an IT role who have no interest (or skill) in IT.

Anything of value sent via snail mail gets seized. CC and bank accounts denominated in USD can't be used. There is a black market where people pay with physical USD and crypto.

Interesting idea. How will this handle legal take-down requests ? Backed by DMCA, GDPR, and so on.

How would you send fiat to a family member stuck in Venezuela ? I agree that the value of cryptocurrency is hugely inflated, but it's not zero either. It's a good fit in some scenarios.

it absolutely is a huge issue, with fines that bite. Google had to settle for +500M after serving ads for fake medicines in the US. I wouldn't be surprised if the primary aim here was to get a bargaining chip for their negotiations for their health care JV (a much bigger market)

I bet in a couple of years the next CIO will discover that the TCO is quite a bit higher then expected.

I live in a country with free healthcare and education (well, nationalized) and we have much stronger protections against predatory lending. The problem with US student loans is that they can't be defaulted on.

Agreed, the US is more lax. I was responding to the parent comment "I have submitted this because it is frequent to see on HN claims that IP addresses are personal data under GDPR"

GDPR is more recent and supersedes this.

Imagine a delayed killswitch in Intel's ME and AMD's PSP.

Humanity may survive, but our civilization likely won't. It relies on cheap energy and a stable climate, both are under threat. Good luck manufacturing a MRI machine when you're struggling to grow enough food for next year.

Yes, to offer that functionality it would need a cookie. No, the website doesn't need to correlate that login and all activity related to it to everything else you ever did on the internet to build up a profile about you. It is technically feasible (even easier) to offer the first ("remember me on this one site") without doing the second ("track me across all sites").

13. It's a market for lemons [1]. Schneier wrote about it in the context of security related software, but it equally applies to bespoke stuff like CRM or SCM.

[1] https://www.schneier.com/blog/archives/2007/04/a_security_ma...

perhaps we need an RFC that defines this type of approach (pages "secured" behind easily guessable urls) as public information.