The killer reason for "Postgres as a platform" is that Postgres has a robust* security model (there are edge cases, but for a subset of statements, it works well)
That is true, and most DBAs are fully aware that the security model is only as good as the extensions they load and docker integration is very likely low on the list of necessities.
Is it "simply" a cloud-connected pilot wire controller? I don't really see anything about what I understand about virtual power plants.
Also, why is a Linky meter necessary, shouldn't it work with any electricity meter?
On another note I don't understand how pilot wires aren't more widespread outside of France. I bought my radiators in France because I couldn't find here anything that would be easy to control, and anything controllable at all was 5 to 10 times as expensive.
I'm already not signed in to Reddit so this already applies. It turns out most forums default to public as that drives organic growth that sustains them over time. There are enough public fora to not have to seek out private ones to answer things.
Using the DNT (Do-Not-Track) header as an example. When you make a request to a service, you're browser can attach this DNT header to signal to the service that you don't want to be tracked. But since services that you're getting responses from can just ignore that (no repercussions for ignoring it really), it becomes another data point they can use to separate you from other users who's headers would be the same as you.
1. resistfingerprinting (RFP) doesn't affect DNT. it's also not some sort of flag that nicely asks services to stop tracking you.
2. That's not a good analogy. If we're looking at a single choice in isolation, it's true that opting into DNT (or RFP) makes you stick out compared to everyone. There's only two options (DNT header being present or not), and one option is obviously more common than the other. However, the difference with RFP on/off is that there aren't really two options. Yes, RFP can only be on/off, and "on" is much more rare than "off", but leaving it "off" also uniquely identifies your device through fingerprinting. You're not really choosing to blend into the "all the people with RFP on" group vs "all the people with RFP off" group. You're choosing to blend into the "all the people with RFP on" group vs "all the people with RFP off and has the fingerprint as you" group[1]. Whether that's more or less identifiable is unclear. If you have the most run of the mill setup[2], then RFP might indeed make you stick out more compared to your normal setup. However, if you have an uncommon setup, it might make you stick out less, because the amount of RFP users is greater than the amount of users with the same fingerprinting attributes as you.
[1] in reality it's not really one group for RFP users and separate groups for everyone else. There are fingerprinting attributes that RFP doesn't block, so it's more like a set of groups for RFP users, and a separate set of groups for non-RFP users, but there are less distinct elements in the RFP set, since various fingerprinting attributes are spoofed to be the same.
> So in short: your normal browser does not have to be honest about it's properties, but it won't make you more anonymous because you still stand out from the other people and content on the web will break. Tor works because everyone has the same properties, including resolution. You can surely change your resolution, but there is just simply a chance that you will be standing out from other people. It's just safer to keep it the way it is.
If the "resist fingerprinting" feature changes anything in the data that is read by trackers, you will stand out like a sore thumb among the millions of browsers with the default settings.
When you are one of the few people that enable this feature, you are part of a smaller group of people. Maybe you are the only person in your own using this feature, so seeing a single client with the "resist fingerprinting" characteristics and correlating that with things that the browser cannot avoid (e.g. IP address mapping), you might now be uniquely identifiable.
Fingerprinting resistance should be more focused on feeding false information to these algorithms rather than crippling their functionality and thus sticking out from the crowd.
To my knowledge, resistFingerprinting mostly does the latter.
The problem is that "feeding false information to these algorithms" only really works if the algorithms are naive and don't try to detect whether you're lying. If your "feeding false information" mechanism can be detected, you're still in the same position.
Frankly I just install Island, and then run Whatsapp (and all not-always-needed apps) inside it. Plus bonus: you can freeze the apps you don't need and keep the island running.
It still makes sense to start with the core business values then go up with nice to have features.
Compexity comes sometimes from not so important features that could take much longer to migrate. But of course some of these features are why some products are picked over others in the first place, however this requires a case study and more analysis.
I agree. Certains functions are way more complicated and hard to show value for than others, which is really hard to comprehend for some managers.
Functionalities like undo/redo take a lot of planning, coordination and integration efforts than others like a simple export function, but good luck selling that to any marketing or product owner for xx manndays.
I still think that this subject is way too specific to be generalized like this, but general thumb of rules still apply like good estimation and technical planning.
That being said, I like the idea of Postgres as a platform for more than data tables storage and database engine. It proved quite powerful and useful.