My company recently switched to MSFT Teams, and the other day I was thinking how difficult it would be to get spam through teams.
By design, only people part of our organization can communicate with each other. There (AFAIK) is no endpoint for my organizational teams account visible to other teams users outside my organization. For spam to occur, someone's account would need to be compromised (which would be found quickly) or a fake account somehow created by the org admin (which seems unlikely).
With email, the IT department is commonly spoofed, or the president, HR, etc. Most people can spot the differences, but with teams they would virtually never get any fraudulent messages.
Still using it, but most of our major applications have been ported to .NET / SQL Server.
That being said, still some 50+ smaller / departmental style applications that continue to work, and will likely keep running in their current form for the next 10+ years.
In fact, someone asked me a random foxpro question in the middle of typing this comment haha.
If you watch the opening credits of The Expanse, you'll see the moon is almost entirely populated, yet if you look closely at the Earth shot, Tibet is basically dark.
Even in a work of fiction we can't seem to make use of the entire Earth!
Completely unacceptable. In my feedback to the trello team, I basically said that the way this was handled makes it easy for a decision maker to say no.
On top of this, the price isn't remotely competitive. 30-50% of an O365 license, for a single application.
If Fogcreek is dumping Fogbugz, at least they could have made that plain from the start, rather then go through a crap re-branding effort and pretending there was an actual new vision (other than to offload the property).
I guess I'll be investigating new SDLC tools for 2019. It's been a good run of 11 years for Fogbugz (for my team), but I guess the writings on the wall...
By design, only people part of our organization can communicate with each other. There (AFAIK) is no endpoint for my organizational teams account visible to other teams users outside my organization. For spam to occur, someone's account would need to be compromised (which would be found quickly) or a fake account somehow created by the org admin (which seems unlikely).
With email, the IT department is commonly spoofed, or the president, HR, etc. Most people can spot the differences, but with teams they would virtually never get any fraudulent messages.