Shakedown Social

0 posts0 participants0 posts today

Kevin Karhan :verified:<a href="https://existiert.ch/@leberschnitzel" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@leberschnitzel</a> shure. Take your time. <ul><li>Usually the most effective solutions are further away from said webserver.</li></ul>Espechally since <a href="https://infosec.space/tags/JavaScript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JavaScript</a> gets universally blocked by users of <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@torproject</a> / <a href="https://infosec.space/tags/TorBrowser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TorBrowser</a> like myself simply because every single piece of <a href="https://infosec.space/tags/JS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JS</a> I came across was not "technically necessary" if not outright <a href="https://infosec.space/tags/malware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#malware</a> designed to do <a href="https://infosec.space/tags/Cryptojacking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Cryptojacking</a>, <a href="https://infosec.space/tags/BrowserFingerprinting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BrowserFingerprinting</a> and/or steal logins.

Kevin Karhan :verified:<a href="https://mastodon.ie/@jherazob" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jherazob</a> <a href="https://existiert.ch/@leberschnitzel" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@leberschnitzel</a> Shure: <a href="https://en.wikipedia.org/wiki/Dread_(forum)" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://en.wikipedia.org/wiki/Dread_(forum)</a>Another Forum that has implemented good Anti-DDoS seems to be <a href="https://en.wikipedia.org/wiki/BreachForums" rel="nofollow noopener noreferrer" target="_blank">BreachForums</a>One does have to admit they are able to do <a href="https://infosec.space/tags/DDoS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DDoS</a>-<a href="https://infosec.space/tags/protection" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#protection</a> w/o value-removing middlemen, <a href="https://infosec.space/tags/JavaScript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JavaScript</a> and <a href="https://infosec.space/tags/BrowserFingerprinting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BrowserFingerprinting</a>…

Kevin Karhan :verified:<a href="https://indieweb.social/@jbz" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jbz</a> this is why using <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@torproject</a> / <a href="https://infosec.space/tags/TorBrowser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TorBrowser</a> is my main recommendation.<ul><li>Cuz they'll inherently keep <a href="https://infosec.space/tags/ads" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ads</a> out of it if not for the sake of <a href="https://infosec.space/tags/accessibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#accessibility</a> and saving <a href="https://infosec.space/tags/traffic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#traffic</a> on <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tor</a>, then it's to enshure <a href="https://infosec.space/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#privacy</a> of users and twart <a href="https://infosec.space/tags/BrowserFingerprinting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BrowserFingerprinting</a> tactics!</li></ul>

Christian Pietsch 🍑<a href="https://sociale.network/@oblomov" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@oblomov</a> My initial gut reaction was the same. And I still think it may be wise to opt out of this experiment until it is better understood.But what if this initiative could indeed serve as a privacy-preserving replacement for <a href="https://suma-ev.social/tags/tracking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tracking</a>? It looks better than all the terrible ideas Google came up with to replace cookies (<a href="https://suma-ev.social/tags/FLoC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FLoC</a> <a href="https://suma-ev.social/tags/PrivacySandbox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PrivacySandbox</a> <a href="https://suma-ev.social/tags/TopicsAPI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TopicsAPI</a>) let alone <a href="https://suma-ev.social/tags/browserFingerprinting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#browserFingerprinting</a>.Here is my take on Mozilla's <a href="https://suma-ev.social/tags/privacyPreservingAttribution" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#privacyPreservingAttribution</a> aka <a href="https://suma-ev.social/tags/privateAttribution" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#privateAttribution</a>: <a href="https://suma-ev.social/@christian/112761712837712799" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://suma-ev.social/@christian/112761712837712799</a>

Recent searches

Search options

Administered by:

Server stats:

#browserfingerprinting