Mitch Effendi (ميتش أفندي)

I like coffee, Philly, Pittsburgh, Arabic language, anything on two wheels, music, linux, theology, cats, computers, pacifism, art, unity, equity, etymology, the power of words, and getting high off airplane glue. Will use Adobe Illustrator for food.

  • 0 Posts
  • 17 Comments
Joined 13 days ago
cake
Cake day: July 30th, 2025

help-circle





  • i just wanted to drop my personal favorite self-hosted git alternative, Gogs (gogs.io). i have very modest git needs (i just need a place to host code and interact with the git client), and i think it fits the bill well.

    i am not associated with it at all, i just want folks to know that self-hosting your own git service has really never been easier or better; there are so many good options, like a similar project, gitea.

    if you are uncomfortable with exposing your home network to the internet, you can use tools like tailscale funnel or a reverse proxy server like caddy and a $5 VPS from any cloud host of your choosing to obscure your home IP, while still keeping the storage and the brains somewhere closeby.

    imo, the only way forward for all of us to stay safe is to keep repeating a simple mantra: “let’s go back to making websites.”








  • I worked with one of the inventors of IPv6 for a bit of time, and I think knowing Carl really gave me an insight into who IPv6 was invented for, and that’s the big, big, big networks — peering groups that connect large swaths of the Internet with other nations’ municipal or public infrastructure.

    These groups are pushing petabytes of data every hour, and as a result, I think it makes their strategists think VERY big picture. From what I’ve seen, IPv6 addresses very real logistical problems you only see with IPv4 when you’re already dealing with it on a galactic scale. So, I personally have no doubt that IPv6 is necessary and that the theory is sound.

    However, this fuckin’ half-in/half-out state has become the engine of a manifold of security issues, primarily bc nobody but nerds or industry specialists knows that much about it yet. That has led to rushed, busy, or just plain lazy devs and engineers to either keep IPv6 sockets listening, unguarded, or to just block them outright and redirect traffic to IPv4 anyway.

    Imo there’s not much to be done besides go forward with IPv6. It’s there, it’s tested, it’s basically ready for primetime in terms of NIC chip support… I just wish it weren’t so obtuse to learn. :/