@kajer @ryanc that was what i was trying to argue.
fine if some people wanna run it, great, let them
i dont want it on my system
i didnt ask for it
i didnt opt in
what the fuck
@kajer @ryanc that was what i was trying to argue.
fine if some people wanna run it, great, let them
i dont want it on my system
i didnt ask for it
i didnt opt in
what the fuck
@Viss @kajer so, taking a moment to steelperson an argument here, n00bs exposing HomeAssistant to the intarwebz with weak passwords, and then shortly thereafter hosting a botnet node is a genuine problem, and those who need it most are not likely to opt in
to be clear, i'm not saying I agree with this position, but it's how i'd justify it rather than being dismissive
@ryanc @Viss then the integration should be in the UI and very forward about what it is and what it's doing, and be like any other integration that you can disable.
If I don't want the weather integration, great, i disable it.
being a CLI only thing that sends API hits to HIBP is shady
@kajer @Viss yes, that would be a far more reasonable solution
@Viss @kajer yeah, the way it's implemented does not respect the users
i think the chief issues here are simply:
- this shit was 100% invisible for 5 years
- it only surfaced its existance when it threw a notice
- it was installed everywhere without consent or opt in
- there is no place in the ui where you can config it, you have to use command line
@ryanc @Viss @kajer @grey
Dunno if 'respect the users' has been a ha goal for a while.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.