Earlier quoted context omitted.
Are you being deliberately obtuse? It's the contents of the tables that have been ripped off.
Its OAuth documentation - its a very well described standard protocol. Most of the OAuth documentation looks and reads exactly like this. The only "smoking gun" is the "random" value used for the state parameter, which seems to be copied over - and developers copy other products/sites documentation ALL THE TIME. While there is substance in the post that some other company is building the same product, saying that its…
Otonomo, with nearly $55M in funding, is cloning our product
61–70 of 637 posts
Re: Otonomo, with nearly $55M in funding, is cloning our product
#62Lawyer up and take them to the cleaners.
Re: Otonomo, with nearly $55M in funding, is cloning our product
#63Earlier quoted context omitted.
Directly copying a document is simple copyright infringement. Just because it's documentation doesn't mean everyone has a free license to copy and redistribute it. Whether or not any violations occurred in copying code probably depends on whether any employees with company secrets were poached and involved in development. That's a very big, well known no-no amongst tech companies. It's why Compaq had a complete "clea…
Couldn't they have written exactly the same things, taking inspiration ?
> For example, the number of random version-4 UUIDs which need to be generated in order to have a 50% probability of at least one collision is 2.71 quintillion [...] This number is equivalent to generating 1 billion UUIDs per second for about 85 years, and a file containing this many UUIDs, at 16 bytes per UUID, would be about 45 exabytes, many times larger than the largest databases currently in existence, which are on the order of hundreds of petabytes.
https://en.wikipedia.org/wiki/Universally_unique_identifier#...
The probability that they generated the same text 1:1 and a UUID in it by random chance is very, very, very, very slim.
Re: Otonomo, with nearly $55M in funding, is cloning our product
#64Re: Otonomo, with nearly $55M in funding, is cloning our product
#65Earlier quoted context omitted.
Bessemer & Co. would not spend this kind of money without doing DD to the point where their competitive review would have snagged the OP's efforts. So most likely they know.
Sounds like VCs need a plagiarism detector for websites (think TurnItIn) to make sure their portfolio companies aren't blatant ripoffs.
Re: Otonomo, with nearly $55M in funding, is cloning our product
#66Re: Otonomo, with nearly $55M in funding, is cloning our product
#67Looks like the link is down. Is there a mirror?
Re: Otonomo, with nearly $55M in funding, is cloning our product
#68Re: Otonomo, with nearly $55M in funding, is cloning our product
#69Holy crap. The only way forward for Bessemer et al. VCs is to immediately withdraw their funding for this “company” and cut all ties in order to prove that they had no forewarning that this is how their money was being used. There are so few actors this visibly bad that if they didn’t do anything they would become “that guy” everybody avoids, in both the deals and funding space, when orgs do their due diligence. So t…
Bessemer & Co. would not spend this kind of money without doing DD to the point where their competitive review would have snagged the OP's efforts. So most likely they know.
Bessemer & Co. probably don't know that the docs are literally being copied though.
Re: Otonomo, with nearly $55M in funding, is cloning our product
#70Earlier quoted context omitted.
Are you being deliberately obtuse? It's the contents of the tables that have been ripped off.
Its OAuth documentation - its a very well described standard protocol. Most of the OAuth documentation looks and reads exactly like this. The only "smoking gun" is the "random" value used for the state parameter, which seems to be copied over - and developers copy other products/sites documentation ALL THE TIME. While there is substance in the post that some other company is building the same product, saying that its…