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

help-circle

  • Avid Amoeba@lemmy.caOPtoMemes@lemmy.mlCome on
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    10 hours 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.








  • 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.





  • Apart from the socializing time, the time to help the helper doesn’t accumulate as time spent on your end because the helper will help again speeding up another task of yours. In the long run the time saved from receiving help and the time spent from helping would balance out. The socializing time is lost and accumulates. With that said, there are tasks that are impossible or take significantly more than double when done alone compared to when done with a helper. That could very well make up for the lost socializing time. Now add specialization where you help in tasks that you’re good at and the helper does the same for you and those tasks end up done way faster than without help. And that’s why we invented division of labour, which allowed us to turn nature into useful stuff much faster than before. 😄

    I don’t ask for help enough. Replaced a toilet yesterday and my back is complaining today.



  • 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.







  • That would be reasonable. I did repeated rescans and only counted subsequent rescans. For me the initial scan after upgrade took a bit more but not hours. Subsequent scans took less. E.g. 20min -> 13min for write-optimized filesystem. So that’s reasonable, although 10.10 was way faster. Library scans are expected to get faster in 13 according to some Github threads I read.

    When I had the broken Home Videos library I waited 3 days for the initial scan to complete and it did not. Repeated rescans did not seem to complete although I didn’t wait 3 days for them. I’m not taking into account those scan times. Something was wrong with this library type on 10.11 and/or my media. Worked fine on 10.10.