• 0 Posts
  • 94 Comments
Joined 3 years ago
cake
Cake day: June 20th, 2023

help-circle

  • You actually have a lot of options in this space. You can take the prefill engine of just about any LLM and turn it’s transformer into a classifier by lobotomizing out the decoder. You can also use a diffusion model on single pass to surprisingly competent result.

    If Jeff looks easy enough to deploy by all means start there, but don’t discount the idea if Jeff sucks; you have a lot of options.


  • You could (and probably should) use a system-one style inference system for spam classification. Much cheaper and the structured output means it’s impossible to go rogue and curl some malware or whatever. It can absolutely misclassify but its output is programmatically structured and just ranks a pre-selected set of output tokens.

    In your case that’s

    Spam

    Not_spam


  • MIT: I build my thing on top of your thing, it’s my thing now. I sell it, you have no rights.

    GPL: I build my thing on top of your thing and your license forces me to distribute my thing under the GPL, including the source code.

    There are legitimate arguments for both. Sometimes it sucks when proprietary things get built on top of MIT code but sometimes it takes money for innovation, and in the realm of code the world often benefits anyway by virtue of copycats or distillation.






  • It would be more accurate to say they try and block the vpn providers and Tor exit nodes. In practice, they do have ~95% of Tor exit nodes blacklisted but major vpn providers it’s closer to 40%. Vpn providers go through a lot of effort to hide their exit traffic and it’s pretty simple to use a provider that has a reasonably robust cli to just rotate nodes until you find one that works

    Connect

    Test known-good video using yt-dlp

    If fail, use vpn cli to connect to a new node

    Reeat until success

    If your provider let’s you connect to specific nodes you can even store the last-known-good and use it on first connect until it gets blacklisted, extending uptime considerably



  • Yes I have, admittedly it’s been about a decade but at the time I switched because getting hardware acceleration in chrome and Firefox was difficult on debian, trivial on Ubuntu. I like the stable, but newer packages that Ubuntu offers, plus the first-party support you get from a lot of projects. I wish debian was the standard dpkg assumption for first-party support but it unfortunately is not.





  • People shit on it but there’s a lot of good open-source tooling that supports it.

    There are nist l1 profiles

    Tutorials and guides for everything

    etc

    Part of being a good sysadmin is knowing when not to reinvent the wheel. Ubuntu has a lot of options for vetted, hardened, “other people’s wheels.”

    Also, for posterity, the competent ones are running the headless, server version of Ubuntu. (As opposed to the bloated mess that is Ubuntu Desktop). The server version catches a lot of flack it doesn’t deserve.





  • If caddy is acting as a proxy for anything, you should not need to forward that port externally. Local host firewalls allowing traffic on your local network is sufficient.

    Depending on your physical host layout you may be looking at an issue with nat reflection.

    You have not given us enough about your topology to assist in troubleshooting.