https://huggingface.co/hexgrad/Kokoro-82M#training-details
The model uses freely licensed audio. Nice.
But it also uses synthetic audio from closed-source models and unspecified open-source licenses. Not nice.
https://huggingface.co/hexgrad/Kokoro-82M#training-details
The model uses freely licensed audio. Nice.
But it also uses synthetic audio from closed-source models and unspecified open-source licenses. Not nice.
Anything in the logs?
WORM: write once, read many. Any good backup software supports this.
You could also keep offline backups. You can’t compromise what you can’t reach.
I don’t have a use case right now, else I would.
If English isn’t your first language, “void” has a connotation of emptiness, nothingness. APIs are about constructing, not emptying.
Why the name “voiden”? Making things void is the opposite of what I want to do with apis.
I find it a lot easier to just clone the repo instead of cherry-picking files one by one. Especially if you think you only need one and then need to go back for more. Or if you want to pull updates in the future, or remember where you got it from. Or you want to include the documentation or examples or whatever else is in the repo.
Look at the repo. There’s at least the variables.yml file.
It’s not just one file.
It hangs at the bot check so I can’t read it, but usually you just need to clone the repo and run docker compose up like anything else. I’d read the readme and compose file to see if it says anything useful first.
It looks like there’s a docker compose file on the repo. Seems like a good enough place to start as any.
Yeah but like… where is the weak link? Is there some deficiency in the protocol itself? Or the implementation in the chipset on one or both sides? Or bandwidth, or overheating?
Longer than that. In particular, a malicious server can detect when a script is being viewed or downloaded vs being piped to a shell, and can serve something different. https://web.archive.org/web/20250622061208/https://www.idontplaydarts.com/2016/04/detecting-curl-pipe-bash-server-side/
I wonder if it was just a shitty chipset, or if it was overheating.
Oh I see. Maybe they have a bad disk; I would try reuploading that part if you can.
The most useful part of those articles is the ffmpeg command you can run inside the container to test it.
When you say “something similar on Hetzner vps” do you mean the command or the log? Can you increase the verbosity to get more info on the error?
Personally, I think seven correctable errors is tolerable.
I would just wait for the Fedora folks to pull it in and make it available to you.
Don’t tell me what to do. It’s my system, I’ll break it if I want!
I’d see if you could request deletion of the account and come back in a few years and create a new one. But there are no guarantees they won’t just require it for all new accounts.
Or just see how it goes without having one. Maybe create and maintain a mastodon account on an industry-relevant instance.
What is open source about this?