This is probably one of the most niche use cases ever, but I decided to release it regardless.
There are already a few more projects doing the same thing, but they didn’t quite fit my personal use case, so here we go:
GoonServe, an in-memory, self-contained funscript server for the Handy.
Why?
As far as I could find, the projects that already did funscript hosting were meant as scalable public-facing infrastructure and not really something you can throw on a Raspberry Pi just for local network use and forget about.
This project accomplishes that. It targets the original Raspberry Pi Zero W, runs entirely in-memory, and is fully self-contained without any dependencies, and is compatible as a drop-in replacement for most use cases.
Wait… I don’t think even you know how huge this project is.
This is half of the handy API implementation and you opensourced it as a single go binary.
For those who are unaware. Every project you ever come across that delivers funscript to your handy needs this since OhDoki don’t have it readily available.
Using this, you can easily write a small bash script or powershell script and push funscripts to this local server (put it in services.msc or systemd) and you can turn your file explorer into your handy library.
tbh its just a self contained go port for the server component of a c++ unix background daemon im writing to sync the handy with mpv (since current solutions in linux are either electron apps, or python scripts that need to be restarted for each video), currently its mostly complete and just missing FW4 support, which i will probably be adding and releasing it as open source sometime around mid september
Yeah but that’s what I mean. There was a project some time back that was an MPV + shell script that you could use but it used a dedicated non-user owned server. This makes that a possibility while hosting that same server locally. This makes a lot of things that weren’t possible, possible.
All this needs is a shell script that handles the protocols and slider. I’m sure you can even write a small client that can issue commands and this would easily be the game changing local API implementation we’ve been looking for.
Just need to write a guide to tell users how to make their own api registration