it seems it has already been

AGENTS.md, CLAUDE.md, copilot as contributor, an insanely long readme full of tables and emoji for a project that is just a couple of months old, solving a problem nobody who can read a man page has, posted by an account named after the project, with explicit disclosures in the post.

idk it's unclear

I don't think so. He has been a developer for at least a decade. I did not find code smell or bad habits. He does cover his code with plenty of tests. Sonarcloud shows very little issues with the code. That is with all original measures and rules in place.

The dev seems to do all the right things including disclaiming the use of AI.

Vibe coding would mean writing no lines of code, just words to an LLM. In the disculosure here, that would be generated.

They have Pair in the disclosure, which is about a 50/50 split in code.

@runwisp_com@lemmy.world you have some formatting issues in the disosure, its all on the same line.

no. I am an experienced engineer that has been writing code for more than 10 years, way before AI. While AI definitely has been used to write code, the code architecture is actively designed and reviewed by me, a human.

actually not harsh

this is exactly the kind of concrete feedback I was hoping for. You're right that the quick-start paragraph explains the actual value better than the current pitch.. Thank you for taking the time to look at this.

I generally like some things that syatemd gives, but is there an easier way to create timed automations with systemd timers?

with cron, its just a single line with the recurrence pattern and the command. with systemd, you have to create a timer unit file with several lines, a service unit file with several lines, put them in the right directory, reload systemd, enable the timer. timers are not difficult, but much more convoluted than the crontab. if you have to make multiple pairs, or update something in them, it gets old fast.

Or just cron that calls a logger works well enough

If systemd timers, journald and cockpit already cover your needs, RunWisp probably isnt for you. RunWisp is aimed at people who want portable TOML-defined tasks and services with unified history, logs and alerts. you’re right that ACLs are currently missing, but access is protected by password authentication and the UI can only trigger commands already defined on the host.

See disclosure at the bottom - Implementation lists pair.

Thats 50/50 per our rules here.