• 0 Posts
  • 20 Comments
Joined 13 days ago
cake
Cake day: March 3rd, 2026

help-circle

  • DoH is not as private as you think, that’s just how big tech positioned it.

    DoH encrypts DNS queries between your browser and the DNS resolver, it does not hide your browsing activity from the DoH provider itself.

    Google, cloudflare or any other 3rd party orgs still see your data.

    I have an open source firewall on gitlab if you wanna take a look. Blocks some IPs - I know it’s not much but fuck Palantir - I made it so their site won’t load.

    Blocks 50+ stalkerware apps as well as data broker trackers.

    I want to go back to it so you can wire in through my VPS and build it as a mobile app to block Gemini and Apple Intelligence from scraping your photos and texts and everything to train their models.




  • I think we should be building localized, smaller, more finely-tuned LLMs.

    1. They wouldn’t require data centers.
    2. They would be forced to become more energy efficient or resource aware because they add costs to organizational profit margins - forcing innovation and creativity instead of throwing data centers and billionaires at the problem.

    I used AI to help with debugging and coding, as well as exploring a theory I came up with a long time ago - and with my framework and notes and research papers and everything else I’ve collected to support my theory, I was able to put it into application with my own AI cybersecurity I’ve developed.

    We’ve created 26,000 new cyber threat datasets because I had access to an LLM that could help me take the frameworks, notes, and research I’d gathered in my attempts to build this out and within a couple months I had something that blew my prototype out of the water.

    • there is a lot of value in these LLMs. What I’ve been exploring is on-hardware AI. Not a friend. Not a chatbot. A program that does what it’s supposed to and that’s it.

    My startup in cybersecurity- we use less than 1GB of ram, at peak use maybe 30% of a single cpu core, and it was build with ethics and safeguards in mind. Not LLM but real Machine + reinforcement learning.

    To me ethics also meant resource awareness. If I’m poisoning the planet and the people then it’s not a good product.

    Building smaller, more specialized local models is not only better from a cybersecurity perspective, but smaller local LLMs mean new startups to build them, a race to innovate and improve resource usage, more data privacy, smaller attack surface, no obscenely expensive API calls and overage fees…

    What we should have is a Symbiotic approach to AI - a partnership sort of understanding.

    LLMs helped me with debugging and putting this research and theory together. And in a fraction of the time it took me to build the framework.

    I pushed autonomous operation because I felt that it was about giving people their time back. Providing freedom. If my cybersecurity can take care of 94.1% of all threats before they reach an analyst - that analyst doesn’t have to wake up at 2AM to sift through 10000 false positives. We do it.

    Now that analyst can do what they got a degree to do - actually defend a network. Build and explore threat research and databases. Find their purpose again.

    We require that a human is always in the loop and help protect cybersecurity jobs by ensuring that all human input is always the final decision. Let our AI do the heavy lifting so you can take care of this shit that matters and what you really want to do.

    Sorry I think my adhd took control of this conversation.





  • Ok - hear me out.

    We get idk 1000 of us poors to buy some cheap land in the Midwest. Up in Appalachia.

    We sell “Rapture Survival Communities”

    They’re $999/month and you’ll get a hidden bungalow community complete with bunker. We’ll fill it with doctors and pastors and birthing women.

    BUT YOU CANT KNOW THE LOCATION UNTIL THE RAPTURE HAPPENS. You don’t want any pesky liberals finding it and gaying up the place with their liberal demonic child sacrifice transness.

    We will deliver coordinates via analog radio and Morse code once the rapture has started.

    By business plan makes Sam Altman hard in his butt:

    1. Collect money
    2. Don’t build anything.
    3. repeat

    When they come screaming for proof and receipts and refunds… Just gaslight them and buy a politician.








  • I tried to help.

    I built mobile mesh network and 2 layers of encryption for a vault to secure digital evidence of ICE terrorism. Chacha quantum resistant with aes-256 fallback.

    It was open source and free… but I asked for $5/month for the optional upgrade to route traffic through an encrypted vpn tunnel.

    VPN was firewalled so all connected blocked most trackers, data brokers - at both DNS and DoH level. We blocked 50+ stalkerware apps for good measure as well.

    I tried to present this to my community. Apparently this made me a “security risk” because I asked for $5/month for the vpn access.

    Fuck me for not sleeping for a week and killing myself to put this together only to be publicly condemned over 5 fucking dollars.


  • Let me help you:

    AI does create a lot of slop - but at the same time, a lot of people don’t know what capabilities exist and what’s just marketing/hyperbole.

    They read “AI will replace software engineers” and think that they can just talk to an AI and spit out working production level code.

    Not saying that’s you. I don’t know your work.

    1. It doesn’t know your machine unless it has local access. How will it know where you’re installing if it doesn’t know your directory tree?
    2. it doesn’t know that it needs to import other modules or how separate functions need to interact. Not until you build it out and track what you’re doing and how the functions interact. It’s just documenting the work you do.
    3. It defaults to basic framework from which to build - just like we would.

    You don’t sit down and write 8,000 lines of code just one line after another. Shit - it could take me 3 days to figure WHERE to put 2 lines of code.

    1. Claude web and Claude code can be split into dedicated projects or containers.

    This allows specific contextual awareness. The more work you do in a project the more you can build off of it.

    Organizing into context aware containers allows you to massively improve your code base because it actually accesses the code itself. Less guess - less slop. Not “no slop” just less.

    It doesn’t replace everything, but recently I had Claude code evaluate ~43,000 lines of code. I verified its audits manually, and let it do its thing. I still had to make corrections on some assumptions it made but I fixed 110 critical bugs in an afternoon because of this system I’ve described.

    If you’re expecting to say “build me x” it isn’t going to be successful.

    Treat it like it’s a tool in the toolbox, not a replacement for good practices.

    To your other note - the first time I tested Claude code I was blown away. Then the 2nd or 3rd time it took over… I felt like I lost my purpose. I need to be involved, not replaced.