iD doesn’t move them, it copies them. Hashtags will still be kept in the comment.
Removing hastags from comments in editors is one of possible solutions.
3 Likes
This is true if you manually enter a hashtag or if the Tasking Manager has passed in a hashtag as part of the comment (which it does). However, if the Tasking Manager were to use the dedicated hashtags URL parameter, the hashtags would appear only in hashtags, not comment.
If you go to this iD preview that has hashtags set, move the hipster-named café, and click Save, you’ll see the hashtags prefilled in the Hashtags field, but the Changeset Comment field will be empty and the Upload button will be disabled:
I haven’t verified whether JOSM behaves the same way when hashtags is passed in via the remote control protocol.
Once iD’s clients decouple hashtags from changeset comments, I think it would be pretty safe to remove the copying functionality. Anyone who manually enters a #hashtag in the changeset comment is probably doing so ironically, or more likely referring to a changeset ID, note ID, IRC channel, or Slack channel.
1 Like
Whatever gets implemented, or nothing at all, I’ll learn to live with it. If I can put up with freetext anonymous useless notes, I can totally put up with hashtag changeset comments.
2 Likes
Ironically, I tested in JOSM entering a hashtags tag but no source tag. It was erased after I pressed to move to next line. I tested renaming an other tag to hashtags, still no source. When I sent my edit, without warning error for empty source, JOSM sent my edit to the API with no hashtags and no source !
It seems like there’s plenty of room for improvement all around for how various tools handle hashtags. I mostly find they just add noise, but I can see their benefit when used judiciously. Moving them to a separate field on the changeset seems best.
I’ll share a funny experience I had recently while using waterwaymap.org to connect gaps in waterways. I had clicked the “Edit in JOSM” button and when I went to upload my changes I saw that it had pre-populated #RiverMapping in the comment field. I added Connecting waterways to the comment and clicked upload. I submitted several more changesets but left the comment alone as I was doing the same thing in all of them. Then I added a completely new stream so I changed my comment to add stream. I didn’t notice until after uploading that the full comment had become add stream #RiverMapping #RiverMapping #RiverMapping #RiverMapping #RiverMapping #RiverMapping. I guess future mappers will get the impression I was really getting excited about river mapping 
. I don’t know why this happened, but it seems with every upload, the hashtag was replicated.
Yes I noticed that too when I started mapping rivers. It’s a bug in JOSM, and it’s been fixed there, but that hasn’t been released yet.
Yes, starting from rejecting some obviously inappropriate comments is obviously more conducive to minimizing the negative feelings towards the editor, and can also intercept behavior that is not just abusing the hashtag (such as hundreds of the same comments continuously ?)
Yes, the most hoped-for thing with hashtags is to bring together changesets with the same characteristics, but currently this cannot be done on the site, and it relies heavily on external tools such as osmcha. (I would also comment this as an expectation for the new backend in The Next Generation of OpenStreetMap — in Python!)
是的，用hashtag最希望做到的是把具有相同特征的changeset汇总在一起，但目前在站内做不到这一点，而很大程度上依赖osmcha之类的外部工具。（我会把这一点也作为对 https://community.openstreetmap.org/t/the-next-generation-of-openstreetmap-in-python/105621 中新后端的期望）
I don’t have much problem with that (using osmcha.org for changeset analyses), though. osm.org simply cannot be everything for everyone, so it has to make compromises what to include and what not. There will always be people unhappy about what was included and what was not.
I do that think osm.org should be geared toward most popular (i.e. non-contributing, or tiny contributions like leaving a note here or there) users, instead towards mappers/developers (which are more likely to have knowledge and will to use several other sites too)
Perhaps this is the time to pause and ask ourselves if hashtag-only changeset comments are actually the problem here. Really, I think what the OP is complaining about, fundamentally, are changeset comments that don’t actually help someone in understanding the change. There is no automated rule that will solve that problem.
Is anyone confused about what I did in this hashtag-only comment?
1 Like
I think it’s unlikely that a mapper would’ve come up with such a comment had it not been for this discussion or perhaps cargo-culting a pattern of changeset comments that they encounter due to Tasking Manager edits. In my opinion, yes, hashtag-only comments are the problem to be solved, but it’s nothing more than a bit of technical debt in our software ecosystem, paired with some outdated policy language that’s strongly coupled to software behavior.
I agree with you that the hashtags are not a social problem that requires an ongoing enforcement campaign. But since I also agree with you about “tools over rules”, I would prefer that we solve the root cause of misleading instructions and poor default behavior rather than hacking around it by slapping users on the wrist and blocking their edits with (depending on the editor) a most unhelpful error message without an opportunity to recover their work.
7 Likes
I would say that they definitely can be put also in hashtags changeset key,
I would even consider it as strongly preferable.
2 Likes
I think it would be actually a nice feature to be able to filter by changeset hashtags. The same as it’s possible to filter traces by tags: Public GPS Traces tagged with osmand | OpenStreetMap (osmand tag). I will write that down!
Yes, I’d say the same - Hashtags IN ADDITION to a good changeset comment
are totally fine and if the editor being used supports it, should
definitely ONLY go into the hashtags key.
If the editor being used does not support it, then we should accept
hashtags in the comment field and nag the editor authors 
3 Likes