| 5 Jan 2025 |
 K900 | And it doesn't do that anymore | 19:09:36 |
| K900 | /shrug | 19:09:40 |
 @hexa:lossy.network | oh yeah, and I noticed my midea guy also has no midea ac anymore | 19:11:28 |
| K900 | Why do you have a midea guy | 19:11:41 |
| K900 | Also is your midea guy using this specific integration | 19:11:49 |
| @hexa:lossy.network | https://github.com/mill1000/midea-msmart/issues/151#issuecomment-2240013869 | 19:11:51 |
| K900 | Or one of the other two | 19:11:52 |
| @hexa:lossy.network | asked for packet captures of the provisioning steps of the app | 19:12:05 |
| @hexa:lossy.network | I provided all kinds of info, radio silence | 19:12:20 |
| @hexa:lossy.network | on some issue he says he doesn't have any midea ac anymore and can't check up on stuff | 19:13:53 |
| @hexa:lossy.network | so rip | 19:13:58 |
| @hexa:lossy.network | lol | 19:21:53 |
| @hexa:lossy.network | all regexes in that packages throw warnings, because they are not raw strings 🫠| 19:22:05 |
| @hexa:lossy.network | K900: midea-local pep517 pls | 19:22:44 |
| @hexa:lossy.network | still says format setuptools | 19:22:52 |
| @hexa:lossy.network | midea-local> /nix/store/gq9pbcplpixh9ddp69kpq5faa0nravs7-python3.13-setuptools-75.3.0/lib/python3.13/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
midea-local> !!
midea-local>
midea-local> ********************************************************************************
midea-local> Please avoid running ``setup.py`` directly.
midea-local> Instead, use pypa/build, pypa/installer or other
midea-local> standards-based tools.
midea-local>
midea-local> See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
midea-local> ********************************************************************************
midea-local>
midea-local> !!
| 19:23:17 |
| @hexa:lossy.network | also setuptools is annoying me about it | 19:23:26 |
| K900 | Ugh I need to focus on one thing at a time and not like eight | 19:25:05 |
 @adam:robins.wtf | I’m in that club too | 19:31:39 |
| 6 Jan 2025 |
 macaroniskengz | In reply to @hexa:lossy.network
we have set up pretty strong isolation for home-assistant in nixos Do you think a container doesnt add anything at all security wise? It runs in a VM already, so that's that | 02:18:51 |
| macaroniskengz | * Do you think a container doesnt add anything at all security wise regarding upstream harding? It runs in a VM already, so that's that | 02:19:06 |
| @hexa:lossy.network | not too much | 02:20:13 |
| @hexa:lossy.network | you need to mount certain things into the container | 02:20:29 |
| @hexa:lossy.network | you probably want to run in the host network namespace | 02:20:37 |
| macaroniskengz | In reply to @hexa:lossy.network
you probably want to run in the host network namespace Actually I dont want that | 02:21:48 |
| @hexa:lossy.network | ok, so no multicast things for you | 02:22:49 |
| @hexa:lossy.network | no avahi discovery | 02:22:57 |
| macaroniskengz | Yes, due to security concerns I already disabled it in my current setup | 02:23:53 |
| macaroniskengz | Maybe I am too paranoid, but i dont trust thesd proprietary devices I cant get rid of | 02:24:25 |
| @hexa:lossy.network | you'd probably have to review the systemd hardening yourself | 02:25:37 |
