Not sure if I could fully agree with the root cause analysis, but it sounds about right for Europe as a whole. Things are likely still mostly as their were, with additional steps and reduced demand
He's lying. 42 is a secret code that refers to letters of the alphabet. It's the fourth and second letter: DB
DB is a hidden operation in Germany. It's a large secret society that moves huge metal objects of unknown purpose through the country. Some people have created schedules that indicate where in the country the vessels are expected to be seen - but when you arrive on site, nothing ever happens.
At this point nobody is sure what goal DB is after, but many people assume it's to confuse and frustrate Germans to death.
Not sure if this works for you, but when I'm in a socially confusing situation, I involve people. If you think someone is talking bad about you, ask them about it. Ask for guidance. If you ask someone for help, they will often remember it positively. It takes courage to ask for help, as it's a sign of weakness, and people usually respect that you trust them with your request.
Ideally it will turn out to be a misunderstanding, or you get some constructive criticism, or you get a confirmation that people are actually talking bad about you. At least you will have more clarity. If there wasn't really anything bad going on, now you're still in a conversation. Even if you say thanks and end the conversation, you've broken the ice with that person.
Friends are very much necessary. You need people in your environment, other than your family, to exchange ideas with and talk about things that are on your mind. Don't try to substitute friends with online relationships. It will never be equal. Finding local people with similar interests online is fine if that helps you to reach out. You can't force making friends, it's a waste of time. Start with making one friend. Quality over quantity
I'd be more worried about media than the ability to pirate it.
Music has adapted to generate plays. Platforms are already being polluted with genAI music.
TV was replaced by streaming services. Series come and go and are very specifically tailored to get people to subscribe. Exclusives are the standard. Single season productions are not uncommon. People are also already investigating ways to pollute this pool with genAI as well.
Movies are a stream of Marvel and Disney garbage that was already more CGI than acting. Now genAI and upscaled classics are on the menu.
Piracy will not go away. People used to record movies with camcorders in the cinema, now they pull raw files from CDN nodes. There is always the scene. The platforms that try to profit from the scene come and go.
I wasn't actively aware of this for most of my life until I recently visited a clients office. Buying someone a cup of coffee is an entire thing. There's no free coffee. You have to purchase every single cup. And you first have to walk several minutes to the place where they sell the coffee. It blew my mind. I'm used to drinking one cup after the other without even giving it any thought. Coffee machine right next to me or around the corner. There, coffee incurs friction and cost.
So when you invite someone for a cup of free coffee, this can open doors for you. I'm not kidding. People get all excited when you offer them a coffee break on your dime. And there's levels to it too. There's the regular coffee, and there's the premium one. For the premium you have to walk longer and wait in line until the barista serves you.
It's a key component in office politics when coffee access is regulated.
Why anyone would restrict access to legal stimulants in the office is unclear to me though. Put espresso machines on every desk!
I can't answer this with confidence, but I was thinking the link in the email opened in the default browser, which wasn't Tor in their case. Or something in the email client perhaps. Ultimately, I have no idea what happened and I was just speculating
Depends on the product. It's just something to think about when signaling errors. There is information for the API client developer, there is information for the client code, and there's information for the user of the client. Remembering these distinct concerns, and providing distinct solutions, helps. I don't think there is a single approach that is always correct.
People who used left-pad deserved everything that happened to them. But, very valid point.
There is no honor system. If your code is open for commercial reuse, that's it. If you have any expectations that are not in line with that, then yes pick a different license.
I guess I agree with you, I'm just phrasing it from a different perspective.
I don't necessarily disagree, but I have spent considerable time on this subject and can see merit in decoupling your own error signaling from the HTTP layer.
No matter how you design your API, if you're passing through additional layers, like load balancers and CDNs, you no longer have full control over all responses your clients receive. At this point it may be viable to always signal a successful backend connection with a 200, even if the process resulted in a failure.
Going further, your API may include partial success scenarios, think batch processing, then the result could be a mix of success and failure that doesn't translate to HTTP status.
You could even argue that there is really no reason to couple your API so tightly with a concept of the transport layer it uses.
So you fucked everyone because of a beef you had with AWS. Go fuck yourselves. Moving people off Elastic products is the right move either way. Don't look back.
I really hate it when people call for impromptu meetings and are completely oblivious to what you mention. People are absolutely incapable of bridging mental gaps. Nobody explains common vocabulary. Nobody explains the expected goal of conversation. Nobody evens the playing field. Instead, you watch people confused and asking stupid questions, before they arrive at a constructive mental place, right before the meeting is over.
Communication is art and a skill. Just because someone is talking a lot, doesn't mean they communicate well.
If you can efficiently enable a group of people to arrive in a mental context where they can contribute value to a decision or process, you are a valuable team member.
IMHO this always requires preparation. You can't expect to have a valuable exchange if you yourself can't fully imagine the mental context the other people are in. At every moment you have to understand what might be keeping them from understanding you, and then approaching the specific conflict. "Why don't you understand me?" is something you should never have to ask yourself.
Also, yes, build more prototypes and actually watch some shit go instead of talking so fucking much. Pictures are a thousand words and a real thing is like thousands of pictures. Stop talking already!
Respect the Accept header from the client. If they need JSON, send JSON, otherwise don't.
Repeating an HTTP status code in the body is redundant and error prone. Never do it.
Error codes are great. Ensure to prefix yours and keep them unique.
Error messages can be helpful, but often lead developers to just display them in the frontend, breaking i18n. Some people supply error messages in multiple languages, depending on the Accept-Language header.
There are many ways your real IP can leak, even if you are currently using Tor somehow. If I control the DNS infrastructure of a domain, I can create an arbitrary name in that domain. Like artemis.phishinsite.org, nobody in the world will know that this name exists, the DNS service has never seen a query asking for the IP of that name. Now I send you any link including that domain. You click the link and your OS will query that name through it's network stack. If your network stack is not configured to handle DNS anonymously, this query will leak your real IP, or that of your DNS resolver, which might be your ISP.
Going further, don't deliver an A record on that name. Only deliver a AAAA to force the client down an IPv6 path, revealing a potentially local address.
Just some thoughts. Not sure any of this was applicable to the case.
There are many ways to set up something that could lead to information leakage and people are rarely prepared for it.
I know that that my opponents just love to bring up how I fucked that one couch only that one time very long ago in the past...
👏 👏 👏 OH YEAH YOU DID YOU HORNY COUCH FUCKING ALIEN ASS MOTHERFUCKER HAHAHAHA 👏 👏 👏
That's the one clapping person he was looking at in this picture.