<?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/"
     xmlns:georss="http://www.georss.org/georss"
     xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
     xmlns:media="http://search.yahoo.com/mrss/">
    <channel>
        <title><![CDATA[Twitter - Law Office of W.F. ''Casey'' Ebsary Jr]]></title>
        <atom:link href="https://www.centrallaw.com/blog/categories/twitter/feed/" rel="self" type="application/rss+xml" />
        <link>https://www.centrallaw.com/blog/categories/twitter/</link>
        <description><![CDATA[Law Office of W.F. ''Casey'' Ebsary Jr's Website]]></description>
        <lastBuildDate>Sun, 19 Jan 2025 15:06:18 GMT</lastBuildDate>
        
        <language>en-us</language>
        
            <item>
                <title><![CDATA[Feds on Twitter | 2702 Short Cut Search Warrant]]></title>
                <link>https://www.centrallaw.com/blog/feds-on-twitter-2702-short-cut-search-warrant/</link>
                <guid isPermaLink="true">https://www.centrallaw.com/blog/feds-on-twitter-2702-short-cut-search-warrant/</guid>
                <dc:creator><![CDATA[Law Office of W.F. ''Casey'' Ebsary Jr]]></dc:creator>
                <pubDate>Mon, 10 Jan 2011 23:02:00 GMT</pubDate>
                
                    <category><![CDATA[18 U.S.C. §§ 2702(c)(4)]]></category>
                
                    <category><![CDATA[Computers]]></category>
                
                    <category><![CDATA[Criminal Defense]]></category>
                
                    <category><![CDATA[Federal Court]]></category>
                
                    <category><![CDATA[Search Warrant]]></category>
                
                    <category><![CDATA[Twitter]]></category>
                
                
                    <category><![CDATA[18 U.S.C. §§ 2702(b)(7)]]></category>
                
                
                
                <description><![CDATA[<p>What About the Feds on Twitter? Most Twitter multimedia is handled by 3d party links. Twitter allows both public or private updates. On Twitter Direct messages are private and the sender can delete these messages. the feds noted that short URLs used to serve malicious links and code. Today we learned the feds will seek&hellip;</p>
]]></description>
                <content:encoded><![CDATA[<div class="wp-block-image">
<figure class="alignright size-full"><img loading="lazy" decoding="async" width="200" height="150" src="/static/2023/12/image-33.jpeg" alt="As not Seen on TV" class="wp-image-2611"/></figure></div>


<h2 class="wp-block-heading" id="h-what-about-the-feds-on-twitter">What About the Feds on Twitter? </h2>



<p>Most Twitter multimedia is handled by 3d party links. Twitter allows both public or private updates. On Twitter Direct messages are private and the sender can delete these messages. the feds noted that short URLs used to serve malicious links and code. Today we learned the feds will seek to recover direct messages and that when Twitter receives the request, they will comply and disclose that such a request has been made.</p>



<p>The Feds frequently use a 2702 request to short cut <strong>Search Warrant</strong> requirements. On the other hand, as of 2010, Yahoo has the following policy on 2702 requests from cybercrime investigators:</p>



<p>“Under <strong>18 U.S.C. §§ 2702(b)(7) and 2702(c)(4)</strong> Yahoo! is permitted, but not required, to voluntarily disclose information, including contents of communications and customer records, to a federal, state, or local governmental entity if Yahoo! believes in good faith that an emergency involving imminent danger of death or serious physical injury to any person requires such disclosure without delay.”</p>
]]></content:encoded>
            </item>
        
    </channel>
</rss>