gencha

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!

There is also https://en.m.wikipedia.org/wiki/Auschwitz_Album and https://en.m.wikipedia.org/wiki/Nazi_Concentration_Camps_(film)

The latter hits hard. Unbelievable images. Luckily not in color.

Can be watched at https://www.spiegel.de/geschichte/was-die-deutschen-nicht-sehen-wollten-a-9e63991b-cd26-4169-9fe8-bb118bf404e4 if that's not geoblocked.

https://en.wikipedia.org/wiki/H%C3%B6cker_Album is also noteworthy.

Da stimme ich allerdings auch in allen Punkten zu. Man kann sich auch etwas Zeit lassen bis Informationen gesichert sind. Und den Punkt mit Alkohol finde ich auch sehr interessant. Den Gedanken hatte ich bisher noch gar nicht. Finde ich eigentlich auch extrem hilfreich zur Einordnung.

The only time I came across this subject was when there were malicious commits in a code base. When else would this matter? The commit contains your name and email address. Who cares about time zone? Just as anything in a commit, these metadata can be freely manipulated and serve purely as information for other developers. Who are you scared of seeing your time zone in a commit on a seemingly public code repository? This is such a pointless non-discovery

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.

Agreed. There are countermeasures to take against everything I mentioned. You just have to be aware and ideally not be a criminal in the first place.

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.

Ich finde daran auch irgendwie gar nicht mehr das Problem. Wenn ein Tourist aus Russland oder Afghanistan in Deutschland jemanden umbringt, dann darf man das doch erwähnen. Das ist für mich schon was anderes als wenn das jemand mit deutscher Staatsangehörigkeit macht.

Wenn ein Nawalny in Deutschland von Ausländern vergiftet wird, dann ist die Information scheinbar rein. Aber wenn ein Syrer jemanden ersticht, dann ist die Information scheinbar gleich rassistisch belegt.

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.