I don't understand what you mean. There is a tag to explicitly state if a type2 charging station has a cable. Why do we need another, new tag? What makes an undocumented colon more "backward-compatible" than a documented underscore?

Hi,
you added the tag "idesq" to two billboards - this looksl ike a mistake, could you check that?

Hi,
here are three ways with a strange tag like this one:
way/744839170

I guess something went wrong with the name tag, could you check that?

Could you check this park? Something went wrong with the name tag:
way/998210161

Please stop these edits. Google images are not an allowed source for edits in OSM!

The POI had these two tags:

socket:type2:cable
socket:type2_cable

The version with underscore is the documented spelling.

I was pretty sure that there is a tag for this. The plant / generator namespace has so many features, but it seems this is missing.
The tag is a description of the power source of this plant, but also contains further description of plant:method.
Maybe one of these fit?

power:source:height_difference (height_difference is used a couple of times on aerialways)
power:source:water_head
power:source:water_height

The wiki page is just 3 days old and wasn't indexed when I wrote the comment. The tag didn't exist either before this edit.
Until 4 days ago only 'name' was used on cemetery=sector objects, 11000 times.

So, it's fine to invent new tags, but it is not "established long time ago".

There are no "forbidden" tags, so in principle everything is valid.
But yes, this scheme (adding :1 for a longer text) is used quite often, and everybody should be able to understand it intuitively.

Hi,
you added the tag 'water_head' here:
way/826796647

This is not used in other places, could you check for a more fitting tag?

Hi,
welcome to OSM!
Please spend some time understanding how OSM works - it looks like you're trying to add some private routes between POIs. OSM is not the right place for that - please consider using an OSM-based service like umap.

There is no well-documented scheme for this, but there are many cases of adding :1 or :2 to an existing key.

The good thing about these is that they can be quite easily supported in any software by looking for a generic ":1" part, but don't break anything if they are not supported.

There are already a few hundred inscription:1, inscription:2... tags to overcome the character limit. I think this is the best solution we can have in OSM..

Hi,
something went wrong here - many objects you added are duplicates of other, older objects. E.g.
This: way/758353459
is a duplicate of
way/82468615

Could you check the 160 objects from this changeset for such duplicates and remove them?

Hi,
be careful with editing objects that contain a "osm_id" tag. These are usually duplicates of other, still existing objects.
I'll have to revert this changeset along with the 4 changesets with 30k objects that created these.

Hi,
welcome to OSM.
It seems like something went very wrong here - these changesets created about 40000 duplicates of existing objects.
Please make sure you check what JOSM is going to upload before you start the process!

Hi,
you added the tag "motor_vechile" in many places. Could you fix the spelling mistake, it should be "motor_vehicle"?

Please check this node, it got a strange 'name:' tag:
node/8932193614

Hi,
you used the new tag "sector:name" here. Usually the name of a cemetery sector is put to the simple "name" tag.
Could you change that?

Hi,
regarding the memorial: Are the names part of the inscription? Then they should be part of the inscription tag.

"memorial:subject" is used quite often in Russia.

And it would be helpful to have a link to the article in Wikipedia, the entry in Wikidata or an image from wikimedia_commons as well.