The disclaimer doesn't really matter, as 1) we wouldn't really expect that many people to read it and 2) it is going to get used in a ton of contexts without th

The disclaimer doesn't really matter, as 1) we wouldn't really expect that many people to read it and 2) it is going to get used in a ton of contexts without that disclaimer... such as in the headline of this Hacker News post. I can't make a company "Apple Computer Backstage" and just put a little note on my website that says "Apple Computer Backstage has no involvement with Apple Computer". This project simply should not have "YouTube" in its name... or, if it absolutely must, it at least needs to be on the other side of some kind of preposition. This insistence upon using other peoples' trademarks in the names of third-party clients based on adversarial interoperability--something that the company often has every reason to "throw the book at" as it is inherently hostile--is what ends up killing the vast majority of these projects over time. This isn't "in for a penny, in for a pound": you need to carefully choose your battles, and flagrantly violating someone's trademarks is going to be your weakest link as it is such low hanging legal fruit and doesn't actually buy you anything.