|
Classic!
I wonder if BB slept in his suit? 
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
I do like the no.19.
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
I expect you also can't have dog with a breed that ends in "...oodle"
|
|
|
|
|
Not only that, but if you have a dog it needs to be blind in one eye.
/ravi
|
|
|
|
|
Maybe, if they have 3 legs, are blind in one eye, and have been shot in Memphis.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
You know what the tombstone of the blues singer said?
"Didn't wake up this morning ..."
|
|
|
|
|
#19 made me laugh out loud. I might add weirdly spelled names like "Saydee" or "La-a" (pronounced Ladasha, the "-" isn't silent).
Hmmm, I own a computer AND a smart phone, but I'm not on Facebook. Does CP count against me? Oh wait, never mind, I'm from Minneapolis, it's only minor depression.
|
|
|
|
|
Ravi Bhavnani wrote: You cannot have the blues in any place that don't get rain.
Ain't dat the trut'. (He said from Phoenix)
|
|
|
|
|
|
I used to play the Blues with my band, along with 60s, 70s,80s, and 90's covers.
I liked items 1 through 20 but disagree with 21. I am living (still) proof of that.
I found the music behind the blues to be repetitive, and rarely listened to the words unless I was the one singing them.
12 bar blues were particularly boring after a while, as only the key and the words would change.
BTW we were semi-pro as we got paid most of the time.
ed
|
|
|
|
|
For sure. In fact there should be a "I got the Facebook blues" song. Mostly satirical, I think.
|
|
|
|
|
This was great stuff. Thanks.
|
|
|
|
|
When the Lord God had created the man, he said to himself: Yes, it fits.
When he then created the woman, he just said: Well, she just has to put on make-up.
|
|
|
|
|
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
When the man checked out the women, he said to himself: Yes, it fits.
|
|
|
|
|
You forgot the third line, where the woman says, "ya, it'll fit," and after looking again at the man, then asks, "but, do you have anything bigger?"
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
|
|
|
|
|
|
It's not an MS problem as much as you would like to think so.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
For anyone offering X as a service products it absolutely is. Giving contractors/freelancers/etc access to your systems is a common enough thing to do; and Company X is far from the only business with and owner either too busy to make the time to remove access for people who should no longer have it or too clueless to understand why he should take a minute to do so.
While I'm neither stupid or unethical enough to take advantage of the access I theoretically have*; if my pc/MS account ever get hacked whoever pwns me is unlikely to have similar scruples about either ransomwaring X's business or spinning up up $100k/day worth of VMs to mine crypto. Beyond that the steady stream of "you need to X" emails I get represent a low level information disclosure vulnerability into X's current setup.
* Theoretical because I have a vague recollection of needing a different password for X's Azure; if so it (and everything else related to X) has been long since deleted from my saved passwords list. On the gripping hand, I've no idea how hard doing a PW reset would be.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
|
|
|
|
|
When a couple split up, the one remaining in the house demands teh key back, or changes the locks to be sure the ex can't get back in.
Failure to get a key back isn't the lock manufacturer's fault - it's "your ex" that has made a mistake and caused a problem.
I'd disagree - it's not MS's problem it's a Company X management problem. Just like when a contractor's contract ends or an employee leaves you revoke their access permissions to the building recover all keys they were issued, they should revoke all permissions to all systems.
MS is right - they can't legitimately revoke permissions as you might be requesting it as a malicious act. Even if they could do it, they don't know that "Joe" has left and "Dan" isn't still an employee you want to make trouble for!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
The account belongs to company X, not MS. It would actually be a crime, I'm sure, if MS helped you get removed from another company's system, without prior written agreement with said company X.
|
|
|
|
|
The actual crime is that by not providing any way for me to stop receiving emails about X's azure, MS is violating the CAN SPAM act.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
|
|
|
|
|
You could write a cease and desist letter threatening further legal action, directed toward company X. That would solve your problem, but it would require some effort on your part.
|
|
|
|
|
Slacker007 wrote: You could write a cease and desist letter threatening further legal action, directed toward company X. That would solve your problem, but it would require some effort on your part.
I had a problem with the company that has programmed the web to access my bank.
I wrote them an email saying about a problem and giving them a couple of ideas to resolve it. The ignored me.
I resent the email some days later, they answered me some weeks later with some "off the book" answers that didn't even correlate to my message.
I sent them more or less the same content a third time and told them that it is not about comfort but about security and that they are not following the european privacy act and they might get accountable for any data leak... the answered me the same day (I saw it next day though) that the changes were already being implemented and that it would go live by the next update...
The issue is still active, and I am really thinking on giving a notice to a customer defense organization (I am not going to start something myself alone against them). If they don't learn being nice...
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Dan Neely wrote: They never removed my access to their Azure for some reason though despite multiple emails between me and my boss and X.
Inform them (via email, with your boss CC:ed) that you've reset your password for that account, and that you're going to snail-mail them the new password on a piece of paper, sent via certified mail, and that you won't be keeping any copy of that document once it's been sent.
Point is, you want to get yourself in a situation where, from that point forward, anything that happens from access through that account is no longer your problem because you cannot access it yourself even if you wanted to.
I suppose the problem is proving you won't keep a copy of the new password (beyond your own claim). But I think you get the idea I'm suggesting.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Elephant | [mastadon]](https://www.codeproject.com/script/Forums/Images/elephant.gif)
part is that their answer was that only the owner of X's Azure can remove me from their account 🤮 and suggested I just spamblock it instead. 
