Hacker News new | ask | show | jobs
by DannyBee 4688 days ago
Why?

How is this any different than me releasing my code under something like the LGPL, which would allow those folks who dynamically link to not release source to their app, but force those who are required to statically link (due to platform or other reasons) to release source to their app?

Note that it's a similar situation. If I release code under the LGPL, i don't have to abide by it, only others do.

Twitter requires third party API users limit themselves to 100k users (or whatever it is), but, even though they use the same API, does not require it of itself.

They also have decided some folks don't have to abide by this.

How is this different?

None of this is "anti-competitive" behavior.

Would you think it anti-competitive behavior if Google provided no API and also told people finding ways to embed it to stop?

1 comments

It's anticompetitive because Google is using its dominant online video platform to promote its mobile OS, even though those are really two separate industries. It's no different from MS selling an internet server that uses nonstandard extensions and only making those available on windows.
This is honestly the silliest thing i've ever heard in my life.