Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@LibreKitsune" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>LibreKitsune</span></a></span> I still consider this a <em>hostile act</em> and a blatant violation of their previous <a href="https://infosec.space/tags/settlement" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>settlement</span></a> that forced them into <a href="https://infosec.space/tags/publishing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>publishing</span></a> said <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a> <a href="https://infosec.space/tags/ranges" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ranges</span></a>... </p><ul><li>In fact had they not actively worked against that previously and it only raised my attention when I saw errors re: said ranges.</li></ul><p>I'm considering to build a <a href="https://infosec.space/tags/workaround" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>workaround</span></a> on <a href="https://infosec.space/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GitHub</span></a> to just use a <a href="https://infosec.space/tags/cookie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cookie</span></a> and some <a href="https://infosec.space/tags/compute" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>compute</span></a> to do it, but if I had cash to spare I'd sue them into removing <a href="https://infosec.space/tags/ClownFlare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ClownFlare</span></a> and allowing me to scrape the list directly... </p><ul><li>I'm very close to just sending them an <a href="https://infosec.space/tags/invoice" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>invoice</span></a> for the personnel hours wasted on that bs and billing them regularly for the expense of manually checking the difference between those (@ minimum of 60:15 billable minutes)...</li></ul><p>Otherwise I do expect regulators to actually go after <a href="https://infosec.space/tags/OpenAI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenAI</span></a> and force them to undo the <a href="https://infosec.space/tags/Cloudflare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cloudflare</span></a>-based <a href="https://infosec.space/tags/Enshittification" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Enshittification</span></a>, since it's neither feasible nor reasonable to claim <em>"<a href="https://infosec.space/tags/DDoS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DDoS</span></a>-<a href="https://infosec.space/tags/Protection" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Protection</span></a>"</em> for a 48 Bytes (!!!) file...</p><ul><li>Every <a href="https://infosec.space/tags/WAF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WAF</span></a> / <a href="https://infosec.space/tags/WebApplicationFirewall" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WebApplicationFirewall</span></a> I know would not get triggered even if I were to query it once per hour (which I now do just to annoy them or rather ClownFlare!...</li></ul>