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
Isn't the whole point of this to not use their services? As long as Haier's software and servers are not being touched I don't see how they have any legal standing. This guy should speak to a lawyer to verify if this is the case.
Anyhow, the last Haier/GE air conditioner I took apart had a commodity off-the-shelf USB Wi-Fi dongle inside it plugged in via a short USB extension lead to an off-the-shelf microcontroller board to enable its "smart" features. I'll bet you a dime Haier is violating the terms of at least one open source license, possibly more than one, via the software stack they're running in there. So as far as I'm concerned they're free to take a flying fuck at a rolling doughnut.
The problem is it's a script that logs onto Haier's servers with the user's email and password and starts polling for data. Considering that most designed usage is probably based around users every once in a while checking and adjusting their thermostat, just one user with an HACS install doing a poll every minute is 1440x more usage than the next who checks it once a day. If HACS uses were the majority of traffic for these devices I wouldn't be surprised by that metric.
That's what probably meant by the ToS because the users using it are probably violating it, and the addon can be considered as something that makes violating it easier (it doesn't have a secondary purpose other than using a set of credentials that are only given after accepting the ToS).
I've had crappy "Smart" ACs and Samsung was the absolute worst. At random times their AWS instance in Europe would go down or their app wouldn't respond. I gave up and coded my own script to directly interface with the device over the local WiFi. You cut Samsung completely out of the equation. You don't have to worry about their servers not working anymore. That's an ideal way for an add-on to work. Ideally most of the script can be retuned to work directly with the device.
Any appliance made by Samsung is pure garbage. I just got rid of one of their dryers and I'm very glad to have it gone.
What kind of trouble did you have with the dryer?
My drier squeaks a lot, it seems like the previous owner has replaced the wheel once, and I replaced the wheel again, and it still squeaks...
All the parts they used internally are made to be as cheap as possible. The rollers that support the drum, and the belt tensioner, use low quality bushings that wear out prematurely. The extra fiction the parts caused would cause the belt to fail too. I'd have to tear the entire thing apart every two years or so and replace these parts to keep it running, far more often than I'd have to repair any other dryer brand. The sensor dry cycle on it never properly dried the clothes, and the steam function on it didn't work very well either.
A friend of mine has a Samsung dryer, washer, fridge, dishwasher, and microwave. He hates all of them with a passion for similar reasons.
I don't hate everything Samsung as I'm quite happy with their tablets and watches, but I'd never purchase another one of their appliances.
Seems like the customer would be violating the TnC, not the repo owner
I said that?
Generally, a lot of companies that add "cloud enabled" to their products don't let you access the local device. Home Assistant isn't talking to the air conditioner, it's logging into their web interface. If it's polling 1/minute, that can be a lot of extra traffic, compared to a normal user.
The better solution is to work with their buyers, not against them. If they provided a local API, then the excess traffic would go away. Theirs no money in that, in the short term, however. So they take the lazy route.
There's a reason I only buy IoT type devices with a local API. They also have a tendency to turn servers off. Suddenly your smart device is bricked, despite working fine.
I'm curious about the details, yeah. Maybe they're plugging into some API or something? Breaking some safety measure? Otherwise I really don't see how these threats aren't empty. Suing somebody for breaking EULA terms does not have a great track record, and neither does modifying things you buy or making unauthorized software for computers.
But hey, if the guy says the project is coming down, then I guess the aggressive language did the thing they wanted it to do, even if it's relatively toothless.