Recently, we've observed a substantial increase in AWS calls attributed to your plugin, prompting the communication you previously received as standard protocol for our company, but as mentioned earlier, we are committed to transparency and keenly interested in collaborating with you not only to optimize your plugin in alignment with our cost control objectives,
i get it; their amazon account gets hit hard by some plugin data stream, they trace the source and kill it for monetary reasons. makes total sense. handled terrible, but still, i also completely understand getting some giant bill from amazon and freaking the fuck out.
It’s damage control, they realised what they did was getting them bad PR since news of it started spreading so they are attempting to remedy the bad PR through damage control
Oh absolutely agree, but this is where they can use it.
The dev can say that they obviously need an official plugin, and work with them on that because now they have 1,800 clones of an unofficial one that may not be optimized.
We also get to know that our tiny HA community has hit a critical mass large enough to get a corpo to freak out a bit
I did my part and sent them a “do this and I’ll never buy a Haier product” email. Corporations exist to maximize profits. Communities like ours just have to learn how to make it clear to them that shutting us out will hurt their profitability.
I think we should all be really proud of ourselves. We banded together and, regardless of WHY Haier is doing this, got them to open a line of communication. This is a huge win!
The whole point of spreading the word about an incident like this is to get public attention on it, and make the company realize that the way they’ve handled things was bad.
A letter like this indicates that they’ve realized they fucked up and they want to do things differently going forward. That doesn’t mean they’re suddenly trustworthy, but it does mean they can be negotiated with.
The correct response is to accept the offer of working together. We want to encourage companies to be cooperative and discourage insular, proprietary behavior. If you slap away the offered hand then you discourage future cooperation, and now you’re the roadblock to developing an open system.
When you start getting the results that you want, don’t respond with further hostility.
Keep pummeling them. There’s no integrity behind this, and going along will just let them get away with their bad behaviour.
They played the “We’ll sue your ass off” card first. That means it’s already in the legal realm, they never even triedto work with the OSS community, they basically said “fuck you” until the community replied, very clearly.
Had the community not responded by replicating the repo 1000+ times, and making a story about it, they would’ve continued down the path of slapping the little guy around.
They now realize they can’t compete with potentially 1000 people working on this, against them. They also fear they’ve pissed off some technophile who has some serious skills or connections. Wonder if they saw a sudden increase in probes on their internet interfaces.
Exactly this. I understand the cynicism, but it ultimately doesn’t matter what the motivation of a company walking back a poor decision is. We take the chance for mutual collaboration and hopefully everyone benefits.
On an individual level, that’s when people can evaluate if they still want to boycott and do whatever their own moral compass demands. But refusing to work together at this point just means we definitely don’t get the chance in the future to steer things in a better direction.
And even if the cooperation doesn’t last, it’s an opportunity for the open source developers to work with the product engineers and get direct information from them right now. There’s nothing as valuable as talking to the guy that actually designed the thing, or the guy who can make changes to the product code.
Even if that relationship doesn’t hold long term, the information gathered in the short term will be useful.
If I were part of this project this is what I’d be going for. Push the company to give you direct contact with the relevant engineers, right now while the negative public opinion is fresh and they’re most willing to make concessions, and then get as much out of that contact as you can. Take them at their word, make them actually back it up, take advantage of the offer to cooperate. Sort the rest of it out later.
Well, how about having a local API and have no calls at all to your cloud infrastructure? Probably too easy and you cannot lock people into your ecosystem.
From any practical standpoint, this makes so much sense.
Sometimes my Tesla fails to unlock for some reason and I have to disable my VPN and then stand next to it like a God damn idiot for 10 seconds while it calls it’s servers in fucking California to ask it to unlock my car.
As if I needed yet another reason to never ever own a Tesla.
My car has this crazy technology in it: You can stick the key in the door and twist and it’ll unlock. Even if the network is down or the battery is dead. Arcane, right?
Hell yes! My sister-in-law has your same year but the diesel version and that thing is a champ. It’s rated at 45 mpg on the highway but she typically gets 50+, even with nearly 200k miles on it.
I had a 2004 1.8t Jetta for 12 years but I swapped it for a Prius. I love the Prius features and fuel economy but I miss how damn quick that my Jetta was, plus I loved the interior color scheme.
Haha yeah there are other, more reliable methods but the “phone as a key” is also super convenient when it works properly, which is most of the time. It just would be a lot smarter if it worked locally.
…Or if there were an alternative option that didn’t rely on software and electronics is my point.
Cars have had electronic remote keyless entry for decades. It’s not new. Some of them even have phone apps that duplicate that functionality. No one but Tesla has been stupid enough to remove the keyhole, though.
I understood your point. My point is those electronics make it more convenient to use. Would I appreciate ALSO having a physical unlock mechanism? Sure. It also increases the attack surface.
Cars have had electronic remote keyless entry for decades.
I think it could definitely be possible to do locally, and I wouldn’t want a car where I have to connect to servers to connect to it. But I am also not sure I want a car that can be opened with a command on the car itself. The code to access your CAR being stored locally on the car itself, with no server side validation, does seem kinda scary. It’s one thing for someone to manage to get into your online login where you can change the password, it’s another for someone to literally be able to steal your car because they found a vulnerability. It being stored locally would mean people would reverse engineer it, they could potentially install a virus on your car to be able to gain access. Honestly, as a tech guy, I don’t trust computers enough to have it control my car.
The issue you are experiencing likely has nothing to do with the VPN. Network connectivity is not needed to unlock the car. I have been in places with no cell phone signal and it still works.
I do sometimes experience the same issue you are. If I wake up my phone, then it works. So it may be working for you not because you disabled the VPN, but because you woke up your phone and it then sent out the bluetooth signal to let the car know you were nearby.
It’s a bit of both! Certain commands to the car can be done locally via Bluetooth OR via Tesla servers. The tricky bit is that status always comes from the server. If you are on a VPN that is blocked (like I use NordVPN and it is often blocked) then the app can’t get status and as long as it can’t get status it may not even try a local command. It’s unclear to me under what circumstances it does local vs cloud commands, and it may have to do with a Bluetooth LE connection that you can’t really control.
When you don’t have service, or you’re on VPN, it may be worthwhile to try disabling and reenabling Bluetooth. I have had success with this before. If you’re using android, it seems like the widget also uses Bluetooth, so you could try adding the widget to your home screen and using that. You can also try setting the Tesla app to not be power controlled, so it never gets closed.
Either way, there’s a definite engineering problem here that feels like it should be fixed by Tesla. But I can at least confirm that, even in situations with zero connectivity, you should be able to perform basic commands like unlock and open trunk without data service.
I’m glad the people with this device are getting traction on using it with their HA, but holy hell this is a complete non-starter for me and I cannot understand why they got it in the first place. There’s no climate automation I would ever want that is worth a spying device connected to the internet and a spying app installed on my phone.
Probably more. Your app can use the local API then as well. And AWS is insanely expensive, especially if you forget to block log ingestion to Cloudwatch (ask me how I know).
I’m cynical so I assume they are turning a profit selling user data. So the lost money is not from AWS expenses but from not having installed apps to steal more data.
The spacing in the email screwed up the formatting:
Dear Andre,
I’m Gianpiero Morbello, serving as the Head of IOT and Ecosystem at Haier Europe.
It’s a pleasure to hear from you. We just received your email, and coincidentally, I was in the process of sending you a mail with a similar suggestion.
I want to emphasize Haier Europe’s enthusiasm for supporting initiatives in the open world. Please note that our IOT vision revolves around a three-pillar strategy:
achieving 100% connectivity for our appliances,
opening our IOT infrastructure (we are aligned with Matter and extensively integrating third-party connections through APIs, and looking for any other opportunity it might be interesting),
and the third pillar involves enhancing consumer value through the integration of various appliances and services, as an example we are pretty active in the energy management opening our platform to solution which are coming from energy providers.
Our strategy’s cornerstone is the IOT platform and the HON app, introduced on AWS in 2020 with a focus on Privacy and Security by Design principles. We’re delighted that our HON connected appliances and solutions have been well-received so the number of connected active consumers is growing day after day, with high level of satisfaction proven by the high rates we receive in the App stores.
Prioritizing the efficiency of HON functions when making AWS calls has been crucial, particularly in light of the notable increase in active users mentioned above. This focus enables us to effectively control costs.
Recently, we’ve observed a substantial increase in AWS calls attributed to your plugin, prompting the communication you previously received as standard protocol for our company, but as mentioned earlier, we are committed to transparency and keenly interested in collaborating with you not only to optimize your plugin in alignment with our cost control objectives, but also to cooperate in better serving your community.
I propose scheduling a call involving our IOT Technology department to address the issue comprehensively and respond to any questions both parties may have.
Hope to hear back from you soon.
Best regards
Gianpiero Morbello Head of Brand & IOT Haier Europe
I read up on it at some point and it was essentially a matter of their UI framework just being custom-implemented. Any advanced UI concept would need so much overwhelming support from the community, that a core dev then sits down for a few months to dish out the necessary UI components, that this is just not really happening. The core devs aren’t exactly bored most of the time anyways.
Having said that, they did recently renovate the settings menu using the UI components they already had, and that turned out really cool.
Also, I do feel like some smaller improvements could be made without big code changes, but yeah, those then end up in too many discussions.
The font has been discussed many times. To give you a taste:
Many want a font with fantasy style, but Minetest can also depict a futuristic setting. Others want a blocky font, but those usually aren’t very legible (i.e. accessible) and often only support a narrow range of languages.
I think, just a font, which looks less serious and less thin, already improves it massively, but you can’t even get folks to agree on that, because well, if the font is tweaked, you might need to adjust lots of UI components and mods and such to work with the different font dimensions. So, if a font change is made, people want to get it perfect from the start.
The button gradients are another case, where most people agree that something else would look better and it could be easily changed, but discussions just never end.
The community is just so big and so public, that there’s always someone new joining into the discussion, so that no consensus can occur…
I think it’s just a larger undertaking. Like mentioned in the last comments. People either need to address that as the main focus for some new major release and work on it. Or subdivide it and find people to work on the individual components to make it happen (gradually).
Also there is always the thing with hobby / free software projects. Sometimes people focus on functionality and features and not so much on asthetics and the first impression. I agree the welcome screen is somewhat important as it’s the first thing a new player sees. But I also like the developers to work on features which enhance the actual gameplay because I just see that screen for 10 seconds and it’s kind of a waste of time to improve it for someone like me. The current screen works alright. There are several dynamics affecting projects: “Perfect is the enemy of good” (don’t make it too complicated) but also sometimes a makeshift solution or something that works “okay” stays inplace indefinitely because “it works” and people concentrate on other stuff. That’s just how things work. It takes deliberate effort to work against those dynamics.
So I’d say the cause is, their focus is somewhere else.
I’m a long time heavily modded minecraft player, and I’ve never heard of this issue. If you want proper feedback, I’d suggest adding more context. (That is to say, an outline of the feedback, so we don’t have to wade through 6 years of discussion.)
Minecraft has always had a janky aesthetic, so this doesn’t seem like it’s particularly out of the ordinary.
Kakao (hopefully) won’t get to know the real names of the developers, which will prevent them from suing the devs personally.
They could try to DMCA claim the repo, but Tachiyomi is completely legal, so hopefully Github won’t take it down. Github previously helped youtube-dl after they got DMCA notices.
As far as we know, TachiyomiSY has the same relationship with Mihon as it did with Tachiyomi previously. Maybe it’ll change since SY’s dev is also said to work on Mihon, but we’ll see.
At the moment Mihon is the same as Tachiyomi with changed branding.
Tachij2kfriends, I saw the mihon dev post somewhere that tachij2k shouldn’t be used anymore. Is there a reason for that? Everything is still working on my end, and until it doesn’t I intend to just keep using tachij2k unless there’s a good reason not to. I also read somewhere that the Dev for j2k said he was gonna make some changes, but I wasn’t able to verify that… Anyone know anything more? Thanks
If it works on your end, no reason to stop using it. The reason they suggested to move elsewhere is because, at the time, there was no indication that j2k had any plans for continued development. Might’ve changed since they put that out, but that’s what they sajd
The reason the Mihon de said that is because j2k is using an older tachiyomi base iirc. Updates on it have been on the slower side.
It’s still being actively worked though (as far as I know) and it still works fine, so there’s no reason to switch off of it for now. If Jay does drop it then you should move onto mihon or its forks (TachiyomoSY and TachiyomiAZ will be based off of mihon in future versions).
github.com
Hot