woodpeck left a comment (openstreetmap/openstreetmap-website#6512)
As a general comment, there was some mention of "anonymous accounts", a concept
that doesn't exist. An anonymous note is not linked to any account (rather than
being linked to an "anonymous account"). Probably just an oversight but worth
keeping the nomenclature straight!
It's been a long time since I did any work on the website code but IIRC there
is some logic that, before even applying a change to the database, will extend
the current changeset's bounding box. If that is still the case then that would
probably be the easiest place to introduce a limit like this - just refuse to
extend the bbox if it grows into a blocked area, and throw an exception or
whatever one does in Rails. -- Another architecture option is something that
@gravitystorm suggested about a decade ago, that you create a mechanism where
separate programs can be looped into the website code and basically ask for all
(or specific?) changeset to be passed by them for evaluation before they are
accepted into the database, but that's probably too grand a scheme.
And yes this could trip up users making world-spanning changesets but that
isn't necessarily an unwanted side effect. We could create a small blocked area
around Null Island and keep it there on purpose ;)
As to the increased support load, I think we should have a "help" team to which
support (and potentially also DWG or LWG) could deflect incoming ticktets that
do not require administrive action but only explanation and hand-holding. But
that is probably out of scope for this ticket ;)
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/6512#issuecomment-3586426747
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/issues/6512/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
