4 ms·
Yep, we didn't write our own encoder - we evaluated and licensed a third party encoder. Article edited to make this more clear. The problem (at this point at le
by jon_dahl 15y ago
Yep, we didn't write our own encoder - we evaluated and licensed a third party encoder. Article edited to make this more clear. The problem (at this point at least) is that our software licensing agreement with the third party includes confidentiality, so we can't name the software without permission. Stupid, I know. But you can probably guess, or figure out, what it is. ;)
- wmf 15y agoI've seen confidentiality the other way (where a vendor can't say who their customers are) but why would someone not want a customer to tell the world how great their software is?
- sanswork 15y agoOnly reason I can think is that if the customer messes up the implementation and creates a subpar service with it then it reflects poorly on the source provider. Actually another reason might be that the source provider doesn't want other users to know about each other to compare licensing agreements and such.
- nfriedly 15y agoI'd guess it was written by a lawyer who was more concerned about a customer telling the world how great their software isn't. And a blanket "do not mention" statement is probably safer than a "do not mention negatively".