Mildly Infuriating
Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that.
I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!
It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means: -No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
7. Content should match the theme of this community.
-Content should be Mildly infuriating.
-At this time we permit content that is infuriating until an infuriating community is made available.
...
8. Reposting of Reddit content is permitted, try to credit the OC.
-Please consider crediting the OC when reposting content. A name of the user or a link to the original post is sufficient.
...
...
Also check out:
Partnered Communities:
Reach out to LillianVS for inclusion on the sidebar.
All communities included on the sidebar are to be made in compliance with the instance rules.
view the rest of the comments
They just don't want to go through the hassle of securing their api, so they're trying to strong arm the devs into dropping the project.
It would be laughably easy for them to kill this, but maybe their devs aren't competent enough to do it.
This seems like the answer. If there is no proprietary code and they did not actually reverse-engineer patented technology, I doubt they have a leg to stand on.
It costs nothing to threaten to sue, and it sometimes works.
afaik reverse engineering is generally legal so long as the person prosecuting you can't prove you used insider knowledge
This is why things like game system emulators are generally fine
Reverse engineering is legal, but if you still arrive at a solution covered by a patent, then that solution is illegal. But this shouldn't be covered by a patent.
Software patents isn't a thing in Europe, so that doesn't hold any weight for Haier. Even their terms are null and void as is the case of almost all "terms of service" documents in Europe.
That wouldn't stop them from pursuing something in a US court if the other party is in the US. But even here, I doubt their argument would hold water in an actual trial, considering existing precedent.
That seems like it would be nearly impossible to prove with software. There are so many ways to structure solutions and most of them conform to an open standard
It's an open source project repository. It can be compared to the process descriptions in the patent. But patents and copyright don't cover APIs, as decided in Oracle vs Google in 2021.
I'm saying this usage of reverse engineering is probably safe, but if you reverse engineered a way to process data that happened to match a patent, it doesn't matter that you never saw the patent or original code, it can still be infringement.
It would still require a lot of time and hundreds of thousands of dollars in lawyers.
It wouldn't require that much time or money to lock down the API. It's not something they'd have to create from scratch.
Although I'm sure the entire platform is a mess of spaghetti code, so maybe it would be expensive to have someone untangle it enough to implement.