425 karma · joined December 5, 2018
[1] Or a pre-requisite. Correlation, not causation and all.
The framing (at least as I understood it) was more on the psychometric side - 24C@65% relatuve humidity _feels_ worse than 27C@45%RH, but the energy savings aspect is also non-trivial.
As an aside - a fairly large number of central AC systems in the US do not have a humidity censor, so they only go by the temperature set point. Upgrading to control system which does measure humidity, while energy inefficient (because AC would be used to dehumidify the air _below_ the target set point), is an option, though not as good as having a stand-alone humidity control system. Sadly, I am unaware of Nest and/or Ecobee's support for this sort of a setup. Probably not cost effective for them. :\
The setup you describe - lacking microinverters - I think there are options there short of wholesale replacement [disclaimer: I, too, am a self-taught in this field, and so am likely wrong in non-trivial ways]
Obviously anecdata on my part, but it is interesting to encounter differing situational understanding which remind of non-universal assumptions.
Have to vehemently disagree there. It doesn't matter if you believe that thousands of lives are at stake. I will stipulate, readily, that being able to assert things about one's own life are within the easy realm. But thousands? Fate of humanity? Yeah, no, I am judging - because those seem like hyperbole/manipulative claims (even if made with the best intentions), and is the same conversation device as the use of 'they say' (who's the "they"? what, exactly, was said, and under what circumstances?)
That seems to imply the carriers are disabling the app somehow. How? Is there more control the telco operators have over their subscribers' phones, or does `deactivacted` means something else?
They have smart accountants, after all.
The presenter was talking about a Solaris PAM integration with LDAP auth right before the break for lunch. The auth was done via a "query-username-and-password-strings-from-LDAP-and-compare-locally" method. I pointed out some issues with that - needing a privileged account for the query since the password LDAP attribute is usually protected, password hash on the wire (l0pht was a thing by then, so it felt wrong to sling those around), couple of others.
To their credit, I spent the lunch break with a couple of their engineers in front of a whiteboard working through a 'bind[1]-as-user-to-auth' mechanism instead. I'd like to think this helped their PAM LDAP module become more secure.
1. Siemens rep physically touching things despite vibration sensors being in place - do they not trust the sensors? If they do not, how are they doing routine monitoring? Have someone sit atop the machine and feel for things 24/7? Or is that just the rep grandstanding for the cameras?
2. Time of grid sync only having hh:mm precision. Nitpick, but at 60hz, that is about 50s of imprecision.
3. The mentioned previous unsuccessful attempts - so went wrong? Dunno, I tend to learn more about systems from failure :)
I do not want to make it see that LPAR isolation is just waiting to be compromised, but security-by-unavailability also plays a part :)
Been computering too much :)
[1] https://en.m.wikipedia.org/wiki/Scientific_wild-ass_guess
```We have included a conclusion that Swiss Privacy laws are good, and very similar to German privacy laws.```
This is weird to me in that these are laws of man, and therefore ignorable or lopphole-able by other humans if they can. Usually, by sneaky buggers in the intelligence agencies. It is, after all, their job.
Rather, I would want the standard to be something akin `Our laws do not force weakening of efforts to establish and maintain privacy.` which is to mean no meddling in E2EE, forcing VPN providers to keep logs, etc.
Possibly even proxy the traffic via something able to do SSL strip/re-encrypt and monitor that traffic with an IDS.