This is about a serious and willful GDPR contravention as you can get. I hope they have good lawyers because they are gonna be hauled over the coals by multiple countries' data commissioners.
If Triplebyte doesn't even do IP filtering for signups, they are servicing EU citizens. Actually I told them that I don't have US VISA, so the ,,local golf course we site'' case doesn't apply.
Unfortunately, the real fines are nowhere near the theoretically possible ones.
This is egregious enough that it could have actually resulted in a fine as opposed to a "please don't do that", but realistically, I doubt the fine would get near 100k.
I’m curious how that’ll work in practice. The sovereignty of a nation is a big thing. The US isn’t going to just prosecute TripleByte because Europe said they should. Sure, if @ammon visits the EU, he could be arrested, but a nation’s laws (generally) don’t extend past their border.
It’s a total pipe dream. I don’t know what fantasy land people are living in where they think the EU is going to successfully collect a dollar in fines from some random small company elsewhere in the world, no matter how messed up their privacy practices are.
First of all, this isn’t popular with the EU crowd here, but there’s no method of enforcement for GDPR for American companies without a presence in Europe. Good luck trying to collect a fine from some tiny business in the US
Second, you really think GDPR is going to be applied to some tiny American startup because they said they might do something and then didn’t?
Third, my understanding is that if you don’t target EU customers, GDPR doesn’t apply. It’s not enough that an EU customer happens to wander into your store. You have to have some accommodation targeting the EU (like translated pages, international shipping, different currencies, etc)
Your company is service provider based outside the EU. It provides services to customers outside the EU. Its clients can use its services when they travel to other countries, including within the EU. Provided your company doesn't specifically target its services at individuals in the EU, it is not subject to the rules of the GDPR.
The thing I like about hooks is that components can be truly modular in terms of both behaviour and state. They can so be relatively easy to reason about in isolation and therefore it's easier to reuse them with less plumbing needed.
For instance a simple custom hook use_graphql_list(url,query) can encapsulate the entirety of fetching json via a graphql query keeping an array up to date and in sync and present data in a format that is easy to use in a list component.
For instance in rust:
let graphql_query = "{countries {name currency emoji}}";
let graphql_url = "https://countries.trevorblades.com/";
let container_name = "countries";
let (list, graphql_control) =
use_graphql_list::<Country>(
graphql_query,
graphql_url,
container_name);
Well it is still mostly JS. Claiming JS is crap (often stated as "beyond repair") and TS is good just because of (arguably) light addition shows some serious cognitive dissonance. But nevermind:
> The fact that it can be transpiled to Javascript is irrelevant
> FYI you are just showing how awful are communities around "legitimately good" languages.
Just to let you know Rust's community is pretty cool and not awful at all. For instance the Rust Survey 2017 reports that 98.7% of respondents feel welcome within the Rust Community.
Furthermore according to the Stackoverflow 2017 survey, Rust is the "most loved" language.
This is about a serious and willful GDPR contravention as you can get. I hope they have good lawyers because they are gonna be hauled over the coals by multiple countries' data commissioners.
Wow just wow.