The two subject repos are: https://github.com/Andre0512/hon https://github.com/Andre0512/pyhOn Make whatever use of that information you will before the takedown occurs.
If people fork the repo, would they also be sent a takedown?
Haier hits Home Assistant plugin dev with takedown notice
21–30 of 172 posts
Re: Haier hits Home Assistant plugin dev with takedown notice
#22I wish there would be an appliance manufacturer that would actually hire developers to create and maintain Home Assistant.
Home Assistant users are small minority of many of these companies user bases (including ours), and these integrations being locally focused often poll HEAVILY causing an upside down ratio in API traffic compared to all other users. The solution is to allow local interfaces (matter, HTTP, etc) but most company cybersecurity teams just freak out at this. Oh, and the reason we don't have a full time team managing HA is…
> but most company cybersecurity teams just freak out at this.
Yeah, and we can see(in general) how good they are. is there any such shitty consumer thing that doesnt have atrocious security?
Re: Haier hits Home Assistant plugin dev with takedown notice
#23The two subject repos are: https://github.com/Andre0512/hon https://github.com/Andre0512/pyhOn Make whatever use of that information you will before the takedown occurs.
If people fork the repo, would they also be sent a takedown?
If you fork it, do a proper git clone and git push. Github can and has DMCAed direct forks in the past.
Re: Haier hits Home Assistant plugin dev with takedown notice
#24Never heard of them. May the Streisanding commence.
One of the largest consumer appliance companies in the world... the own GE Appliances, for instance.
They do about $30 billion a year in revenue.
Re: Haier hits Home Assistant plugin dev with takedown notice
#25I wish there would be an appliance manufacturer that would actually hire developers to create and maintain Home Assistant.
Home Assistant users are small minority of many of these companies user bases (including ours), and these integrations being locally focused often poll HEAVILY causing an upside down ratio in API traffic compared to all other users. The solution is to allow local interfaces (matter, HTTP, etc) but most company cybersecurity teams just freak out at this. Oh, and the reason we don't have a full time team managing HA is…
Why would the cybersecurity freak out at that, that seems opposite. The company owning the data (and controls!) is much more of a risk.
Re: Haier hits Home Assistant plugin dev with takedown notice
#26Earlier quoted context omitted.
If people fork the repo, would they also be sent a takedown?
If you fork it, do a proper git clone and git push. Github can and has DMCAed direct forks in the past.
At the risk of asking a dumb question, what does a git push do for you there? (Fully agree on the clone locally point.)
Re: Haier hits Home Assistant plugin dev with takedown notice
#27Earlier quoted context omitted.
Home Assistant users are small minority of many of these companies user bases (including ours), and these integrations being locally focused often poll HEAVILY causing an upside down ratio in API traffic compared to all other users. The solution is to allow local interfaces (matter, HTTP, etc) but most company cybersecurity teams just freak out at this. Oh, and the reason we don't have a full time team managing HA is…
Why would the cybersecurity freak out at that, that seems opposite. The company owning the data (and controls!) is much more of a risk.
Don't ask me to explain the mindset of your average "tool runner" cybersecurity person.
I've long advocated a local HTTP interface for our products, but usually a losing battle.
Re: Haier hits Home Assistant plugin dev with takedown notice
#28Earlier quoted context omitted.
Home Assistant users are small minority of many of these companies user bases (including ours), and these integrations being locally focused often poll HEAVILY causing an upside down ratio in API traffic compared to all other users. The solution is to allow local interfaces (matter, HTTP, etc) but most company cybersecurity teams just freak out at this. Oh, and the reason we don't have a full time team managing HA is…
> but most company cybersecurity teams just freak out at this. Yeah, and we can see(in general) how good they are. is there any such shitty consumer thing that doesnt have atrocious security?
Security via obscurity and "closed loop" tends to be the answer, plus whatever doesn't show up on a scan tool.
Thankfully we have a (fairly) accessible API to the cloud side.
TBD on what (if anything) matter will change.
Re: Haier hits Home Assistant plugin dev with takedown notice
#29Earlier quoted context omitted.
If you fork it, do a proper git clone and git push. Github can and has DMCAed direct forks in the past.
At the risk of asking a dumb question, what does a git push do for you there? (Fully agree on the clone locally point.)
Not the GP but at that point it's available and more discoverable for at least a little while longer for others (and no guarantee you'd get hit with a takedown as well).
Re: Haier hits Home Assistant plugin dev with takedown notice
#30Earlier quoted context omitted.
At the risk of asking a dumb question, what does a git push do for you there? (Fully agree on the clone locally point.)
Not the GP but at that point it's available and more discoverable for at least a little while longer for others (and no guarantee you'd get hit with a takedown as well).
Thank you! I was considering a different/lesser form of "keep it privately available" (as I suspected that keeping it widely/anonymously publicly available was never going to work.)