Github supports ephemeral runners which are limited to a single job.
You can use `workflow_job` webhook to be notified of a new job, after that you need to call `generate-jitconfig` API to get a just-in-time configuration token, and then you can start a Github runner in ephemeral mode with the JIT token.
This allows you to orchestrate Docker containers, KVM instances, etc., which are used for a single time, and then destroyed.
There are some open source projects, such as using ephemeral Kubernetes pods with the ephemeral runners.
Yeah thats exactly why Im on it. The frontend is fine, maybe a wash compared to Swiftfin last time I tried it out. But for my library, I had frequent issues with codec support on native client vs 0 times on Infuse.
Just for the comparison, Damn Small Linux is still around 700 MB, and contains Linux kernel, desktop environment, web browser, office suite, and other software.
Mimo app will never support as many devices as Linux kernel does.
I'd assume that most people wouldn't want to get back to wired headphones.
Transition period was definitely rough, but nowadays bluetooth headphones are substantially better than they were in the past, and it's quite freeing to not have to deal with wires.
There are definitely benefits to wired headphones, such as better audio quality and no battery life to worry about, but for those cases there are USB-C DACs.
Brand new devices' batteries are awesome but wear off and need to be changed at some point, if A) the device is designed to let you do that and B) the battery is still in production.
You don't really own a wireless headphone. You can see it as a rent, or an ownership that loose its capability when in use.
It's not like wired earbuds/headphones are invincible either. I've had a few wired ones lost due to cable damage, which constitutes more casualties than my wireless inventory, including noticeable charge loss. Of course, there are a lot more cheap wired options with replaceable cables now, thanks to Moondrop and gang.
I really wish the debate was more than jack vs Bluetooth, and more wired fans would consider supporting devices with multiple USB-C ports. Yeah, Sony still puts a jack on Xperias, but most audiophiles note that it's driven by Snapdragon's mediocre integrated DAC, possibly because Sony doesn't want it to compete with Walkmans. Yeah, Valve puts a jack on the Steam Deck, but SD OLED's jack has interference issues that users need to fix with electrical tape or loosening screws. If these devices had two USB ports, then it would be easy to use a better DAC with no interference issues (while also charging with a cable attached to the other port). Having a second USB port would increase device life, and tie wired earbuds/headphones to a more durable standard that's actively developed and backed by legislation. We know this is possible for phones because ASUS ROG Phone has 2 USB ports.
This is simply wrong. Apple airpod was not designed to replace battery(they use tons of glue), yet many repair shop still offer service to replace battery for them.
>B) the battery is still in production
The industry is kind of converging into using standard "coil cell" battery for their headphone
Sure, but I am totally willing to make that tradeoff, and when my earbuds die, I buy new wireless earbuds, not permanently switch to some wired headphones I have lying around (mostly just in case, to not be left hanging if my earbuds suddenly die). I didn't know that before I started using wireless stuff, but now I do. Because, you know, I can change my T-shirt, maybe even take a shower, and start cooking something in the kitchen without pausing that audiobook, all while my phone is charging in another room.
I am even cautiously aware that people have lost their hearing, because damn LiOH exploded in their ear. That's much scarier than knowing I will have to buy new earbuds in a couple of years. Didn't stop me using them either.
This sounds correct, there are no changes for public repositories.
For private repositories, each GitHub account gets 2000 free minutes of runtime per month. Both self-hosted runners and GitHub-hosted runners count against that quota.
They are not just more expensive, they are also slower. Last time I compared them, AWS ARM64 instances could easily run jobs 30% faster, for the same CPU/memory count, than those that GitHub offers.
Self-hosted runner regularly communicates with the control plane, and control plane also needs to keep track of job status, logs, job summaries, etc.
8h job is definitely more expensive to them than a 1 minute one, but I'd guess that the actual reason is that this way they earn more money, and dissuade users from using a third party service instead of their own runners.
You can use `workflow_job` webhook to be notified of a new job, after that you need to call `generate-jitconfig` API to get a just-in-time configuration token, and then you can start a Github runner in ephemeral mode with the JIT token.
This allows you to orchestrate Docker containers, KVM instances, etc., which are used for a single time, and then destroyed.
There are some open source projects, such as using ephemeral Kubernetes pods with the ephemeral runners.
reply