Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://universeodon.com/@punissuer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>punissuer</span></a></span> <span class="h-card" translate="no"><a href="https://queer.party/@m04" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>m04</span></a></span> <span class="h-card" translate="no"><a href="https://cyberpunk.lol/@FediPact" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>FediPact</span></a></span> I'm not a lawyer (and I only can refer to ones in my juristiction, which is <a href="https://infosec.space/tags/Germany" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Germany</span></a> (so i.e. <span class="h-card" translate="no"><a href="https://mastodon.social/@wbs_legal" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>wbs_legal</span></a></span> would be the form to get in touch with) so your mileage is different...</p><ul><li>However <a href="https://infosec.space/tags/AFAICT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AFAICT</span></a> having extortive pricing and predatory business models will likely get ripped apart in court (see lawyers like <a href="https://infosec.space/tags/Gravenreuth" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Gravenreuth</span></a> who made their money preyong on alleged spammers and pirates, demanding absurdly high cease-and-decist fees to not press charges) as <a href="https://infosec.space/tags/FRAND" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FRAND</span></a> licensing would likely be mandated.</li></ul><p>Plus a mere HTTP(S) request would likely not hold up in court as an informed contractual agreement customary for that sum.</p><ul><li>Similarly right-extremist tinfoilhats aka. <em>"Reich Citizens"</em> fail get their made-up debts (against legal and natural persons in Germany) from overseas (i.e. <a href="https://infosec.space/tags/USA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>USA</span></a>) enforced.</li></ul><p>By contrast giving them a custom 402 (Payment Required) error or 403 (Forbidden) page demandng them to contract for access may be deemed sifficient if done ASN-wide.</p><ul><li><a href="https://infosec.space/tags/Funfact" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Funfact</span></a>: <a href="https://infosec.space/tags/ESPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ESPN</span></a> did 403 most website visitors from the U.S. if their ISP didn't pay their ransom demands.</li></ul><p>Personally I'm considering to block all <a href="https://infosec.space/tags/GAFAMS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GAFAMS</span></a> and <em>"<a href="https://infosec.space/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a>"</em> companies from my systems...</p><ul><li>Again: <a href="https://infosec.space/tags/NotLegalAdvice" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NotLegalAdvice</span></a>!</li></ul>