Library elements in v19: are block settings meant to be stored per placement, not in the Library?

Hi @zaravanina

Welcome to the Forum!

It was well described by Justin; additionally, I described this earlier(Before the development) in a walkthrough of the concept, which you can watch here:

First, I’m explaining the UX side of it and wrapping it up with a story around why it conceptually makes sense to have them as separate data sets — in other words, having the Settings as local properties.

I completely understand that it can be inconvenient for an existing project that utilized the Settings for things that should have be shared — in this case, a refactor of your content architecture would be needed. So you make sure that the properties that should be ‘shared’ take part in the 'Content ’ model of your Blocks.
— around 31:30 I invite you to consider properties in Settings to be only optional adjustments for your Block and thereby not something Authors would need to define in their usual workflow.

I hope the feature will be a great addition to your project, and feel free to provide feedback — would always love to hear how it works out for you

Best, Niels