It is in the bottom right corner when clicking (i) button just like the https://osmfoundation.org/wiki/Licence/Attribution_Guideline... suggests. The only questionable part I see is that after page reload it flickers for half a second and then gets automatically hidden instead of getting hidden after manual interaction with map. Is there any other point in attribution requirements that it doesn't comply with?
I could've sworn it wasn't there before - but maybe I also just missed it since it is covered by the half-transparent panel (on mobile) and all the other stuff around it distracted me.
This is my mistake, mobile is/was a mess and I was only really looking at desktop before posting. It was buried behind the misplaced bottom bar. Fixed now.
It's not so much about which countries actually grow that much right now, but which mindset underpins the political and medial discourse, trying to get those countries "back on track for continuous growth" or whether there's some realization, that infinite growth as fundamental principle just isn't what we all should be aiming for anymore.
This won't simply dump power into the grid (unless the used inverter would violate codes right and left), since those inverters need to sync to the grid first before allowing for any output.
So if the grid is down - nothing will happen.
Overproduction is a possible issue for the grid operator. It's not a huge risk, but if there is an issue where the grid is producing too much energy, and at the same time homeowner solar is also producing a lot, then it becomes a potential issue for the grid to have to figure out how much production to cut to minimize the risk of damaging the grid while also not browning out the grid.
It's a small risk, but one to consider when UL listing cheap solar for everyone.
grahamc wrote down how to optimize this (within the constraints of max 128 layers supported by OCI) to categorize/prioritize packages by popularity/dependencies which lead to dramatic speed-ups for pulling updates or related images.
Most systemd components do rely on some core systemd components like systemd (the service manager) and journald. I would say that a core thesis of systemd is that Linux needs/needed a set of higher-level abstractions, and that systemd-the-service-manager has provided those abstractions. The fact that other parts of systemd-the-project rely on those abstractions does not imply that the project is monolithic.
>Try running any part of the systemd software suite on an openrc system and see how that works out?
Well from this POV it's kinda openrc's problem if it doesn't. What about trying to run any part of the Openrc software suite on an Upstart system? The question why would anyone sane want to is rhetorical tho...
Why obsessing over whether systemd is monolithic and in what measure anyway? There certainly ARE optional systemd parts. So it's correct to say it's not entirely monolithic.
openrc-init can be used on an upstart system, the daemon manager itself can't but that's because you'd have two different daemon managers. Beyond that there aren't any openrc software components, because it was designed to be a modular init system that just handles what it was intended to handle.
The rest of the system for example chrony, sysklogd, cron, etc run fine on upstart systems, because they aren't tied to systemd and are fully modular.
It's okay to be a monolith, that doesn't make it inherently bad or anything, but we should be honest about it, and it does come with some tradeoffs.
Explain the existence of "elogind" and "eudev" then?
It might be the case that one can disable some components of systemd, on a systemd system. It is certainly not the case that they are "loosely coupled", or there would be no incentive to maintain forks of core systemd components with the sole and explicit purpose of decoupling from systemd.
In theory. In practice, systemd is a mess of different components that have subtle dependencies on each other. And while the core of systemd is solid enough, everything around it is not.
It's a collection of tightly-coupled components that are functionally a monolith because large distros tend to rely on the various components rather than allowing modularity.
If it contains forbidden substances you fine the importer.
Most grocery chains in Germany with the exception of Edeka (I guess it's similar in other countries) apply stricter standards than the legal limit anyway with their suppliers, and ensure compliance by testing on their own
If you're not using the OSM API, there are also full exports of the complete dataset available at https://planet.openstreetmap.org/