When I saw the 47-day expiration period, it made me wonder if someone is trying to force everyone onto cloud solutions like what Azure provides.
The old geezer in me is disappointed that it's increasingly harder to host a site on a cable modem at home. (But I haven't done that in over two decades.)
> The old geezer in me is disappointed that it's increasingly harder to host a site on a cable modem at home. (But I haven't done that in over two decades.)
It might be harder to host at home, but only for network reasons. It is perfectly straightforward to use letsencrypt and your choice of acme client to do certificates; I really don't think that's meaningful point of friction even with the shorter certificate lifetimes.
Why wouldn't you go with a week or a day? isn't that better than a whole month?
Why isn't it instead just a minute? or a few seconds? Wouldn't that be better?
Why not have certificates dynamically generated constantly and have it so every single request is serviced by a new one and then destroyed after the session is over?
Maybe the problem isn't that certificates expire too soon, maybe the problem is that humans are lazy. Perhaps it's time to go with another method entirely.
There is in fact work on making this an option: https://letsencrypt.org/2025/02/20/first-short-lived-cert-is...
> Why isn't it instead just a minute? or a few seconds? Wouldn't that be better?
> Why not have certificates dynamically generated constantly and have it so every single request is serviced by a new one and then destroyed after the session is over?
Eventually the overhead actually does start to matter
> Maybe the problem isn't that certificates expire too soon, maybe the problem is that humans are lazy. Perhaps it's time to go with another method entirely.
Like what?
On the other hand, the Great Wayland Security Theater probably doesn't admit such riff-raff.
I'm pretty sure it's doable, but it probably does need to be baked into the compositor. But since there are compositors that can do full immersive 3D environments with windows moving around in them, I can't believe that there's any manipulation of the contents of a window that you can't do in Wayland.
Of course, being able to add it as tiny helper program is probably something that's going to be specific to X11, or possibly (best case) require non-portable APIs that are specific to individual compositors in Wayland.
Maybe they want dns resolution to work properly
In any event, that makes no sense. Pretend for a moment that glibc has working DNS and musl doesn't have working DNS (not true, but let's pretend). You don't build your compiler chain with working DNS support and then use it to build programs without working DNS.
Out of the glibc tarpit
Why have any glibc? GCC et al. work fine compiled against musl (as proven by ex. Alpine only doing musl). Or is it for running on GNU/Linux systems (can't you statically link the build chain?)?
I am the youngster volunteer at a local demonstration garden. The elder volunteers in their 70s are all very sharp. They usually don't stop until arthritis or back problems force them to stop. But their minds are agile, and they are all very social, cooperative, and upbeat.
The key seems to be enjoying it all, and not being too aggressive. Moderation. Going with the perennials, especially natives to the area, can produce unexpected large displays of very vibrant flowers that attract a lot of pollinator and bird life. A high tolerance for failure helps greatly. You'll know when something is working in your niche microenvironment.
Okay, ask the obvious question. Isn't that a perfect candidate for causality to go the other way? Anybody with basically any mobility or serious health problems is less likely to go out gardening, so of course you only see healthy people out gardening. (To be fair, I would expect that it is good for you and helps people stay healthy, but I would expect the selection effects to be a stronger explanation for what you're observing.)
I've also done xpra in docker before; that's always felt as hacky as it sounds though.