pelletier

Agree. Though at some point I also added a round up when percentage was strictly between 0% and 1%. In my case it seemed like users believed more easily that the program was “broken” if it took a while at 0% rather than 1%.

> Multi-repository pull requests should be a first class feature of any serious source code management system.

Do you have examples of source code management systems that provide this feature and do you have experience with them? repo-centric approach of GitHub often feels limiting.

I'm curious to see how the limitation of using pyodide packages only will play out for non-trivial builds. Thinking of all the non-pure python code out there that need to be manually rebuilt to support a non-trivial production app.

Maybe Cloudflare's adoption will help bring more packages into the fold, and if it's an 80/20 rule here, would be good enough.

I'm curious what are the implications of having pre-set hardware info. Maybe rate-limiting? or easier for Apple to flag those particular serial numbers to block the service if they wish?

They mention the generation needs a plist from an actual Apple device, and provide one of their own in the repository. I wonder what Beeper does. Maybe they have just one serial number? Maybe they have multiple and rotate?

How does the generation of validation data for registration work? As far as I understand, this requires details from an actual Apple device (serial number, model, etc.)

You mention it's a passion project. If technology is the center of that passion, then pick what you're passionate or curious about!

If not: the tried but true Rails + Postgres.

Add more things only when needed. For example Alpine.js if a bit of interaction that's not covered by Rails' Turbo. If the need for background processing arises, bring in the good_job gem, and there may be no need to deploy it separately at first.

For hosting I'm not quite sure these days. Heroku may be on life-support, but its feature-set covers most basis.