• 0 Posts
  • 8 Comments
Joined 7 months ago
cake
Cake day: June 7th, 2025

help-circle
  • It isn’t a magic solution, no, but you have a lot more control than crummy layer 3 firewall rules and endless lists.

    The big players have far more data about what bad looks like. Either we can play whack a mole with outdated tools and techniques or get smart and learn to use what is available.

    Self hosting doesn’t mean we go backward in terms of the sophistication and difficulty, it means embracing modern solutions.

    In the dinosaur days, we had primitive tools, but so did the attackers. We cannot hope to self host with any measure of security if we bring piss to a shitfight.


  • Get a WAF. Sophos firewall is free if you want to diy. If not, use cloudflare.

    Opening ports, logging, monitoring, nailing up allow listed IP addresses and dicking around with fail2ban is such a timesuck. None of that crap will stop something from exploiting a vulnerability.

    Some things are worth farming out to a 3rd party. Plus, you can just point your DNS entry over and be mostly done. No more dynamic IP bs.




  • Also, Americans are subject to supporting this bullshit. If any company in the us (or in the world really) owns or maintains data that the EU qualifies as adult-oriented, they have to either maintain a means of actively prevent EU users or support the filtering and tracking that the EU mandates. If not, they can be fined by the EU, and as long as there is a financial relationship between the us and EU, the fines will be enforced.

    This has global impact.

    I’m curious if more companies will move their hosting to countries that are non compliant with EU regulations and move to accepting payment from cryptocurrency only. I would not be surprised if x-rated content providers were to move to such places.




  • A robot told me: The Meta/Yandex exploit worked by having JavaScript running on a website (such as Meta Pixel) connect from the browser to a native app on the same device via the localhost (127.0.0.1) interface, using HTTP, WebSocket, or WebRTC. This communication occurs entirely within the device and does not traverse the network in a way that browser extensions like uBlock Origin can intercept or block. Browser extensions generally cannot block or even see requests made to localhost sockets, especially when those requests are initiated by scripts running in the browser and targeting native apps on the same device