• 0 posts
  • 23 comments
Joined 2 years ago
Cake day: November 5th, 2024
  • I could rant about the slop but it’s pointless because the developers of this didn’t even understand why Discord alternatives never work out.

    • Bridging Discord without bots on Discord’s side is against Discord ToS, so don’t rely on that.
    • P2P is a great idea except it scares the hoes so you’ve cut 80% of your market off right there.
    • No federation so realistically everyone is gonna have to create and manage like 10 separate accounts for each of their friend groups, which even the most hardcore anti-Discord folks aren’t going to bother with.

    Also this is a promo post, however sneaky you try to make it. Tag appropriately.

  • Some day we’ll just have to stop routing people who misuse our common protocols.

    I already stopped caring about my IP being on blocklists because it only ever ends up on those for the dumbest reasons. If someone can’t connect to me then it’s their problem. I can’t perform remote IT support for every person who bought a Unify firewall and clicked “block bad IPs”.

    I reckon in my life time I will also turn off IPv4 and just stop dealing with it’s bullshit.

  • Here is my copypasted documentation

    				== PROXMOX CONTAINERS & VIRTUAL MACHINES ======================
    				C:TorRelay      -	192.168.78.160  /  2a05:f6c7:8321::0160
    				C:Gonic		-	192.168.78.161  /  2a05:f6c7:8321::0161
    				C:Corrade	-	192.168.78.162  /  2a05:f6c7:8321::0162
    				C:MeshCore	-	192.168.78.163  /  2a05:f6c7:8321::0163
    				C:Apache        -	192.168.78.164  /  2a05:f6c7:8321::0164
    				C:Backups       -	192.168.78.165  /  2a05:f6c7:8321::0165
    				C:PiHole        -	192.168.78.166  /  2a05:f6c7:8321::0166
    				C:WireGuard     -       192.168.78.167  /  2a05:f6c7:8321::0167
    				C:qBitTorrent	-	192.168.78.169  /  2a05:f6c7:8321::0169
    				C:OwnCast	-	192.168.78.170  /  2a05:f6c7:8321::0170
    				C:i2pd		-       192.168.78.172  /  2a05:f6c7:8321::0172
    				C:endlessh	-	192.168.78.174	/  2a05:f6c7:8321::0174
    
  • it attempts to log in using a list of credentials.

    Do you read what you post or do you just google “ssh vulnerability” and post the first result to waste my inbox space?

    Software doesn’t get patched all the time,

    SSH does, it is one of the codebases with the most eyeballs on it at any given time and patches to it get fast-tracked downstream.

    advising hobbiests on how to configure and maintain their personal server, not the engineering meeting for a fortune 500

    You don’t need to be a genius to enable keys, disable root and install fail2ban.

    it remains best practice not to expose ssh to raw internet unless absolutely necessary

    This is correct, but we are arguing about a case in which it is necessary to expose something and it’s better that it’s one of the most secure and battle-tested pieces of software in the world as opposed to some open source hobby *arr stack.

    arguing against the industry standard … more experience and engineering time than you or I.

    I work in this industry, ma’am.

    Did you know that simply being connected to the internet puts you at risk? Your firewall could have a vulnerability! Your router’s admin panel could be misconfiguration and exposed to the internet! The only way to be safe is to unplug your cable and stop replying to me. Also rip out your bluetooth modules and any LEDs in every device you own because they have been demonstrated to be attack vectors. In fact just stop using anything more complicated than a MOSFET.