Ask HN: Take down my reverse-engineered Snapchat lib because they asked?
31–40 of 137 posts
Re: Ask HN: Take down my reverse-engineered Snapchat lib because they asked?
#32I don't know anything about the Snapchat API but if it's simply undocumented I don't see how that would be a "technological measure" of "effective control."
If you had to sniff or crack an API key of some sort, maybe that does.
In any event, it seems like a friendly enough request, maybe take it down as a courtesy pending their clarifying exactly what "technological measure" of "effective control" they think it "circumvents." Depending on their response and how much you think you want to push it, you can then decide what to do.
Re: Ask HN: Take down my reverse-engineered Snapchat lib because they asked?
#33I persume they can't file a lawsuit without filing DMCA takedown notice first?
If so, when they'll file the notice, GitHub'll take it down (as they usually do). Then you may consider filing counter-notice (if you can afford legal action) or, I guess (IMNAL!) ignore the whole affair.
Anyway, you'd better consult a lawyer.
Re: Ask HN: Take down my reverse-engineered Snapchat lib because they asked?
#34I hate to play devil's advocate here (especially since I already have a post here) but I had a thought. For Snapchat some of the biggest selling points are the self destruct abilities of the media sent. So an unauthorized client puts a stake trough the heart of that claim (and the company). I see why they may be worried, but I think that they should have communicated their concerns more clearly and pleading, and not…
Re: Ask HN: Take down my reverse-engineered Snapchat lib because they asked?
#35I hate to play devil's advocate here (especially since I already have a post here) but I had a thought. For Snapchat some of the biggest selling points are the self destruct abilities of the media sent. So an unauthorized client puts a stake trough the heart of that claim (and the company). I see why they may be worried, but I think that they should have communicated their concerns more clearly and pleading, and not…
Re: Ask HN: Take down my reverse-engineered Snapchat lib because they asked?
#36Re: Ask HN: Take down my reverse-engineered Snapchat lib because they asked?
#37It is all well and good to write these sorts of things as a demo, but distribution is something where I would defer to the actual owner of the API in question.
After all, how many of us would want someone creating an unauthorized library to a private API that we don't wish to have public?
Re: Ask HN: Take down my reverse-engineered Snapchat lib because they asked?
#38Morally, I would take it down. It is all well and good to write these sorts of things as a demo, but distribution is something where I would defer to the actual owner of the API in question. After all, how many of us would want someone creating an unauthorized library to a private API that we don't wish to have public?
https://www.eff.org/deeplinks/2012/05/no-copyrights-apis-jud...
Re: Ask HN: Take down my reverse-engineered Snapchat lib because they asked?
#39Ignore 99% of the responses in this thread, particularly any that say "I think...", "It seems fair...", and so on. You're in a legal situation here, if you are worried, contact a lawyer.