• 0 Posts
  • 46 Comments
Joined 10 months ago
cake
Cake day: June 4th, 2025

help-circle

  • notabot@piefed.socialtoLemmy Shitpost@lemmy.worldWacky
    link
    fedilink
    English
    arrow-up
    13
    ·
    12 hours ago

    What kind of prehensile pps are y’all having??

    Just the normal kind.

    Are dicks supposed to have 6-packs?

    You need to put in the work to get the best result.

    Or is there a secret fellatio technique that includes pelvis-deep sucking?

    You really have been missing out…




  • The TCP connection time out on linux defaults to a bit over two minutes, although individual client programs can use different values, and I’m assuming Windows is similar. Honestly, I was thinking about the time to boot a server, but if you’re just suspending you’d almost certainly be ok, albiet with a slight power draw even when the machine is not in use. Hibernating might also be ok as long as your hardware gets through its POST quickly.


  • WoL works, but your server will take some time to come back online, but the router probably wont be able to buffer the traffic for that long, and a tcp connection would likely timeout before then anyway. You usually want to send the WoL magic packet, wait for the server to come back online, and only then start sending traffic.


  • A big problem is that vibe-coded stuff tends to be much harder to maintain as the ‘author’ diesn’t actually know how it works, and the code was not built for humans to understand. That’s not a problem that’s unique to LLM generated code, but it is common place in code that is, so “was this generated by LLM/AI” becomes a useful proxy question for “is thus codebase likely to be harder to maintain, and thus be less likely to be maintained well?”

    There’s also the sociatal level costs of using these models to consider. At present, they use significant amounts of power and cooling, both of which lead to adverse environmental effects. It serms quite appropriate to ask if a project using them, and to make the choice to avoid those that are, out of principal as well as technical concern.







  • An airgapped machine is certainly going to be most robust from external attack, but even then you should probably encrypt your files to ensure privacy should you ever discard, or otherwise lose control of, the storage media.

    An encrypted partition may be sufficient, but your journal entries will still be “plain text” when it is mounted, and so you will be able to read them without extra effort. If you want to make it so that once an entry is written it is encrypted and can only be read with deliberate effort, you could use GPG encryption.

    First generate a key pair with a really strong passphrase, and store it on a USB drive. Then import just the public key onto your journaling machine and store the USB drive somewhere safe. With just the public key on your machine you can encrypt files, but you can’t decrypt them. Ideally you’ll set up your journalling tool to only write via GPG, but if not, you can just encrypt each entry after you write it.

    As to what journalling tool to use, I like VIM, although I know not everyone gets on with it. You can have it start up with a template ready to go, not write temporary files, and save via GPG so the plaintext never hits persistent storage.



  • I’m assuming this is some sort of canary message to indicate that the code base has been compromised, the author can’t talk about it, and everyone should immediately stop using the service. Surely no-one would be unwise enough to commit this otherwise?

    Even ignoring the huge red LLM flag, a 25kLOC delta in a single PR should be cause for instant rejection as there’s no way to fully understand or test it, let alone in 2-3 weeks.





  • Thats the thing, if you’re feeling lost and powerless, having someone “strong” tell you that it’s because of some other group and telling you what to do and what to think probably feels really encouraging and positive. The fact you’re even more powerless in that situation probably doesn’t even register.