Oh, I meant searching for lists of celebrities with mixed heritage.

You might be able to find some more unique looks by searching for terms like mixed heritage, often children with unusual combinations of ethnicities also have facial features that are not often seen in the countries where the individual ethnicities are common.

Also to advocate for a specific tab size while also advocating for hard tabs is nonsense. The one flimsy claim to usefulness tabs have is that different people can use different tab sizes and all at the low, low cost of everyone having five times more work to use tabs for indentations and spaces for alignment and thus having to use visual whitespace of some kind.

You mean you don’t have muscle memory to obsessively save every time you stop typing?

Usually those are the ones all those companies and organizations are using who have their files encrypted by malware.

I thought the Microsoft technologies designed to allow anyone to access your servers were called Exchange and Active Directory.

It might be worth mentioning which xmpp implementation you are actually using for your server if you expect anyone to help you. Also in general, more details about your hosting setup, how you installed it, did you follow any tutorial or use any particular installer (e.g. Helm chart on Kubernetes), possibly if you made any changes to the config,…

I don’t really feel the UI is the problem with APT. It is more stupid errors that do not give enough detail such as the dreaded “but will not be installed” nonsense where you manually have to then try to install that package to see why or the issue with post-install scripts failing leaving the package manager in a bad state.

I would honestly expect that with modern spam filters the random rate fluctuations of spam getting through the filters would have a bigger impact on the spam you see in your spam folder than the actual number of devices sending it.

Also, if your theory were correct that those make up a sigificant percentage of spam sending devices I would expect home office trends during the pandemic (which often use devices sending all their outgoing traffic over VPNs with relatively strict firewalls) and especially complete closures at the start of the pandemic to have a big impact on spam volume which has never been brought up anywhere to my knowledge.

Because if a program dies and just prints strerror(errno) it just gives me “Permission denied” without any detail on which operation had permissions denied to do what. So basically I have not enough information to fix the issue or in many cases even to reproduce it.

The whole point of my complaint is that shitty C conventions produce shitty error messages. If I could rely on the programmer to work around those stupid conventions every time by actually checking the error and then enriching it with all relevant information I would have no complaints.

I know about strace, strace still requires me to reproduce the issue and then to look at backtraces if nobody bothered to include any detail in the error.

During development is just about the only time when that doesn’t matter because you have direct access to the source code to figure out which function failed exactly. As a sysadmin I don’t have the luxury of reproducing every issue with a debug build with some debugger running and/or print statements added to figure out where exactly that value originally came from. I really need to know why it failed the first time around.

You were the one who brought up assembly.

And stop acting like you don’t know what I am talking about. Syscalls implement operations that are called by someone who has certain permissions and operate on various kinds of objects. Nobody who wants to debug why that call returned “Permission denied” or “File does not exist” without any detail cares that there is hardware several layers of abstraction deeper down that doesn’t know anything about those concepts. Nothing in the hardware forces people to make APIs with bad error reporting.

The unofficial C motto “Make it fast, who gives a shit about correctness”

Returning error codes in-band is the reason for a significant percentage of C bugs and security holes when the return value is used without checking. Something like Rust’s Result type that forces you to distinguish the two cases is much better design here. And no, you are not working with a whole language ecosystem of “sufficiently disciplined programmers” so that nobody ever forgets to check a return value.

Not to mention that errno is just a very broken design in the times of modern thread and event systems, signals, interrupts and all kinds of other ways to produce race conditions and overwrite the errno value before it is checked.

stderr is useless if the syscall already returns a single integer only because of stupid C conventions.

It does very much have the concept of objects as in subject, verb, object of operations implemented in assembly.

As in who (user foo) tried to do what (open/read/write/delete/…) to which object (e.g. which socket, which file, which Linux namespace, which memory mapping,…).

Passing around extra error handling info for the worst case isn’t free, and the worst case doesn’t happen 99.999% of the time.

The case “I want to know why this error happened” is basically 100% of the time when an error actually happens.

And the case of “Permission denied” or similar useless nonsense without any details costing me hours of my life in debugging time that wouldn’t be necessary if it just told me permission for who to do what to which object happens quite regularly.

The lesson to learn is to not hype up shitty company’s products and invest effort into software for their fandom, not to do so elsewhere.