• 1 Post
  • 239 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle

  • OMG.

    https://en.wikipedia.org/wiki/Security_through_obscurity

    In security engineering, security through obscurity is the practice of concealing the details or mechanisms of a system to enhance its security. This approach relies on the principle of hiding something in plain sight, akin to a magician’s sleight of hand or the use of camouflage. It diverges from traditional security methods, such as physical locks, and is more about obscuring information or characteristics to deter potential threats. Examples of this practice include disguising sensitive information within commonplace items, like a piece of paper in a book, or altering digital footprints, such as spoofing a web browser’s version number. While not a standalone solution, security through obscurity can complement other security measures in certain scenarios.

    You don’t know what you’re talking about - please stop. It’s embarrassing. It’s a long-standing industry term not some weird phrase I just made up. Nobody is saying “Linux is obscure”.





  • See what I mean?

    As if a proxy blindly passing traffic directly to a backend server “reduces attack surface” in any meaningful way. 🙄

    Edit: Guy edits his post with a bunch of stuff and assumes I’ve read it later. I can’t eyeroll enough…

    1. You’ve increased your “attack surface” by adding a second application to the stack. Proxies aren’t magic, they are also targets.
    2. Sure - you can do those things on a proxy. How many people here are? And why are those things never suggested when people here say “use a reverse proxy”? Because they think the proxy is the security.











  • So - I setup that model according to the docs and gave it this prompt:

    Write me a highly optimized n-queens solver in go. It should take advantage of parallelism (what little there is) and output only the solution and how long it took.
    

    After 10 minutes it gave me code that didn’t compile.

    It took another 3 mins to fix the compile error and the output is not correct.

    As I said - LLMs on 8Gig VRAM just aren’t worth it.



  • Yeah - I’ve been playing around more with the Qwen3-Coder-30B-A3B-Instruct MoE model and it’s still quite… Meh. I’ve been using llama.cpp and I’ve tried a bunch of tuning. It works and performs well enough (15t/s) but the output is just garbage. I can do some simple coding but I’m finding I’m fighting with it more than if I just wrote the code myself. Maybe I just have standards that are too high. Claude Opus 3.7 is just in an entirely different league…