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.
Avid Amoeba
- 46 Posts
- 1.07K Comments
If you believe what is happening is a result of the progression of the capitalist system, that assessment makes perfect sense. I tend to believe that.
Without QC we’d have turned indistinguishable from Americans.
Seem like over double the price and in my opinion - half as pretty. 😄
It’s like 20% thicker and 50% heavier. It’s weird. I bought the smokey and amber for gifts. Was shocked at the difference in the amber.
This is what they look up close:

The amber ones are significantly thicker and heavier.
Avid Amoeba@lemmy.caOPto
Selfhosted@lemmy.world•Improve very slow library scans on Jellyfin 10.11 / 12 on spinning mediaEnglish
1·3 days agoThis 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.
Got them from Coffee Addicts: https://coffeeaddicts.ca/collections/hearth-glass/products/hearth-double-wall-4oz-120ml-glass-set-of-2
It looks like a lot of the options they have are out of stock. Maybe they are phasing them out.
Seems like Cafune also have them.
I got some from Hearth. Don’t know much abt the firm, I got them from a Canadian retailer and they’re really well made.
Avid Amoeba@lemmy.cato
homeassistant@lemmy.world•Looking for a Thread 2.4 GHz transmitter to control a lightEnglish
2·5 days agoAny Matter/Thread IR blaster should work with HA. Assuming you already have a Thread radio on your HA.
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.
Avid Amoeba@lemmy.caOPto
Selfhosted@lemmy.world•Improve very slow library scans on Jellyfin 10.11 / 12 on spinning mediaEnglish
2·8 days agoThanks 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.
Avid Amoeba@lemmy.caOPto
Selfhosted@lemmy.world•Improve very slow library scans on Jellyfin 10.11 / 12 on spinning mediaEnglish
1·8 days agoHm. As far as I know that can only be done if AXFR is enabled (it’s not), if the domain has entered some search engine that has remembered it, through SSL cert that’s not wildcard, or through brute force lookup. Am I missing something?
Avid Amoeba@lemmy.caOPto
Selfhosted@lemmy.world•Improve very slow library scans on Jellyfin 10.11 / 12 on spinning mediaEnglish
1·8 days agoIt’s just an A record pointing to my IP. IP’s updated from my router via the DNS provider API.
Avid Amoeba@lemmy.caOPto
Selfhosted@lemmy.world•Improve very slow library scans on Jellyfin 10.11 / 12 on spinning mediaEnglish
1·8 days agoThanks for looking into it. As far as I read they moved to an ORM with 10.11 as a prereq to supporting other db engines. I’m guessing the db connection code would be undergoing major changes when they do that so I wouldn’t rewrite the current implementation. I’d either follow that work and help them get it right or rework the implementation after they’re done. We’ll just suffer through the mean time. 😄
Avid Amoeba@lemmy.caOPto
Selfhosted@lemmy.world•Improve very slow library scans on Jellyfin 10.11 / 12 on spinning mediaEnglish
3·9 days ago64K is generally small recordsize. For media they recommend 1M. My db was sitting on the default 128K recordsize and perforned fine on 10.10. It doesn’t matter much for reads because ZFS keeps it in RAM and if it gets evicted it goes into SSD cache (l2arc). But for writes the cache wouldn’t help unless I disable sync which risks data loss. I don’t think 10.10 did much writes during lib scan so write perf only mattered when something changed.
Avid Amoeba@lemmy.caOPto
Selfhosted@lemmy.world•Improve very slow library scans on Jellyfin 10.11 / 12 on spinning mediaEnglish
2·9 days agoNot sure if this is the problem I was hitting with my Home Videos library type. It’s got directories with YouTube videos. I tried re-adding it in 12-rc3, which was released a month after the nightly mentioned in the issue thread. Still couldn’t complete. I ended up re-adding the media as Shows library. Works okay with the directory structure I have.
The write performance was recorded without the problematic library (deleted).
Avid Amoeba@lemmy.caOPto
Selfhosted@lemmy.world•Improve very slow library scans on Jellyfin 10.11 / 12 on spinning mediaEnglish
3·9 days agoThat 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.









Well-hung