Making a breaking change to the mobile API also breaks old outdated installations of the app. Websites and their APIs are usually synced, apps not so.
If they were really motivated to stop your method, they could just obfuscate the frontend with webpack and break your scraper every time they make an update.
I suspect that any of the methods proposed here would be prone to a C&D, but IMO the safest legally would probably be the RSS method (not a lawyer though). Reddit's RSS feeds are public, documented, and available without the need for private APIs, authentication, or an API key, so I don't see how they could claim that a wrapper is unauthorised/illegal. Documenting their private API however seems like a gray area. Google LLC v. Oracle America, Inc. found that APIs are copyrightable, but this use may constitute fair use.
Is there a reason you're scraping data rather than attaching a network sniffer/reverse engineering the official apps and documenting the results? Or map the RSS feed to an API? The main thrust behind my comment is that I think scraping is pretty fragile, so I'm interested as to why other options are infeasible.
If by conversation you mean asking for a word by describing it conceptually because I can't remember, every day. If you mean telling it about my day and hobbies, never.
Bundaberg Spiced Ginger Beer
I think the Rabbit R1 is an underbaked and dumb product. That said, Rabbit would have had to have had a few too many kicks to the head if they seriously considered not just running Android under the hood. Android is open source, and there is no good reason to not utilize the hundreds of millions of dollars that Google has already poured into developing mature a mature operating system with all the drivers and frameworks they need.
As a moderator of a couple communities, some basic/copypasta misbehaviour is caught by automated bots that I largely had to bootstrap or heavily modify myself. Near everything else has to be manually reviewed, which obviously isn't particularly sustainable in the long term.
Improving the situation is a complex issue, since these kinds of tools often require a level of secrecy incompatible with FOSS principles to work effectively. If you publicly publish your model/algorithm for detecting spam, spammers will simply craft their content to avoid it by testing against it. This problem extends to accessing third party tools, such as specialised tools Microsoft and Google provide for identifying and reporting CSAM content to authorities. They are generally unwilling to provision their service to small actors, IMO in an attempt to stop producers themselves testing and manipulating their content to subvert the tool.
The computer is probably locked down and all software/os provisioned by their IT department
This is the comment that tipped the maintainer over the edge:
ayan4m1
You should do a better job updating your documentation so that people do not waste their time like I did. This change to closed source was announced where, exactly? All of your READMEs and documentation sites do not mention this. Very easy to be confused and very disappointing to me that this went closed-source.
Not only did you sell out, you also removed all the old versions that were released under an open source license so that others couldn't continue to use out-of-support versions. DISGUSTING.
tl;dr get off GitHub and npm entirely if you want to do the closed-source thing, kthx.
Which is incredibly disrespectful in my opinion, and this kind of entitlement is what makes me weary of starting any open source projects.
Seattle and Redmond. So Amazon and Microsoft?
Just use Kotlin
Mozilla's next largest source of revenue is subscriptions and advertising (source 2021 financial report), by a wide margin. That "useless shit" is their other revenue, and they're investing in it because they know they need to diversify revenue to fund Firefox. You're suggesting they kill it because it's not their core (unprofitable) business?