Automatically updating a Steam user profile Is it legal to automatically update a user profile on Valve's Steam network? I looked through the subscriber and privacy agreements, but couldn't really find anything precise enough about it (or I missed it, I don't know much of law). So is it possible, for example, to make an app that allows people to, say, automatically update their steam profile's bio every day, featuring a unique daily quote, as long as they give their agreement and login credentials, without them actually pressing the &quot;Save&quot; button or anything ? Or is it possible to automatically send comments to other users' profiles if agreement is given? Or is it possible to automatically upload files to the Steam Workshop ? I'm very new to all of this, thanks for reading me out.
Only if you ask Valve for permission first, and they agree in writing. I'm not a lawyer, but when I was reading through the Subscriber license you linked, this stuck out to me: You are entitled to use the Content and Services for your own personal use, but you are not entitled to: (i) sell, grant a security interest in or transfer reproductions of the Content and Services to other parties in any way, nor to rent, lease or license the Content and Services to others without the prior written consent of Valve, except to the extent expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use); (ii) host or provide matchmaking services for the Content and Services or emulate or redirect the communication protocols used by Valve in any network feature of the Content and Services, through protocol emulation, tunneling, modifying or adding components to the Content and Services, use of a utility program or any other techniques now known or hereafter developed, for any purpose including, but not limited to network play over the Internet, network play utilizing commercial or non-commercial gaming networks or as part of content aggregation networks, websites or services, without the prior written consent of Valve; or (iii) exploit the Content and Services or any of its parts for any commercial purpose, except as expressly permitted elsewhere in this Agreement (including any Subscription Terms or Rules of Use). The part that I've bolded is probably the part that makes this against the Terms of Service, since in order to post these sorts of automated messages to their service, you'd need to use a &quot;utility program&quot; to &quot;emulate or redirect the communication protocols used by Valve in any network feature of the Content and Services, through protocol emulation, tunneling, modifying or adding components to the Content and Services&quot;. I doubt that Valve would ever agree, since such a program could very easily be used to create spam bots that works bombard users with unsolicited advertisements, but maybe Valve would be willing to cut deals with AAA video game companies to let them deploy tools to automatically manage their store pages.
You can license the use of your IP only for certain uses, for example (most commonly) &quot;non-commercial&quot;. The general template of permission is &quot;You have permission to ___ as long as you ___&quot;. What the user is permitted to do, in your scheme, is something along the lines of &quot;only distribute the output in this manner&quot;, or &quot;not distribute code developed with this tool anywhere else&quot;. It's up to you to prove that someone violated that condition, if they did.
Copying is illegal, creating an identical work by coincidence isn't. If it is not a criminal case, then a court decides whether it is more likely that the identical work was created by copying or by coincidence. Creating an identical work through a random process isn't going to happen, claiming this would be an awful defense. On the other hand, it is quite possible that two software developers using very stylized code adhering to struct coding conventions can produce quite large bits of identical code. Your links titled "metadata" and "hash" don't actually link to a description of metadata, or the description of a hash, but to a description of torrent files, which is something totally different. Systematically distributing files whose only purpose is the illegal duplication of copyrighted works should not be done without consulting a lawyer, as has been said on other threads (whether posting links to copyrighted files is legal). The chances that a random process will generate a file identical to an existing copyrighted file of say over 100 bytes are virtually zero. If there is an illegal copy of a copyrighted file, and you claim that you created it through a random process and coincidence, you will lose, and deservedly so.
I know that some of this may be covered by either the Creative Commons license or the OGL it was published under, but it's not clear to me how far those freedoms extend. It was all published as materials under copyright to the original authors, TSR, WotC, &amp;c. and if things had been left like that hszmv's answer would've been completely correct: stay vague and allow users to enter those names and descriptions, talk to WotC's lawyers and sales department about license fees, or just keep it to yourself and your friends. You're right, though: WotC went whole-hog, dumped their partial OGL idea, and relicensed some things as Creative Commons. There are different Creative Commons licenses, though, some restricting commercial use that would still keep your app to yourself and friends without a specific licensing agreement. Go find out exactly what WotC put under CC. If it's only the Player's Handbook, then you can only use names and descriptions that are from the Player's Handbook and you're still facing a cease-&amp;-desist if you start adding in Monster Manual info.If it's everything, it's everything they have but still won't include any older modules that they don't have the right to change the copyright status of. It'll still be under copyright, usually until 70 years after the death of the original creator. For Gary Gygax, that'll be 2078. Expect that length to extend during your lifetime though. US copyright usually extends every time Mickey &amp; friends come close to entering the public domain. [Edit: The comments below suggest it might only have been the Systems Reference Document (I assume for 5e). It's 403 pages of not nothing but it's not much given the universe we're talking about. The spell and monster lists are generic. Bigby is nowhere to be found and the only mention of a beholder is a reminder not to use the name beholder without their written approval.] Go find out exactly which CC WotC used. The article above says &quot;all use&quot; but you need to find out the exact number of the Creative Commons license for each thing you're using and make sure all of your uses fall within its terms. Some are basically free use but still insist you mention the copyright holder prominently or in every use. Go ahead and do that if you have to. [Edit: The comments below say it is probably CC 4.0. The SRD download page says you can use CC 4.0 or their own OGL. In both cases, yes, you must acknowledge WotC by name in a way prominent enough to satisfy the license you choose.] And of course, Don't trust legal advice from internet randos or ChatGPT. If this is a serious thing you're going to be spending a good chunk of your life working on or expect to make significant money from, go talk to an actual lawyer. Bonus points for one specialized in IP with a knowledge of roleplaying and the way it's been (partially) opening up lately.If you start off just by talking to WotC's lawyers, just do that somewhere where you get their explanations and permissions in writing. Then keep that somewhere safe in electronic and hard copy. Then still take that with you when you go talk to your own lawyer.
Anyone can sue anyone for anything- you don't need a law that says &quot;user39137 is allowed to sue Microsoft for restarting his PC&quot;. The question is whether you will succeed. You won't, for two reasons. Three if you count the fact that it's trivial to stop updates restarting your PC at inconvenient times. First, you probably agreed to this in the EULA. Updates. The softwareperiodically (sic) checks for system and app updates, and downloads and installs them for you. You may obtain updates only from Microsoft or authorized sources, and Microsoft may need to update your system to provide you with those updates. By accepting this agreement, you agree to receive these types of automatic updates without any additional notice. Windows 10 EULA This likely isn't the only bit where you accept this, but it's the best I could find by skimming with ctrl-f. Obviously if you were to start a lawsuit, you'd want to read the whole thing. Second, to sue someone you need to have suffered damages. &quot;Being annoyed because the computer restarted in the middle of Among Us&quot; isn't really worth anything.
Per the comment, the applicable license term seems to be Licensee agrees to maintain in confidence the source code version of the Licensed Software by using at least the same physical and other security measures as Licensee uses for its own confidential technical information and documentation, but in no case less than reasonable measures. So if your own code is on a physically unconnected thumbprint-secured blah blah blah computer deep in a mountain, with files encrypted, so must theirs be. If yours is stored in &quot;the cloud&quot; with decent password protection, theirs must be as well. This seems to describe your Github use (I don't have any knowledge of the degree of hackability of private Github repositories). The legal judgment as to whether this is &quot;reasonably secure&quot; is based on whether a prudent person would know that it is practical to gain unauthorized access. Protecting a file with the password &quot;password&quot; would probably be found to be unreasonably insecure.
A web site that is serious on protecting some content behind a paywall will put the protected content, or a version of the page with both protected and unprotected content, on separate page or pages, so arranged that a user will not be able to follow the link until that user has signed in and been accepted as an authorized user. A site that merely uses CSS to hide "protected" content is not really protecting it. CSS is designed to be modified by the ultimate user -- that is part of its function. If the site chooses to send you content, you are entitled to read it. Even if some of the content has a CSS tag attached which suppresses or obscures the display of that content, they know perfectly well that any user can supersede this with local CSS, and so I don't see how they have any legal claim, nor any way of knowing if you have accessed the "hidden" content or not. If you attempt to bypass or hack a login screen, that might be circumvention under the US DMCA, or "Unauthorized computer access" under any of several laws.
The agreement linked in the question seems to be or to purport to be, for a non-final, non-production version of the board. I have seen such agreements used, both for hardware and software, used when beta-test versions of products are being distributed to those who agree to do such testing, often in exchange for a reduced price on the final product, or an early look. I have also seen similar language used when an evaluation version of a product is provided free, or at a much reduced price. In such a use, it would be a reasonable contract, it seem to me, and I see no reason why if it were agreed to by both parties in such a situation, it would not be binding. Often such agreements also include a non-disclosure aspect, but this one does not seem to do so. I cannot see how such an agreement could be made applicable automatically, without both parties having chosen to agree to it, and indicated this by signing, clicking, or in some other positive way. I doubt that it could be made automatically applicable, on an "by using this product you agree" basis. I don't know of any physical consumer product, or appliance, sold with such an agreement in ordinary commerce. I am not sure what would happen if a manufacturer wanted to require all purchasers to sign such an agreement. I don't know if it would be binding. I would think that the purchaser's rights under the First Sale doctrice, could be modified by a valid contract agreed to by the purchaser. I do not think that they could simply be revoked by a contract of adhesion, which the purchaser had no choice to decline before making the purchase. As the OP says this was not signed or agreed to in any way, I can't see how it binds the OP.