Would I be violating terms of service if I asked for permission but got no reply? I created a Python API wrapper for a service, which I want to release as an open source python package if possible but not necessarily, the main issue is that I have a small python project where I need to use their API, not too many requests, if I could release it, that's better. The company is in my country, Lebanon The company's terms of service forbid me from doing so, but they don't offer a python wrapper in the first place. The company has two founders, one left and one works at google, I tweeted the first, sent a LinkedIn message to the second, asking for permission got no reply. The company has two email addresses, I sent emails to both addresses got no reply. If the worst case scenario is them blocking my IP address, that's fine, but I wonder if they would be able to pursue legal actions against me even though I went above and beyond trying to ask for their permission without being able to reach them. Am I still violating their terms of service?\ For example if you use Google translate API for free, you are also violating their TOS, they only block your IP if they detect a large number of API requests and never sue the writer of the library, you could find many free Google translate libraries.
No. You need to actively be given permission for you to have permission. If they don't reply you don't have permission and are violating their ToS.
IANAL, just a programmer with an interest in legal rules. Due to the very permissive nature of the MIT license, no, it does not appear that anything illegal has been done. Specifically, the section to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software (emphasis mine) grants everyone the right to modify your code and share those modifications, provided one includes the license. Since this person has included your license (including your copyright notice), they have followed the conditions of the license and are able to share your stuff. Legally. Ethically, I still think its ****. This might be a good starting point in selecting a license (note the Modification column). https://en.wikipedia.org/wiki/Comparison_of_free_and_open-source_software_licenses The CC-BY-SA license family, as mentioned by Ron Beyer in comments is on this list, for example. TL;DR: You unfortunately granted a more permissive license than what you wanted/needed to. This was a BadThing(TM), analogous to giving too broad of access rights to a method or class. Determine your desired permissions, then select a license that matches what you'd like to grant.
See https://stackoverflow.com/legal/terms-of-service and https://law.stackexchange.com/help/licensing. As with most social media sites, your contribution of content does not transfer ownership of any copyright in the content; rather, you grant to the platform a non-exclusive license. Because the license is not exclusive, you can grant similar or different licenses to other parties, which generally happens when you post the same content on other sites. (Of course, you can only grant licenses when you own the copyright or have a license that allows you to grant a further license, so posting content created by others can be complicated; this seems to be beyond the scope of the question, though, so I mention it only in passing.) To answer with respect to a specific site, of course, you have to look at the site's terms of service.
There are a number of misconceptions here. GDPR does not generally impose blanket bans, but things get dicey if you're using data in a way that is not strictly necessary. Consent (freely given opt-in) is a way to continue nevertheless. A website without ads, tracking, or potentially tracking embedded content can probably work without having to ask for consent. Under the GDPR, every processing of personal data needs a purpose. This purpose must be covered by a legal basis. Some processing might be legally mandated or required by a contract with the data subject. It's also possible to base processing on a legitimate interest, but this requires a balancing test that also considers the data subject's rights and interests. As a last resort, consent can be an appropriate legal basis, but this comes with additional restrictions. Once you have a clear purpose that is covered by a legal basis, you can process the minimum data necessary to achieve the purpose. Sometimes, laws prescribe a particular legal basis. This is the case for cookies. You can use cookies (and similar technologies that access information on the end user's device) as strictly necessary to provide a service explicitly requested by the user. If you go beyond that, the ePrivacy Directive says you must obtain consent first. So for example, session cookies, shopping carts, or cookies that remember a “dark mode” preference are all perfectly fine because they are strictly necessary for something the user is trying to do. Also, you can use cookies to remember if the user gave or declined consent. On the other hand, analytics or tracking cookies are not necessary and require consent. If a website embeds third party content, this discloses personal data such as IP addresses to the third party. This disclosure requires a legal basis, most likely consent. There is case law about this regarding Facebook Like buttons on a page (→ Fashion ID case) but the same principle can be generalized to embedded Tweets or Youtube videos, images, or JavaScript files. A common way to handle this is to replace the embedded content with a placeholder, and to only load the embed once the user gives consent. But not all other domains or services are “third party” in the sense of the GDPR. When you engage a company to act as a data processor on your behalf, they are contractually bound to only use the data as instructed by you, and not for their own purposes. The GDPR allows you to outsource processing activities such as serving web content, as long as you have a suitable contract in place. Such “data processing agreements” are common for hosting providers or CDNs. When consent is to be used as a legal basis, it's important to consider the various conditions that the GDPR imposes (see Art 7 GDPR). The core principle is that consent must be freely given. You cannot make access to a site conditional on consent, so a naïve cookie wall or captive portal will be non-compliant. It's fine to force a choice, but “no” MUST be valid and possible. That consent is freely given also means that you must provide enough context for the user to make an informed decision, that the user must give consent through an unambiguous, affirmative action (consent is never the default), and that consent must be specific for a particular purpose (you can't bundle unrelated purposes). That is why modern consent management tools have multiple layers of information and allow the user to give consent for individual purposes (e.g. yes to analytics but no to ad personalization). In your particular context, you could proceed as follows: Figure out what kind of external content you're currently including. Can you enter into a data processing agreement with the external providers? If so, sign that. Can you host the content locally? This can be an easy solution except for video streams. Careful: copyright concerns might make this impossible. Can you replace the content with placeholders that only load if and when the user gives consent? That way, the rest of your site remains accessible without annoying consent walls. If the third party content is an unavoidable and essential part of your page, use an interstitial to inform the user of the risks before they proceed.
The second paragraph is an invitation for people who don't want to follow the terms of the GPL (e.g. who want to incorporate it into a larger closed-source work, or make closed-source modifications) to contact XXX for a less onerous (but more expensive) license. That would require that XXX have full rights to the software, that they did not for instance incorporate others' GPLed code. It would be a stretch to read the second paragraph as attempting to limit the first paragraph, particularly given the &quot;please&quot;.
You have the right to request anything you want, but there is a very limited set of things that you can have a legal expectation of them doing. The service provider has no obligation to block a user. You can likewise request a report, and from a pirate site I would expect no response. There is no legal requirement that a pirate site block an offending user after a certain number of offenses. There is no direct way to compel a pirate site to ban a user. Indirectly you might accomplish that end if you take legal action against the site, which causes them to ban a user in order to protect themselves If a DMCA request was not "proper" (the correct legal form) they will not perform a takedown, and may not inform you that they won't. Make sure your takedown request is legally correct and actually delivered to the correct person. If they still ignore your request, they will have lost the "safe harbor" provisions, and you can theoretically sue them. Since the pirate site presumably only hosts a link to elsewhere, their making public such a link is not itself copyright infringement, so you need to be going after the ISPs who manage the actual host sites. The pirate site might still be a contributor to infringement, along MGM v. Grokster lines. A standard defense against infringement would be "We had no idea", and ignoring DMCA takedown notices is clear proof that they did have an idea. That's basically what DMCA takedown is about: saying what it takes to use the "We had no idea" defense.
It is not clear from your question whether you intend to make use of the Yelp API to display Yelp ratings on your own website. You ask: So is my idea fair use of these websites data or is not because of the TOS? The ToS is not for Yelp data, it is for the Yelp API. The ToS will only apply to you if you agree to it. However, if you agree to the ToS for the API, fair use is irrelevant. The ToS is a legally binding contract that trumps fair use. You also brings up Google's display of Yelp stars. This display is not based on the Google using the Yelp API, but on Yelp opting in on a mechansim created by Google called Rich Snippets. Returning to Yelp ToS, it is clear that its purpose is permit re-use of their "ratings, reviews, photos" etc. by to promote your own Yelp-rated business. Also what they clearly do not allow you do do, is to build a competitor to Yelp. Since your planned restaurant rating site would compete with Yelp, you will not be able to use the Yelp API to get the data. What if you didn't use the Yelp API, but simply scraped their site - would fair use apply? What constitutes fair use in borderline cases such as yours is mainly decided by case law. Case law differs from jurisdiction to jurisdiction. My general impression is that it is not fair use if the use is commercial in nature (i.e. you create something intended to directly compete with the site you scrape the data from) and your product or service does not communicate something new and different from the original or expands its utility. As always: If you want specific advice, hire a lawyer.
You Own The Code To answer your question on whether or not it is copyright infringement: Yes, you do own the rights to the written code but posting it on Github gives Github the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it. To simply put it, no matter what license you use, you give GitHub the right to host your code and to use your code to improve their products and features. This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive your Content. So with respect to code that’s already on GitHub, I think the answer to the question of copyright infringement is fairly straightforward. Things aren’t quite as clear-cut in a scenario where Copilot is trained on code that is hosted outside of GitHub. In that situation, the copyright infringement question would hinge largely on the concept of fair use. If Copilot is being trained on code outside of GitHub, we accept that at least some of what they’re looking at is copyrightable work. So, the question then becomes if it’s fair use. Now, you ultimately can’t conclude definitively that something is fair use until you go to court and a judge agrees with your assessment. But I think there’s a strong case to be made that Copilot’s use of code is very transformative, a point which would favor the fair use argument. There is precedent for this sort of situation. Take the case of Google Books, for example. Google scanned millions of books, provided people who were doing research with the ability to search the book, and provided the user a small snippet of the text that the user was searching for in the book itself. The court did in fact find that was fair use. The use was very transformative. It allowed people to search millions of books. It didn’t substitute for the book itself. It didn’t really take away anything from the copyright holders; in fact, it made it easier for readers to access the work and actually opened a broader market for book authors. And, it was a huge value add on top of the copyrighted corpus. In the latter scenario, a lot depends on the thoroughness and the length of Copilot’s suggestions. The more complex and lengthy the suggestion, the more likely it has some sort of copyrightable expression. If a suggestion is short enough, the fact that it repeats something in someone else’s code may not make it copyrightable expression. There’s also the question of whether what’s being produced is actually a copy of what’s in the corpus. That’s a little unclear right now. GitHub reports that Copilot is mostly producing brand-new material, only regurgitating copies of learned code 0.1% of the time. But, we have seen certain examples online of the suggestions and those suggestions include fairly large amounts of code and code that clearly is being copied because it even includes comments from the original source code.