<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Interesting Supreme Court Case - Geofencing]]></title><description><![CDATA[<p dir="auto"><a href="https://www.scotusblog.com/2026/04/justices-appear-mixed-on-whether-geofence-warrant-violated-the-fourth-amendment-/" target="_blank" rel="noopener noreferrer nofollow ugc">https://www.scotusblog.com/2026/04/justices-appear-mixed-on-whether-geofence-warrant-violated-the-fourth-amendment-/</a></p>
<blockquote>
<p dir="auto">The case began in 2019, when a man armed with a gun entered a federal credit union in the Richmond, Virginia, suburbs. The robber gave the teller a note demanding money and made off with nearly $200,000. When the investigation into the robbery stalled, law enforcement officials served a “geofence warrant” on Google, which directed the tech company to provide location data for cellphone users who were near the bank at the time of the robbery.</p>
</blockquote>
<blockquote>
<p dir="auto">Google provided information to law enforcement officials in three steps. Google first gave law enforcement officials a list of the 19 accounts – but not the names of the accounts’ owners – linked to devices that were within 150 meters of the bank during the 30 minutes before and after the robbery. Based on that list, the government next asked Google for more information about nine accounts that were in the area during a two-hour period. Third and finally, a detective asked for, and received, the names and information for three accounts – one of which was Chatrie’s.</p>
</blockquote>
<blockquote>
<p dir="auto">Based on the location data, law enforcement officials obtained a warrant to search two residences linked to Chatrie, where they found almost $100,000 of the stolen cash, a gun, and demand notes.</p>
</blockquote>
<blockquote>
<p dir="auto">Chatrie was charged with (among other things) bank robbery. He argued that prosecutors should not be allowed to use the evidence obtained as a result of the geofence warrant against him because the warrant violated the Fourth Amendment.</p>
</blockquote>
<p dir="auto">To me, this is a situation that the writers of the US constitution could never ever ever imagined.  So for those who say that the constitution needs to be interpreted as the writers wanted makes no sense.</p>
]]></description><link>https://nodebb.the-new-coffee-room.club/topic/39559/interesting-supreme-court-case-geofencing</link><generator>RSS for Node</generator><lastBuildDate>Thu, 30 Apr 2026 06:43:58 GMT</lastBuildDate><atom:link href="https://nodebb.the-new-coffee-room.club/topic/39559.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 30 Apr 2026 00:31:57 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Interesting Supreme Court Case - Geofencing on Thu, 30 Apr 2026 02:42:05 GMT]]></title><description><![CDATA[<p dir="auto">I was listening to this on NPR yesterday.   Very interesting topic.</p>
]]></description><link>https://nodebb.the-new-coffee-room.club/post/361959</link><guid isPermaLink="true">https://nodebb.the-new-coffee-room.club/post/361959</guid><dc:creator><![CDATA[Mik]]></dc:creator><pubDate>Thu, 30 Apr 2026 02:42:05 GMT</pubDate></item><item><title><![CDATA[Reply to Interesting Supreme Court Case - Geofencing on Thu, 30 Apr 2026 01:07:45 GMT]]></title><description><![CDATA[<p dir="auto">Orin Kerr, probably the most prominent living 4th amendment scholar, was live tweeting the orals the other morning.   As he put it 'for the dozen or so people who are interested'.   lol. I wasn't interested enough to follow the live tweet but I'm interested enough in how the 4th amendment intersects with modern technology to follow Orin Kerr.</p>
]]></description><link>https://nodebb.the-new-coffee-room.club/post/361956</link><guid isPermaLink="true">https://nodebb.the-new-coffee-room.club/post/361956</guid><dc:creator><![CDATA[jon-nyc]]></dc:creator><pubDate>Thu, 30 Apr 2026 01:07:45 GMT</pubDate></item></channel></rss>