5 ms·
I just had nightmares of internal corporate instances. >Mastodon by Teams (tm), please log in with your active directory credentials to see the latest posts fr
by MonkeyMalarky 4y ago
I just had nightmares of internal corporate instances.
>Mastodon by Teams (tm), please log in with your active directory credentials to see the latest posts from HR!
- trelane 4y agoAt least they'd (Microsoft) have to make the changes publicly available, since it's AGPL. So they can't have secret shenanigans that others don't have.
- doctor_eval 4y agoGenuinely don’t understand. Is the ActivityPub protocol AGPL? Is there something stopping MS from just building their own server from scratch?
- codefreakxff 4y agoThey would also make a Microsoft owned version of the protocol to support features only their client and server supported
- sitkack 4y agoWhy wouldn't they just implement SOAP over JSON?
- esarbe 4y agoActivityPup is an API. APIs are not protected by copyright.
- fragmede 4y agoThe AGPL only applies if they make it available externally though. If they have their own internal instance the AGPL only says that Microsoft employees must be able to access the source code.
- mr_toad 4y agoMicrosoft hosts teams for their customers. So if they modified the code all their customers users would be entitled to see it.
- LinuxBender 4y agoWhile I agree with this, I've interfaced with many lawyers that interpret AGPL differently mostly due to following license dependency trees. They nuked any project that went anywhere near AGPL even if the project was internal-only. This was not limited to places I worked either. There are others in my circle that had their projects shot down for using AGPL code. I do not fully grasp the logic the lawyers arrive at. Perhaps they are treating it the same way I treated PCI compliance, in that anything touching it gets infected by the zombie virus and must also be compliant.
- JAlexoid 4y agohttps://www.w3.org/TR/activitypub/ https://www.w3.org/TR/activitypub/ - It's not AGPL
- alisonatwork 4y agoThis already existed. It was called Yammer, and nobody used it, and then Microsoft bought it anyway. Apparently it's rolled into Teams now, but since my last few companies were Slack shops I don't know how many people use the Teams-branded Yammer feature. Probably still nobody. Unlike chat, email and wiki, I don't think microblogging has ever proved to be useful in the workplace.
- lmm 4y agoYammer was pretty nice for what it did. It felt more structured and formal than Slack, but wasn't as painful to edit as wikis tend to be.
- happymellon 4y agoTeams is already more structured and formal than slack. And it's an absolute pain to send team messages. Everyone always just starts a group chat instead, as the reply is always so small and hidden, and the card system makes it hard to manage more than one or two threads at a time.
- Angostura 4y agoYammer is separate from Teams, still
- ekianjo 4y ago> Apparently it's rolled into Teams now Yes, and still nobody uses it
- jackvalentine 4y agoIt is absolutely massive at my org. The comms team religiously using it, and the ‘what’s happening’ digest being on by default meaning posts are surfaced in to people’s inboxes regularly until they unsubscribe means everyone knows about it.
- MattDemers 4y agoOddly, I know a few EVE Online corporations used it.
- selfhoster11 4y agoThat don’t sound too bad. I would use it, if it meant avoiding the Teams client application.