The indemnification for IP is a standard term that exists in all SaaS terms. What it's saying is "if you upload copyrighted/infringing material to our service and someone sues us because of it, you have to pay our legal costs since we had nothing to do with it".

This is a pretty reasonable thing, you're the one who uploaded the material, you're responsible for it, especially since zoom isn't checking/filtering what you upload/share.

even worse, they turned down a buyout offer back in February for $16B https://www.reuters.com/business/zendesk-rejects-16-bln-offe...

Other folks have already pointed out how this is unenforceable, but I'll give a very tangible example.

Twitter (and Instagram) ToS prohibit selling handles and yet I've been on both sides of those transactions before. You just offer the person a "consulting" contract, part of which is delivering the handle

This is basically https://www.taxact.com, minus #4

Tesla dwarfs everybody else combined: https://cleantechnica.com/2021/02/08/2020-us-electric-vehicl...

Yep, this is definitely an intentional design decision, it renders that way on all iPhones

Yes but that's not records that they actually have. The reason you need a wake word is because that processing is done locally on the device, it's not until you say the wake word that it starts streaming the audio data to the central server for processing.

Its certainly possible for Amazon/Google/Whoever to send your device a firmware update that turns it into an always-on microphone, but it doesn't do that by default

Two problems with that approach at large scale shows:

1) These days the cabling is run inside a run of barricade bisecting the crowd, so it's in a secure area the entire time

2) Modern PA systems at shows of that size have almost exclusively moved to digital snakes / audio networks, not analog

To realistically pull that off you'd need production access to the event to tap into the audio network and re-route things. That said, given the number of people with appropriate access and the fact that InfoSec isn't a high priority, that actually seems pretty doable.

Once they realized what was going on though, a few breakers flipped would drop power to the amps or speakers (depending on whether using powered or passive arrays) and it would be over (which would happen pretty quickly since the power distro is very well organized and labeled since quick troubleshooting is often necessary).

For context, I'm the GM of the Enterprise Team at Stack Overflow and have been working on it since we launched our full Enterprise product about 18 months ago.

Enterprise is intended for large teams (at least 500 tech staff) who want to have their own completely isolated and standalone Stack Overflow community that can be run on-prem or in a private cloud. Enterprise deployments have full control over the system and also get support from our Customer Success team to build up their community using all the lessons we've learned in 8+ years of building communities. As part of this we have all those features you'd expect like integration with SSO, audibility, massive 50 page contracts, etc

Channels on the other hand is meant for smaller teams (all the way down to just 2 people) who want to store their own knowledge (privately and securely) alongside the the public knowledgebase at stackoverflow.com. Any size team will be able to just walk up, put down their credit card and instantly be sharing knowledge with each other.

So the two products are very complimentary to each other, just depends on your team size and exactly what you're looking for feature wise.