Comments As Well As Cookie Filters - October 2014
Friday, November 1, 2019
Edit
The new, mandatory CAPTCHA form, for weblog readers wishing to comment anonymously, has been inwards service for but nether a week.
We're seeing a diversity of problems, reported inwards Blogger Help Forum: Get Help amongst an Issue, past times weblog owners together with readers alike.
Long ago, for blogs amongst readers who were non actually comfortable amongst maintaining safety on their computers, nosotros would recommend changing comment class placement.
The sum page (or the slightly less preferable popup window) comment class was to a greater extent than usable, amongst readers who exercise non know how to properly hold cookie together with script filters. With recent changes inwards Blogger together with Google, all Blogger comment forms are at ane time vulnerable to inappropriate filters.
The Google "One account" login, at "google.com", is at ane time used past times many weblog owners together with readers - instead of the Blogger native login, at "blogger.com". When the "blogger.com" login was used, cookies created nether "blogger.com" were non as vulnerable, to cookie filters.
Whether used nether "blogspot.com", or whatever province code alias or custom domain is inwards role (for the embedded comment form) - or nether "blogger.com" (for the sum page together with popup window comment forms) - login cookies created nether "google.com" (by the Google "One account" login) are vulnerable to "third party" cookie filters.
Blogs published to custom domains are becoming to a greater extent than together with to a greater extent than popular. All blogs published to custom domains, which role the embedded comment form, are vulnerable to "third party" cookie filters.
Blogs referenced nether country code aliasing are becoming to a greater extent than normal. All blogs dependent area to province code alias redirection are vulnerable to "third party" cookie filters.
The new, mandatory commenting CAPTCHA form needs to access the Blogger / Google login cookie - together with hence weblog readers, who are logged inwards to Blogger / Google, volition non survive dependent area to the CAPTCHA. The embedded, sum page, together with popup window forms are every bit vulnerable to "third party" cookie filters, given the inwards a higher house discussed issues.
Thanks to the Google "One account" login, as Blogger is made a trend of life to to a greater extent than of a reader population who bring no involvement inwards maintaining safety on their computer, these issues volition choke more problematic.
>> Top
We're seeing a diversity of problems, reported inwards Blogger Help Forum: Get Help amongst an Issue, past times weblog owners together with readers alike.
Long ago, for blogs amongst readers who were non actually comfortable amongst maintaining safety on their computers, nosotros would recommend changing comment class placement.
The sum page (or the slightly less preferable popup window) comment class was to a greater extent than usable, amongst readers who exercise non know how to properly hold cookie together with script filters. With recent changes inwards Blogger together with Google, all Blogger comment forms are at ane time vulnerable to inappropriate filters.
- Use of the Google "One account" login creates login cookies nether "google.com" - non "blogger.com".
- Publishing blogs to custom domains - non "blogspot.com" - makes cookie access "third party".
- Referencing blogs from countries dependent area to country code aliasing - non as "blogspot.com" - makes cookie access "third party".
- The new, mandatory commenting CAPTCHA form, business office of all Blogger comment class placement options, makes cookie access real important.
The Google "One account" login, at "google.com", is at ane time used past times many weblog owners together with readers - instead of the Blogger native login, at "blogger.com". When the "blogger.com" login was used, cookies created nether "blogger.com" were non as vulnerable, to cookie filters.
Whether used nether "blogspot.com", or whatever province code alias or custom domain is inwards role (for the embedded comment form) - or nether "blogger.com" (for the sum page together with popup window comment forms) - login cookies created nether "google.com" (by the Google "One account" login) are vulnerable to "third party" cookie filters.
Blogs published to custom domains are becoming to a greater extent than together with to a greater extent than popular. All blogs published to custom domains, which role the embedded comment form, are vulnerable to "third party" cookie filters.
Blogs referenced nether country code aliasing are becoming to a greater extent than normal. All blogs dependent area to province code alias redirection are vulnerable to "third party" cookie filters.
The new, mandatory commenting CAPTCHA form needs to access the Blogger / Google login cookie - together with hence weblog readers, who are logged inwards to Blogger / Google, volition non survive dependent area to the CAPTCHA. The embedded, sum page, together with popup window forms are every bit vulnerable to "third party" cookie filters, given the inwards a higher house discussed issues.
Thanks to the Google "One account" login, as Blogger is made a trend of life to to a greater extent than of a reader population who bring no involvement inwards maintaining safety on their computer, these issues volition choke more problematic.
>> Top