3 ms·
Have you considered the possibility that someone could get fired for helping you with this? In which case, the Spotify engineer would simply not respond. The S
by vacri 12y ago
Have you considered the possibility that someone could get fired for helping you with this?
In which case, the Spotify engineer would simply not respond. The Spotify engineer is going to be far more aware of corporate culture than the outsider who can't get any info out of them.
Let's not shame people for openly asking questions when they've already tried to solve the problems themselves and also failed when using the 'official' channels.
- umanwizard 12y agoFirst, I wasn't trying to shame him at all. I thought it was an ill-advised thing to try to do, and was explaining why I thought that. That's nowhere near the same thing as "shaming". Second, it's naive to think Spotify engineers are, as a class, immune to the sort of social engineering that would lead people to commit serious policy breaches. If people can be tricked into giving away their social security numbers over the phone, it's not unreasonable to imagine somebody not realizing something was serious that actually (for whatever reason) was.
- vacri 12y agoIf people can be tricked into giving away their social security numbers over the phone isn't quite the same as a question asked openly on Hacker News, hence why I said "openly" - open to community scrutiny. I understand that you don't intend to be shaming, however that's what you're doing: "how can you ask this question, when it might cost someone their job?". We can't all walk on eggshells in order to protect those people who are close enough to the technical core to give technical answers, yet naive enough to not be aware of phishing and/or draconian corporate culture. In short, ask away. If there is a draconian response as a result of your questions, that onus is not on you. And it's not like other phishers will leave that naive person alone simply because you did; they're still going to be a weak link in the chain, and they'll get compromised by someone malicious, and they'll still lose their job next time around while at the same time exposing their company to a malicious actor. Similarly, if we're talking theoretical situations, then how about Spotify management not being jack-booted thugs[1], and when the data breach is found, instead of firing the naif, they use the event to update their corporate policies and retrain all employees with access to privileged information about phishing threats, thereby strengthening the company against future malicious attacks? The naive employee then gains some valuable information on the nature of the world and the company ends up stronger after this benign 'scare'. Win-win all around. [1] I don't actually know what kind of footwear they use
- GREEN-HORNET 12y agoI am new to this site, and by far not the programming and code wizards that many of the people here are. However, I think this is a fair question!? I understand both sides to this "debate", but we are talking about a MAJOR player in the music streaming world,for now, and i would think they should be bending over backwards to not only do what the people want, but also the fact and language that everyone understands=MONEY!!! which means make people want your programs/apps more than the next guy, so I think if enough people bring this up to them, it should be handled, or we will all move on, tech moves fast and someone is ready to take their place, any businessman should know this, so I think it would be in their best interest to LISTEN BETTER to feedback, and definitely for the people who are PAYING for PREMIUM service. just my opinion on it, like i said I'm no programmer.