This reminds me of how much “fun” it was to write Blackberry apps back in the day. Whenever you compiled your app, not only did the entire app need to be signed by the RIM servers, each individual module of library code you incorporated into your app had to be signed, so the more shit you added the longer the process took (and signing a single app sometimes took 30-40 minutes or never happened at all because the signing servers were down). I remember once I needed to use the sin() trigonometry function, which forced me to incorporate one of the cryptography library modules, which in turn doubled the amount of time it would take to compile and sign my app - so I ended up writing my own custom sin() function for no good reason at all.
There was a whole website back then called isthesigningserverdown.com (long gone now) devoted to telling you whether the RIM servers were working or not. The only good part about this was that if I ever felt like blowing off work, I would just tell my bosses that the signing server was down and go home.
Ah, but that’s the beauty of employers that are wrapped up in M365: it is always Teams’ fault!
Even if it isn’t actually a problem with Teams, you can just blame it and not a single person will ever second guess you.
Once, my Slack account was deleted due to an error in an automated system, along with everything else, while I was at lunch. That was fun. But not as fun as the 6 months it took until all access was mostly restored.
100% down. My experience with comms security has been such that we were still shitposting on ‘official’ Spam channels with people who had not been employed at that company for months. One of them even slipped up and accidentally dissed one of his former teammates on the project team channel, and that’s when they ejected him from Slack. About 5 months after he quit.
They did love insta-deleting GSuite accounts without switching doc ownerships or transferring associated accounts, effectively annihilating a lot of vital design stuff. Stuff was super-secure after that, I’ll give’em that much!
Ha, at the company I work for they are very fast to turn off access, you could tell someone is gone just by looking at their status
Now, that’s the sensible approach, but we don’ take too kindly to “sensible” 'round these here parts!
Jest aside, I see the point in doing this in cases where the company actually deals with very sensitive stuff, but in terms of average app developing company… meh… Most people are smart enough to know not to share keys and creds, and most people who hang around the ol’ Slack channels for a meme and a laugh really don’t care about said keys or creds.
In my case, I did my 6-year stint in full-on Corpo, then dipped from Start-up to Start-up, and it’s always been the same story.
At a place I worked many years ago I left because I was moving. I still had remote access to the cameras until they upgraded the system.
Worse, they are migrating to Teams this weekend and didn’t inform you.
“It might be time to polish up your resume, Slack appears to be online.”
Is IsSlackDown down? This link isn’t working for me for some reason lol
you may have been fired from the internet
This is why you never trust Jen with the internet.
I definitely didn’t just make it up.
They fixed the glitch.
My programmer friend suspected he was fired when his VPN access cut off. Calling his peer, he got a shrug and a “good luck”.
Dotcoms suck.
“Programmer”
“Humor”
Yes.
