<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>samesite &#8211; EFR Technology Group</title>
	<atom:link href="https://www.efrtechgroup.com/category/samesite/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.efrtechgroup.com</link>
	<description>We maintain technology so you don't have to!</description>
	<lastBuildDate>Wed, 15 Jul 2020 08:25:11 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://www.efrtechgroup.com/wp-content/uploads/2019/02/cropped-EFRTG-color-2-32x32.jpg</url>
	<title>samesite &#8211; EFR Technology Group</title>
	<link>https://www.efrtechgroup.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Google Chrome update limits cookie tracking and blocks annoying notifications</title>
		<link>https://www.efrtechgroup.com/tech/google-chrome-update-limits-cookie-tracking-and-blocks-annoying-notifications/</link>
		
		<dc:creator><![CDATA[Randall]]></dc:creator>
		<pubDate>Wed, 15 Jul 2020 08:25:11 +0000</pubDate>
				<category><![CDATA[chrome]]></category>
		<category><![CDATA[chrome 84]]></category>
		<category><![CDATA[gear]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[samesite]]></category>
		<category><![CDATA[Tech]]></category>
		<guid isPermaLink="false">https://www.efrtechgroup.com/google-chrome-update-limits-cookie-tracking-and-blocks-annoying-notifications/</guid>

					<description><![CDATA[[ad_1] Google’s Chrome 84 is now available for all desktop users after a delay in releases due to the coronavirus pandemic. The version resumes the SameSite cookie changes Google started implementing with Chrome 80. If you’ll recall, the tech giant had to roll the feature back a couple of months after it was first introduced [&#8230;]]]></description>
										<content:encoded><![CDATA[<p> [ad_1]<br />
</p>
<div>
<p>Google’s Chrome 84 is <a href="https://chromereleases.googleblog.com/2020/07/stable-channel-update-for-desktop.html" target="_blank" rel="noopener noreferrer">now available</a> for all desktop users after a delay in releases due to the coronavirus pandemic. The version <a href="https://venturebeat.com/2020/07/14/google-chrome-84/" target="_blank" rel="noopener noreferrer">resumes</a> the SameSite cookie changes Google started <a href="https://www.engadget.com/2020-02-04-google-chrome-80-rollout.html">implementing</a> with Chrome 80. If you’ll recall, the tech giant had to <a href="https://www.engadget.com/2020-04-03-google-rolls-back-chrome-samesite.html">roll the feature back</a> a couple of months after it was first introduced in an effort to ensure that it doesn’t cause online services and portals to stop working in the midst of coronavirus—related lockdowns.</p>
<p>The changes require developers to set their cookies&#8217; SameSite attribute or Google will automatically switch their setting to a more secure option, which is something that can potentially break websites. Now that enough time has passed, Google has likely decided that it was time to enforce the SameSite attribute changes to prevent security issues caused by cookie vulnerabilities.</p>
</p></div>
<p>[ad_2]<br />
<br /><a href="https://www.engadget.com/chrome-84-resumes-samesite-cookie-changes-073511129.html">Source link </a></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Google rolls back Chrome feature that blocks cross-site tracking</title>
		<link>https://www.efrtechgroup.com/tech/google-rolls-back-chrome-feature-that-blocks-cross-site-tracking/</link>
		
		<dc:creator><![CDATA[Randall]]></dc:creator>
		<pubDate>Sat, 04 Apr 2020 00:16:00 +0000</pubDate>
				<category><![CDATA[chrome]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Internet]]></category>
		<category><![CDATA[samesite]]></category>
		<category><![CDATA[Tech]]></category>
		<guid isPermaLink="false">https://www.efrtechgroup.com/google-rolls-back-chrome-feature-that-blocks-cross-site-tracking/</guid>

					<description><![CDATA[[ad_1] The feature requires developers to indicate their website cookies&#8217; SameSite attribute, which dictates how those small files a browser saves should behave. If they don&#8217;t, then Google will automatically switch that attribute to a secure option that prevents cookies from tracking users across websites. However, the change can break products and services that need [&#8230;]]]></description>
										<content:encoded><![CDATA[<p> [ad_1]<br />
</p>
<div>
<p>The feature requires developers to indicate their website cookies&#8217; SameSite attribute, which dictates how those small files a browser saves should behave. If they don&#8217;t, then Google will automatically switch that attribute to a secure option that prevents cookies from tracking users across websites. However, the change can break products and services that need cross-site tracking to work.</p>
<p>Google says most developers were prepared for the change &#8212; it was first revealed in mid-2019, after all. But the company still decided to roll back its enforcement, because it wants to ensure that websites providing essential services, such as banking, online groceries, government services and healthcare, continue to be accessible in these difficult times. The tech giant will start the rollback today and promises to announce when it plans to resume its enforcement on the <a href="https://www.chromium.org/updates/same-site" target="_blank" rel="noopener noreferrer">SameSite updates</a> page.</p>
</p></div>
<p>[ad_2]<br />
<br /><a href="https://www.engadget.com/2020-04-03-google-rolls-back-chrome-samesite.html">Source link </a></p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
