The main reason is that libtorrent, which is the literal backbone of most torrenting clients, has implemented supported for I2P only recently in its latest v2.x branch… It takes time for libtorrent to iron out bugs and stablize and it takes more for clients to upgrade their embedded libtorrent to v2.x.
It would be greater if it can also leverage IPFS. So we can have unique identifiers per media object and hence deduplication in a P2P network which in my opinion is more federvise affinitive. I have been thinking of making such an alternative media backend for a while.
Quadrupling the daily active user to 1.1-1.2M is so far so good. I don’t know how different your story is but that is barely 0.5% that of Twitter still.
You can try your luck with the Nvidia’s open-source kernel driver. I dun think it will work any better than the proprietary one though.
I have bought an 11th gen Intel Framework. When the Intel 12th gen was out, I purchased a motherboard and replaced the 11th gen one. The process was common and straightforward but the experience was almost magical. We should have been able to do thIs years ago. The 11th gen motherboard is now runnIng my media center faithfully in a DIY acrylic case. Kudos Framework. You ought to be the future.
Yeah Chuuka Ichiban! (中華一番!) is the first to the formula and should be deemed the original to Food Wars aka 食戟のソーマ.
The last commit was made March this year (2023) right?.. That’s fairly recent at least by the standard of open source software. Also if the app runs, why bother?..
P.S. Btw if you check the
developbranch, the most recent commits were made last month.