Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)VO
Posts
0
Comments
46
Joined
2 yr. ago

  • To be fair, he doesn't have a title or any official position of power. His mother already had him when she met and later married the crown prince of Norway. But everyone in Norway knows who he is and he's definitely very privileged, so he may have abused that fact..

  • Not where I work. My thinkpad is managed by the understaffed IT department, and is severely crippled by clownstrike and other garbage and bloatware. Linux is not allowed, only windows.

    But my colleagues who chose a MacBook don't have all that crap because said IT department haven't figured out how to remotely manage Macs yet...

  • I suggest changing it slightly to POTUSITO - President of the United States In Title Only.

    Has the added bonus of -ito being a diminutive suffix in Spanish, and probably many related languages, so afaik one could read it as "little POTUS" 😁

  • You should also say/yell "I do not consent!", because it's illegal to search or arrest someone without their consent. It was a popular spell a few years ago, but I don't see it being used much anymore, so it's possible that the cops have found a counterspell. 😉

  • Not an expert, but the only thing I can imagine is that it's related to certificates or keypairs used for encrypted communication / authentication. Afaik ssl certificates can be issued to a given company, for example, and might become invalid when that company no longer exists. Or it becomes impossible to issue new ones.

    Something in that vein, maybe.

  • Had a similar thing at work not long ago.

    A newly deployed version of a component in our system was only partially working, and the failures seemed to be random. It's a distributed system, so the error could be in many places. After reading the logs for a while I realized that only some messages were coming through (via a message queue) to this component, which made no sense. The old version (on a different server) had been stopped, I had verified it myself days earlier.

    Turns out that the server with the old version had been rebooted in the meantime, therefore the old component had started running again, and was listening to the same message queue! So it was fairly random which one actually received each message in the queue 😂

    Problem solved by stopping the old container again and removing it completely so it wouldn't start again at the next boot.