rastinza @rastinza@social.cleverlibre.org

@worldsendless
E volavo, volavo felice,
Più illuminato del sole ed ancora più su,
Mentre la sintassi pian piano spariva lontano laggiù,
Una purezza dolce si organizzava soltanto per me...

Volare... oh, oh!...
Lispare... oh, oh, oh, oh!
Nel blu dipinto di blu,
Felice di programmare lassù.

@unsweet
A normal adblocker does the job

@GustavinoBevilacqua
"Literally cannot go tits up"

@rzasharifi
Buona notte

@i0466lt
Confermo, illustrator funziona decisamente meglio.
@diorama @Fbrzvnrnd @xx @zuz @kimary94

@amapanda
Sure, but since you're trying to add a new tag to the map I feel it would be sensed to at least motivate why it should be added and if it really makes sense to be added.
I'm deleting nothing, I just deem this data questionable; I feel it should be written somewhere else and then correlated with OSM.
I feel there are some big maintenance problems with this tag, moreover it will probably apply only in the US.

@amapanda
So it's a union formed by the employees of that shop only?

@amapanda
You did not address any of all the other points I made, you just replied to my personal opinion that adding this tag adds complexity.

@amapanda
I don't know what you mean by unionized.
This tag anyway would be quite difficult to define properly: if one out of 50 employees is in a union is it =yes?
If one out of 50 is not in a union is it =no?
If half the employees belong to a union and the other half to another one what happens?

I do not like this cramming of any type of information in OSM, I feel that some can be useful while others simply increase the complexity.
In this case I feel that it would be better to perform an analysis and plot the results on the map and not include this data in the map itself.
OSM, as the name says, is a map. It uses a database to store all information related to the map, this doesn't mean that it should become a database of every bit of information that can be located on the map. At the very least there should be a clear and well defined use that people will do with that information.

Is this data really available and maintainable?
How much time will it take to collect a decent amount of data for it to actually be useful?
When this happens, how much of the data available will be out of date?
People change jobs, thus places that have employees in a union change over time.
Collecting this kind of data is also very tedious and complex, very prone to errors and extremely difficult to verify.

I guess the original idea is to study the spread of the unions (in the US?) over the territory. I feel this analysis would be better performed through a separate analysis and a well defined data source.
Moreover I think this idea is very US centric, I would never go around checking which stores have employees in a union, because I can safely assume most of them are in a union in my country.
Moreover, you would have to take into account the different declinations of unions over the world: the definition of a union can change quite a bit and that tag might be senseless in other places in the world.

@amapanda
I don't see this working on a map and I don't really understand the use.

A bunch of people are in a union and you'll get some pretty much everywhere, however being in a union is a personal choice, thus often you'll get places with some employees in a union and some others who aren't.

Moreover I don't think you can get this kind of data easily, unless the employees themselves declare being in a union.

@trinsec
I would love it if it was to work on the mobile app...
Unfortunately it's quite a useless feature to me since I rarely use the webpage
@peterdrake @freemo