Ask HN: Take down my reverse-engineered Snapchat lib because they asked?
21–30 of 137 posts
Re: Ask HN: Take down my reverse-engineered Snapchat lib because they asked?
#22Re: Ask HN: Take down my reverse-engineered Snapchat lib because they asked?
#23A lot of times when you use a product, you're required to agree to an EULA wherein you promise/commit to not reverse engineer a product or its protocols. If you did use snapchat as a registered user, this issue could affect you negatively. Another alternative is to mail them back and ask them for clarification. Why do they consider it an infringement? The law clearly states the following: (2) No person shall manufact…
Re: Ask HN: Take down my reverse-engineered Snapchat lib because they asked?
#24Re: Ask HN: Take down my reverse-engineered Snapchat lib because they asked?
#25I would seek a lawyer if you can afford one and if not, then you can't afford a lawsuit either, so in this case, pull it offline. If you do the latter, you should post the results of your research somewhere, this can't be taken down as it is sharing information and not an API tool.
Re: Ask HN: Take down my reverse-engineered Snapchat lib because they asked?
#26Re: Ask HN: Take down my reverse-engineered Snapchat lib because they asked?
#27Earlier quoted context omitted.
Asking for moral advice when you need legal advice isn't a good idea. The two are often conflicting.
Save the lecturing, you don't know if he needs legal advice. Maybe he has already gotten legal advice.
> I am under the impression that reverse engineering is still protected under fair use doctrines. Is this the case? How should I respond, if at all?
Speaking as someone who has been involved in an arduous civil matter for the last four years, matmaroon's advice would be well heeded.
Re: Ask HN: Take down my reverse-engineered Snapchat lib because they asked?
#28As with file formats, the notion that network protocols & APIs should ever be granted any type of protection and that no-one other than the creators should be able to write software that conforms to these protocols is ridiculous.
Snapchat, in my view, have every right to restrict who uses their service and in what manner - via standard mechanisms like API keys and login credentials. But preventing third-party implementations of protocols or APIs is so 90s. Oracle had a bit of trouble with this recently.
One problem I'm personally trying to remedy is the proliferation of various APIs and protocols for accessing various online storage services (Dropbox, Google Drive, Box etc) by developing an SDK that supports all of them. We need more of this kind of these kinds of projects, not less.
Micah Schaffer, if you're reading this, you're welcome to send me a takedown request and discuss the issue with me. My email address is in my profile.
EDIT: It's at 62 now. I wouldn't be surprised if even Barbra Streisand has forked it.