The name of that website is interesting. I had heard of landmarks being named after politicians, laws being nicknamed after them (e.g. obamacare) or after judicial decisions, but it seems that it's usually, at least seemingly, by others. This one is directly named after the president launching it. I can't think of a precedent, was there one?
Incidentally, it was GOP who branded the Affordable Care Act as Obamacare in an effort to make it seem bad. Obama never asked for or wanted that name, although he later accepted it.
Trump, as we know, has an insatiable need for recognition and attempts to put his name on everything he can.
I think that's an OS in the form of a library, like Wine for example. From what I get from the description it allows you to run programs on your real OS and make it see a cut down API to your actual system to reduce the attack surface.
Actor model is one of these things that really seduces me on paper, but my only exposure to it was in my consulting career, and that was to help migrate away from it. The use case seemed particularly adapted (integration of a bunch of remote devices with spotty connection), but it was practically a nightmare to debug... which was a problem since it was buggy.
To be fair, the problem was probably that particular implementation, but I'm wondering if there's any successful rollout of that model at any significant scale out there.
I was in a team that built a bigger telco project for machine to machine communication, using akka actors. It was okayish, the only thing that I hated was how the whole pattern spread through the whole code base
I work on Teams (I know, I know... please don't hit me, it's not my fault)
1. I don't speak authoritatively and
2. I don't have knowledge of the whole product - there's always a rogue team here and there doing stuff.
We've had that feature turned on at MSFT for some time now. It does not allow your manager to see that you're at Starbucks, at home, on the shitter or anything like that. There's a new toggle in the calendar settings called "Share location with my organization", and the settings are: "all details: building, desk, etc.", "general location: office or remote", "can't view any location information". What it does when turned on is just adding, at the top of your calendar, icons that tell you which of your colleagues are in office, and if they share and you click on someone's picture, what building they're in (when it works).
The whole "it will tell your manager what your wifi is" is just baseless extrapolation, and plainly false from what I can tell.
Thanks for showing up to provide some corrective information. I know it can feel like opening a box of yellowjackets, but one of the best things about the HN community is when someone with first-hand knowledge is willing to share what they know.
This is how I expected the feature to work once I read the real product brief, so that's a plus at least. You might want to tell your product people to ask whoever deals with this stuff at Microsoft anymore if they can, like, talk to the press about it? Various outlets have been running stories for almost a year now about how Teams is going to start sending your WiFi data to your boss.
The wording on the product page also makes it sound like tenant administrators will get to decide how opt-in works (ie - that they could select which options the end-user is allowed to pick, and at Microsoft they happened to give you the freedom of choice); this makes sense from my experience in enterprise software management but also makes the feature seem like it will be incredibly yucky/annoying. Is that just a case of poor wording?
This still seems like a super weird feature to push through in terms of "yuck" to "value," but I also know how that goes.
Out of curiosity is this related to the 'emergency location' that we admins have to provide for every calling plan user or is it a wholly separate system? Reading the other comments here they must not realize that teams is already tracking their address because it has to know which PSAP to connect them to.
The emergency location is for 911 dispatch. The theory goes that in the time of wired phones, a call from 212 555 1212 was definitely from the phone on the 11th floor of 60 Hudson Street, so the correct police/fire/ambulance would be obviously in South Manhattan -- but now that we have VOIP and softphones, the phone could be anywhere -- so which 911 point-of-presence should handle it?
I appreciate you having the guts to comment on working on Teams :)
What do you think the coolest small thing coming to Teams people probably aren't aware of is? Anything cool you've worked on that you're allowed to publicly brag about? How'd you end up working on Teams, just the way things kind of went or something along the lines of what you aimed for?
This happens almost EVERY SINGLE TIME there is a sensationalized headline about something I know about deeply. The title or claim in the article will take a option or feature or some industry where something MAYBE possible and state it as a fact for the propose of creating some kind of fear.
Given that not every device has built in GPS, it sounds like the Network Team is going to have to provide the locations of APs for that to work.
Curious how Teams will resolve that. If you're on your phone using a VPN back to your home network will it know or show you as at home? What happens if you have multiple APs at home?
There are public databases of APs. Google reportedly used their Android users to sniff APs (?), and used StreetView vehicles to wardrive. MS can surely pin many APs to user's PII and locations just on the data they already have?
Assuming this is how it functions, the network team would export the list of BSSIDs (I.e. AP+SSID+Band specific wireless MAC used) by location and then there's really nothing about being VPNed in or even having a remote work device which advertises the work Wi-Fi that would create some problem needing to be resolved.
Perhaps it can be derived indirectly, if you have all global positions in the area and can calculate back, with some uncertainty, who is where and when and how.
It's like in Minority Report. Though with not perfect accuracy yet.
You'd probably want to clone the BSSID of one of the APs, the SSID is unlikely to be used as it gives zero context to which office it's at most of the time.
The tenant admin configures that mapping. They can also configure whether the data can be exposed to users outside of the organization. There’s no magic here.
It's not your fault that you chose to work on Teams? Maybe "fault" is not the right word, but it's your choice.
If you think it needs changing, it's in your hands. If you think it's fine to work on Teams, don't apologize.
Maybe it’s not their fault that this feature exists?
Also, about choice: we like to pretend that people are free to choose where they work. They are; if there are no blocking consequences to that choice. For example, between working at Microsoft and letting my family starve? Well, I’ll bite the bullet. The market isn’t amazing, we can be much kinder on people for where they work.
1. VeryGoodCorp builds a "harmless" feature that's super useful and maybe even opt-in. Only privacy-nuts object to it.
2. The feature is in fact useful, so most people enable it. It may even become company policy to have it enabled.
3. Companies who buy this feature ask for a way to force their employees to use it, as it's "confusing" if location data is only available for 90% of the employees. Not it's an opt-out feature, in the best case.
4. VeryGoodCorp is in a bit of trouble with its shareholders. Revenue growth hasn't been as great lately. They realize that they are sitting on a mountain of location data, aggregated from multiple harmless features, that would tell its customers if their employees are slacking off at work. Surprisingly, the customers are willing to pay good money for a "employee productivity score".
5. Profit..
Edit: formatting
Edit 2: Now you may say "well that wouldn't be legal", and depending on the jurisdiction I'm sure it isn't. But that hasn't kept VeryGoodCorp from collecting this data, they just forgot to turn off the toggle for EU you know, honest mistake. But they still have the data, and laws can change, or, you know, made to change.. (Prop 22 anyone?)
So it only lets Microsoft know people's exact location -- how close is Microsoft to the Trump regime? Nadella has apparently gifted Trump millions?
Why in the f does Word need my location (access to location services) for me to write a document? Pops up every time.
Teams already has a location setting, if you wanted to automate that a more correct way would seem to be adding the feature and offering users the opportunity to turn it on. Microsoft hasn't really changed since the IE days it seems.
It seems like people go out of their way to find something Microsoft, Apple, etc do everyday to get outraged about. Always appreciate someone from the source correcting misinformation and putting it into perspective.
I cut coffee for over 6 months, and one of the most significant thing it did for me is that, when I resumed, I noticed that caffeine actually helped me feel more awake and alert (while I didn't notice any effect when taking a lot of it before stopping cold-turkey)
reply