woodpeck left a comment (openstreetmap/openstreetmap-website#5309)
I know that we should ideally separate the software from operational
requirements. The software should not be monkey-patched just because its users
have a pressing need. However (:smile:), the DWG is facing a rising number of
requests where people want their original changeset comment modified or hidden
and this currently requires someone with raw database access rights to fiddle
with the SQL - an action that will leave no trace and certainly not replicate
to downstream users. In some cases the data protection case is strong enough
that the mappers would doubtless succeed in court against the OSMF - we've just
been lucky until now that nobody was bellicose enough.
(Yes, it is unfortunate that mappers are thoughtless enough to enter stuff they
later want hidden, but the law is on their side and probably for good reason.)
Anton's implementation leaves it up to the moderator who hides a changeset tag;
the moderator can write a changeset comment saying "I have hidden something
here for XY reason", which will lead to the whole changeset metadata
re-entering the replication feed and being properly replicated downstream - or
the moderator can decide not to do that in which case nothing will be
replicated. I think this, while perhaps not perfect, is good enough to go and
its deployment would relieve a lot of pressure on the moderators and database
admins.
Thank you for considering it.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/5309#issuecomment-3206062338
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/pull/5309/c3206062...@github.com>
_______________________________________________
rails-dev mailing list
rails-dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/rails-dev
