@infosec_jcp 🐈🃏 done differently<p><a href="https://infosec.exchange/tags/BreakingNews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BreakingNews</span></a> <a href="https://infosec.exchange/tags/Twitter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Twitter</span></a> <a href="https://infosec.exchange/tags/ClosedWeb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ClosedWeb</span></a> vs. <a href="https://infosec.exchange/tags/OpenWeb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenWeb</span></a> <a href="https://infosec.exchange/tags/OligarchPlatformWatch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OligarchPlatformWatch</span></a></p><p>Holy crap they <a href="https://infosec.exchange/tags/rolledback" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rolledback</span></a> the code change from the June 30th, 2023 to go <a href="https://infosec.exchange/tags/ClosedWeb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ClosedWeb</span></a> behind a login at Twitter.</p><p>Twitter is being dragged kicking and screaming back into the <a href="https://infosec.exchange/tags/OpenWeb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenWeb</span></a> <a href="https://infosec.exchange/tags/XCorp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>XCorp</span></a> <a href="https://infosec.exchange/tags/DelistedTwitter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DelistedTwitter</span></a> <a href="https://infosec.exchange/tags/TWTR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TWTR</span></a> , sorta*.</p><p>Test this on your side with a simple web browser that is NOT logged into Twitter:</p><p>Jack twipp:<br><a href="https://twitter.com/jack/status/1675230141792886784" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="ellipsis">twitter.com/jack/status/167523</span><span class="invisible">0141792886784</span></a></p><p>Test yourself here on your side:</p><p>Google Search for 'Twitter <span class="h-card"><a href="https://infosec.exchange/@jack" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>jack</span></a></span>' link:<br><a href="https://www.google.com/search?q=Twitter+%40jack" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">google.com/search?q=Twitter+%4</span><span class="invisible">0jack</span></a></p><p>* The second result is <span class="h-card"><a href="https://infosec.exchange/@jack" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>jack</span></a></span> tweets, single posting with NO replys! 🧐 Interesting!</p><p>Thank you and everyone who have helped keep pressure on <a href="https://infosec.exchange/tags/Twitter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Twitter</span></a> for reopening this to the <a href="https://infosec.exchange/tags/OpenWeb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenWeb</span></a>, even if this is a SINGLE TWIPP, without replys shown now as 'the new normal' at partially closed <a href="https://infosec.exchange/tags/XCorp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>XCorp</span></a> / <a href="https://infosec.exchange/tags/twitter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>twitter</span></a> </p><p>The loss for <a href="https://infosec.exchange/tags/MajorNews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MajorNews</span></a> breaking here is barely, marginally, useful as a one sided medium behind a login, without the replys shown also, btw.</p>