Avid Amoeba
- 61 Posts
- 2.41K Comments
Avid Amoeba@lemmy.cato
Technology@lemmy.world•YouTube’s AI slop detector incorrectly targets Kurzgesagt as other creators fear same fate - DexertoEnglish
9·2 days agoOh yeah the unsolvable deficit had my jaw drop. They packaged run-of-the mill pro-1% noliberalism as objective fact. It was crazy.
Avid Amoeba@lemmy.cato
Technology@lemmy.world•YouTube’s AI slop detector incorrectly targets Kurzgesagt as other creators fear same fate - DexertoEnglish
21·2 days agoNothing compares, to you
Avid Amoeba@lemmy.cato
Linux@lemmy.ml•For laptop owners: What is the landscape of linux sleeping policy like 2026, i.e. S0ix vs S3?
14·2 days agoS0ix 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.
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.
Avid Amoeba@lemmy.caOPto
Technology@lemmy.world•Chinese CXMT to Match Micron's DRAM Manufacturing Capacity This YearEnglish
61·6 days agoI meant the CCP isn’t, not CXMT.
Avid Amoeba@lemmy.caOPto
Technology@lemmy.world•Chinese CXMT to Match Micron's DRAM Manufacturing Capacity This YearEnglish
41·6 days agoWrong. Plenty of German large corpos helped Hitler come to power and made good money under him, and are prime brands these days. E.g. Agfa, BASF, Bayer and Sanofi. Our capitalists definitively do not want democracy. Plenty of them have said as much and their interests are aligned with autocracy. Democracy means taxes and regulations and they def don’t want either of those.
Avid Amoeba@lemmy.caOPto
Technology@lemmy.world•Chinese CXMT to Match Micron's DRAM Manufacturing Capacity This YearEnglish
5·6 days agoThat’s what I’m thinking too. They’re gonna go as far and as wide as they can go.
Avid Amoeba@lemmy.caOPto
Technology@lemmy.world•Chinese CXMT to Match Micron's DRAM Manufacturing Capacity This YearEnglish
51·6 days agoKamala Harris contributed plenty towards destroying democracy by refusing to represent a significant part of the American piblic that would typically vote D.
Avid Amoeba@lemmy.caOPto
Technology@lemmy.world•Chinese CXMT to Match Micron's DRAM Manufacturing Capacity This YearEnglish
272·6 days agoA smart decision which the Americans are probably not gonna make would be to nationalize Micron once they become unviable for-profit business, in order to keep the competency and ability to make RAM, which is an essential economic input these days. Instead I think they’ll just let the CXMT gang buy them at that point, just like they’ve let that happen to so many important firms. That’s unless democratic socialism has taken enough control of the US political power.
Avid Amoeba@lemmy.caOPto
Technology@lemmy.world•Chinese CXMT to Match Micron's DRAM Manufacturing Capacity This YearEnglish
20·6 days agoDo you think they’ll stop expanding after filling the consumer memory market though?
Avid Amoeba@lemmy.caOPto
Technology@lemmy.world•Chinese CXMT to Match Micron's DRAM Manufacturing Capacity This YearEnglish
1591·6 days agoThis shit is so over. This gang ain’t gonna collude on price with Micron. They’re in for eating Micron. First its market share, then its IP by buying it for pennies on the dollar.
Especially pay attention to the CCP’s directive to share IP among RAM manufacturers. They appear to be looking at this problem as a supply shortage of an essential component for the rest of the economy, which it is. But that also means they aren’t playing for profit.
Avid Amoeba@lemmy.cato
Linux@lemmy.ml•Linux desktop use spikes to over 10% in North America for the first time. There is also a corresponding drop in Windows and OSX use.
4·7 days agoRight? Windows gives MS enormous market power beyond the desktop license revenue. At the same time there’s obvious cost savings to be had by outsourcing the OS. What is the capitalist to do facing this conradiction… 🤭
Avid Amoeba@lemmy.caOPto
Selfhosted@lemmy.world•Improve very slow library scans on Jellyfin 10.11 / 12 on spinning mediaEnglish
2·9 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·9 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·9 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·9 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).















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.