HackerTrans
TopNewTrendsCommentsPastAskShowJobs

oreoftw

no profile record

comments

oreoftw
·3 ay önce·discuss
Maybe it’s feels important/necessary as it can give a feeling of control.

Things are uncertain(were they ever certain?), every day there is another armageddon prophecy screaming at you from social media and newspapers.

So one can try to hedge, squeeze more out of oneself to make sure he did all he could.
oreoftw
·5 ay önce·discuss
Snitch is a firewall, not sure about Lulu.
oreoftw
·geçen yıl·discuss
most likely he was referring the fact that you need plenty of GPU-fast memory to keep the model, and GPU cards have it.
oreoftw
·2 yıl önce·discuss
How would you design it to support mentioned use cases?
oreoftw
·2 yıl önce·discuss
Not an Irish citizen or a resident. Everyone residing in the EU(including EEA) enjoys GDPR protection.

I don't know how stringent the geo check for claims is, but as soon as you become an EEA resident you can invoke GDPR.

I would recommend to ask Google’s DPO anyway.
oreoftw
·2 yıl önce·discuss
Invoking the right to retrieve and correct information helped me to get Google’s attention to my case and unban me.
oreoftw
·2 yıl önce·discuss
Find google data protection officer email. State your request to get the data with a mention of escalation to the Irish Data Protection Officer if no action is taken within a reasonable timeframe.

This has magically unbanned me in less than two days. In contrast to two months of tweeting, emailing support, nagging my google eng friends and even support folks via linkedin.
oreoftw
·2 yıl önce·discuss
The author should consider himself lucky. Just one google service has been suspended. I got my account banned for no reason and lost access to more than 10 years worth of emails, documents, single sign ons to different apps, etc.

Only invoking GDPR and the ownership of a domain name allowed me to regain access and restore email service. Without GDPR I would've got nothing at all.
oreoftw
·2 yıl önce·discuss
Exposing bare GraphQL the right way can be challenging, totally agree with author on that. Using it on a small project also can be an overkill.

But at the same time it doesn’t have to be that bad. I don’t have this array of issues because I do: - query whitelisting for performance and security, - data loading to avoid n+1, authentication with whatever works(session cookies, tokens), - permission check based on the auth context in a resolver.

It works decently for us, allowing to stay away from getting into ESB. Yet have some shared domain, type safety, and easy integration of legacy and new systems/services.

I would say a bigger issue for us was to keep it all nicely organized / designed in terms of types and api contracts. But that’s manageable.