You can. Sort of.
Lemmy does not provide it via the UI. But it does provide the info via federation. If you set up your own instance, other instances will happily share this info with you. The information is inconvenient to access, but not hidden or private.
An important point of this deal, is that Germany can now collect taxes on profits made elsewhere. If Poland collects 10% tax, then Germany can collect the remaining 5%.
This means that governments aren't competing for businesses anymore. Instead they are fighting amongst each other to figure out who is allowed which share of the newly found bounty.
What I miss in the CLI, is proper structure in the text.
For example, a good IDE will list all problems found with your code, ordered in a sensible way. If I then click in a problem, it expands, and I get to see the full text description of that error. I can then click on a file/line combo, and be directed immediately there.
If I run CMake directly, I get kilobytes of error message dumped into a single blob of text.
Colors, line prefixes, and separator lines attempt to bring some structure into this mess, but it still remains a big wall of text.
It takes less effort for me to process the data presented to me by a good IDE, because it is organized and structured.
Same thing with git commits/branches/tags.
Same thing with diffs/merges.
Almost ALL text data can be organized in some way. But most text data is not big enough or common enough, that it is worth our time and effort to structure it that well. I therefor see GUIs as tools for when you are doing something so commonly done, that the effort of structuring the data was worth it.
About 80% of all effort for the Lightyear cars is in efficiency.
You have the obvious, like weight and aerodynamics. But also things like in-wheel motors, which are much more efficient than normal electrical engines, since there are almost no mechanical losses. Or the rear-view camera's, which save a lot of energy on air-resistance.
I'd like to know what an alot is.