One of the requirements of the European Union’s GDPR regulation is that site users need to first opt-into non-essential cookies and other trackers. They then must be offered the ability to opt-out at any time.
GDPR was not and is not Cookie Banner legislation. One cannot be too clear on that. It is not.
It clarified already existing Cookie Banner legislation that everyone should have been following already for EU site users.
Security headers are technical. Most of us have likely never heard of them. They are the instructions we as site owners give users’ browsers to secure content from our website. It is the job of modern web browsers to be secure. Browsers allow site authors a good deal of freedom though in how secure their content is. They are as secure in some places as we tell them to be and not more than that.
It is surprising and somewhat shocking to me that anyone today has a website or blog that is not HTTPS. Changing over is easy. It is quick. It is free. It helps with your site SEO. That is, search engines rank sites with HTTPS higher than those without. That over time means more readers.
The General Data Protection Regulation (GDPR) regulations were written in 2016. They went into effect in 2018. Here we are in 2019, and most genealogy bloggers are not following it. Really. None of us. Not Debbie Kennett, not Judy Russell, not Blaine Bettinger, not Leah Larkin, not Roberta Estes, and not I.
Family Tree DNA sent the following information out to project administrators on the 15th. One of the most important changes that is being folded in with the GDPR updates is that new project members will have to change the default setting after they join a project to allow the project administrator to impersonate into their kit. This is important for doing things like downloading the CSV file of BIG Y500 STR results.
Family Tree DNA sent this message out to project administrators and co-administrators on April 9th. Once they finish their site updates, I will go over them as tutorials. I deeply believe that it is important for those who take part in group projects to understand both what project administrators can and cannot see as part of project access to their accounts.