

I think it only means if you do get paid reasonable amounts for open source work, you don’t have to pay tax on that.
So between jobs it shouldn’t matter since you wouldn’t pay taxes anyway, unless you worked a lot and received a lot of donations. But if you contribute after hours of a regular job, this would ensure you still get the full amount the foss project receives.
There is also mention of assistance with administration, which I’m not sure what that entails.









The entire renewal process is fairly cheap, resource wise. 7 day certificates are already a thing.
In terms of bandwidth you could easily renew a billion certificates a day over a gigabit connection, and in terms of performance I recon even without specialized hardware a single system could keep up with that, though that also depends on the signature algorithms employed in the future of course.
The dependence on these servers is the far bigger problem I’d say.
This shortening of lifetimes is a slow change, so I hope there will be solutions before it becomes an issue. Like keeping multiple copies of certificates alive with different providers, so the one in use can silently fall through when one provider stops working. Currently there are too few providers for my taste, that would have to improve for such a system to be viable.
Maybe one day you’ll select a bundle of 5 certificate services with similar policies for creating your certificate the way you currently select a single one in certbot or acme.sh