• 61 Posts
  • 2.41K Comments
Joined 3 years ago
cake
Cake day: July 5th, 2023

help-circle
  • Avid Amoeba@lemmy.caOPtoMemes@lemmy.mlCome on
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    1 day ago

    I think that’s a result of them being less willing to throw AI at everything earlier on. They didn’t slap it on use cases where it didn’t work so well. Instead they gradually introduced use cases where AI integration did add obvious value. That strategy ended with ChatGPT’s public explosion.





  • S0ix is fine. LTT doesn’t know shit about shit. I use it on first gen Framework. It works way more reliably than S3 since there’s little nees for special handling in drivers and firmware. The Framework already consumes 3W when idle. S0ix brings that down to 1-2W. The first gen suppprts S3 and that doesn’t consume less power. So either way I need suspend-then-hibernate or suspend-to-both and that’s what you want as well. You’d have to forgo Secure Boot to enable hibernate. If root is on Ext4 on encrypted LVM, hibernate works even with a swapfile (default on modern Ubuntu). For fancier setups like root on ZFS you’d need to use encrypred swap partition for it. That’s what I currently use. If you want to know more details, have Qs, ask away.


  • This is true but it’s nice to have the whole app, data and database in one place, going together, snapshotted together, “backupable” together. It’s slower for sure. That said it can be reasonably fast with a large pool (more disks). With the magic of SSD cache, database reads fly and reads are the majority of the loads in my heads. In the future I would put root on ZFS as well and either do SSD cache or have root on ZFS SSD pool that gets send/recved regularly onto the spinning pool so it’s easy to restore when needed.












  • Thanks for the pointer. Checked, tried a couple others - they don’t know about it. They have some other non-random DNS records. AFAIK they can absolutely find it if they scan for all domains, but it’ll take forever if the name is randomly-generated and sufficiently long. Someone has to be determined to spend the resources. This doesn’t guard against that but against bots trying to fuck with the service at the port. I could move it to a wildcard though. There’s an overlap with another subdomain (they’re actually sub-subdomains and the first sub is common) but I could move that.