More focussed on developer UX than telemetry, `Make VS Code Awesome` [0] shares a lot of configs to clean up the UI/nags/prompts. I'm not affiliated but have bought it and found it significantly improved my days in Code.
I'm implementing some faceting in a project I'm working on. I have some nested `jsonb` columns which include categorical variables (to quote this article).
The table is only 5 million rows and isn't likely to grow significantly, but it is not very wide.
The performance is okay and I was about to experiment with flattening out the table (putting all categorical vars into their own columns) and indexing that way vs. indexing JSONb paths.
I'm not super familiar with the postgres internals to know if this is better or worse so wondering if anyone could share any similar experience?!
Non-starter because you don't want to migrate the images into Cloudflare? I.e. you want the transformation/caching of some non-CDN images via Cloudflare?
Asking as this could look very attractive (£ wise) for a project with images stored in Uploadcare where it would be feasible for us to do the source-image migration.
EmpowerRD is a fast-growing scale-up based in London, UK. Our vision is to assist our clients to unlock all of the funding that rewards innovation globally. We do this by combining expert knowledge and advanced technology to take the complexity out of claiming for funding that is available. Our current focus is on helping companies within the UK unlock some of the £5Bn of funds available annually for companies that invest in research and development.
As we grow we're looking for a full stack developer versed in Ruby.
Skills and experience we need:
Ruby (1+ years), Ruby on Rails, Modern frontend framework (1 year, React/Vue/Alpine), SQL
Skills and experience that would be a bonus:
AWS (EC2, RDS, VPC), Docker, Experience in a SaaS business
I recently purchased something from the official UK Nintendo Store [1]. I did not opt-in, and was not asked to opt-in, to marketing emails.
Several days after purchase I received a marketing email with an Unsubscribe link.
I submitted a GDPR enquiry and after a few weeks I get:
Having investigated this matter fully, we can see that you were opted in as a result of a small technical difficulty which we are now fixing. We have taken action to set your marketing permissions to "no" as requested.
I think we're so far past the GDPR "start date" that there's an apathy to it from companies and they're pushing the limits again. How Nintendo can have such a formalised GDPR enquiry process but such sloppy controls is beyond me. I will formally complain to ICO (UK data regulator) but I doubt it'll effect much.
I have a different issue myself. Despite having opted-in to marketing e-mails I never have obtained a marketing e-mail from Nintendo since then. Nintendo's website shows that I have agreed to "receive promotional e-mails". At one point I did in fact unsubscribe, but later I resubscribed. I think that there is a bug that sometimes causes promotional e-mail setting to not be updated in newsletter database (maybe the server was down when I tried to change the setting, and Nintendo Account website quietly ignored the error).
Main bulk mailing companies (iContact, Sendgrid) will make a blocklist for you of anyone who has unsubscribed - and if you're not careful about it once on you'll NEVER get off - and it prevents send to those addresses even if you later re-add them to your list.
I complained about tv2.dk (I used to be a customer) sending me a e-mail after I deleted my user and told them not the send me e-mail. This was a really bad experience where their support attempted to make me login to the site which I refused to do since I removed my user previously.
Then I sent them a GDPR request to remove all my info and complained to the Danish Data Protection Agency.
I stopped receiving e-mail but got nowhere with my complaint. The agency wrote me that they didn't want to pursue this.
Based on this ..
I don't think that anyone is taking GDPR seriously and no one is trying to defend the small people (me!).
Sad, I get that it might be to small a case to actually deal with, but most cases will be. Only in aggregate will complaints as your ever get anywhere.
On a positive note, I have noticed that deleting accounts have become much easier after the introduction of the GDPR, and more and more I see tracking opt-in/out forms where opt-out is just as easy as opt-in. So something is working.
This is actually a really good idea. A Trust Pilot type of site which is owned by a non profit or some such with no monetary interest in contrast to TP where GDPR issues toward companies can be created, shared on social media and executed automatically when a number of people agreed to complain about the same issue.
Having seen how other companies make the sausage, I can take a guess.
To Nintendo, marketing is not a "core" business function, so when the company was sorting out GDPR, no one invited them to the room and they didn't ask to be invited. When companies think about "what data do I have" they tend to get tunnel vision to their main business operations. I bet Nintendo has robust processes for their online gaming services. No one ever seems to think about the twenty dozen Google Analytics accounts they're all running, and a good fraction of them don't even think about their CRM systems.
In the UK, there's another law called the PECR in place that may supersede the GDPR in this case.
I've had multiple merchants get back to me after such a complaint claiming that under the PECR they're allowed to send further marketing solicitations following a purchase.
I haven't pushed it further so no idea if this is actually legal or if the GDPR supersedes it.
The Privacy and Electronic Communications Regulations (PECR)[1] do not supersede GDPR as such, they sit alongside it.
Section 22 is the relevant section they are hoping to rely on, specifically section 22(3) which allows them to:
----------
(3) A person may send or instigate the sending of electronic mail for the purposes of direct marketing where—
(a) that person has obtained the contact details of the recipient of that electronic mail in the course of the sale or negotiations for the sale of a product or service to that recipient;
(b) the direct marketing is in respect of that person’s similar products and services only; and
(c) the recipient has been given a simple means of refusing (free of charge except for the costs of the transmission of the refusal) the use of his contact details for the purposes of such direct marketing, at the time that the details were initially collected, and, where he did not initially refuse the use of the details, at the time of each subsequent communication.
----------
So in this case, they are obliged to let you withdraw your consent every time they email you. It is not a blank cheque for them to keep emailing you simply because you've purchased something; it is consent-based and therefore uses the same consent processes as the GDPR.
> How Nintendo can have such a formalised GDPR enquiry process but such sloppy controls is beyond me.
Probably because only 1% of 1% of their customers even bother to notice. I'd be willing to bet money that you were the first person to discover this implementation error.
Yes, part of the Brexit agreement was the UK "domesticating" some parts of EU law by passing them as UK legislation. There is now a law called UK-GDPR, which is literally a copy-paste of GDPR, with names of EU institutions find-and-replaced with their UK equivalents.
There are still some operational differences, around the fact that the UK regulators will not participate the cooperation mechanisms that the other regulators will. This ends up mattering for businesses: a significant aspect of GDPR was that a company only ever had to deal with one regulator, but now they need to interface with one for the EU and a second for the UK.
I believe GDPR is supposed to be implemented in every participating country's legislation, so the GDPR was implemented in UK law and this remains the case even after Brexit. Nothing prevents them from amending that law and repealing the GDPR's effects on it though.
EmpowerRD is a fast-growing startup based in London, UK. Our vision is to assist our clients to unlock all of the funding that rewards innovation globally. We do this by combining expert knowledge and advanced technology to take the complexity out of claiming for funding that is available. Our current focus is on helping companies within the UK unlock some of the £5Bn of funds available annually for companies that invest in research and development.
As we grow we're looking for a full stack developer - versed in Ruby - who can support both internal and external development.
Skills and experience we need:
Ruby (1+ years), Ruby on Rails, Modern frontend framework (1 year, React/Vue/Alpine), SQL
Skills and experience that would be a bonus:
AWS (EC2, RDS, VPC), Docker, Experience in a SaaS business
We are looking for a Ruby full stack developer to help support our journey from startup to scale up.
EmpowerRD is a fast-growing startup based in London, UK. Our vision is to assist our clients to unlock all of the funding that rewards innovation globally. We do this by combining expert knowledge and advanced technology to take the complexity out of claiming for funding that is available. Our current focus is on helping companies within the UK unlock some of the £5Bn of funds available annually for companies that invest in research and development.
As we grow we're looking for a full stack developer well versed in Ruby.
Skills and experience we need:
Ruby (3+ years), Ruby on Rails, Git (gitflow), front-end JavaScript (jQuery/Alpine/vanilla) and CSS, SQL (Postgres)
Unless I'm misunderstanding something, they are going to have an immense SLA claim issue. 99.9% SLA on Workspace services, so any business paying for Google for Business (now known as Workspace) is going to have a credit claim (assuming the outage is longer than 43m 49s which feels like it will be).
Edit: As I comment it looks like things are coming back! Timing or what...
I’m aware Mac OS has some isolation/sandboxes but without running codex via docker I wouldn’t be running codex.
(Appreciate there are still risks)