Auto-generated Changeset Comments

[Matija_Nalis]

@Nielkrokodil

Your example of a bad changeset comment has one hashtag #added and then some words, so it is no hashtag only comment. Actually I don’t know why you put the “#” there, it is quite uncommon I think. The changesets of Streetcomplete and Every Door don’t use hashtags.

Just a quick digression: EveryDoor does use hashtags if you specify them, (see Configuration / Changeset hashtags) - but as you note, most users are likely going with default auto-generated comments without customizing hashtags; and we’re straying away from original subject.

@Nielkrokodil

You are again not discussing the original topic. The original topic is not about deprecating auto generated human readable changeset comments (like Streetcomplete or Every Door do), but hashtag-only (and therefore most of the time not human readable).

You are correct; however posts/links I reacted to seem to link one to the other (paraphrasing: “because they’re all auto-generated crap!”).

To rephrase the issue with that: is "added benches" changeset comments radically better than "#added #benches", and thus former should be allowed while latter forbidden? Or is the root of the problem actually something else unrelated to use of # character?

And is:
"#hotosm-project-15476 #moroccoearthquake2023 #OPSGIS2023"
so much worse then:
"HOTOSM project 15476 mapping Morocco earthquake in 2023 #OPSGIS2023"?

Because that is a change that I predict will happen to sources generating such changesets if technical measures to prevent hashtag-only-changeset-comments are implemented. Is that the result we want to accomplish, and if not, what should we do in order to avoid it happening?

IOW, are we barking at the wrong #tree here?