[openstreetmap/openstreetmap-website] Increase character limit for OSM user preference API values (Issue #6297)

[Tobias]

tordans left a comment (openstreetmap/openstreetmap-website#6297)

> My question would be, what are the apps storing in the preferences that the length restrictions are even relevant?

App settings and preferences. Most likely as some kind of object-string-representation.

> …it just seems as if morphing the service to a more general purpose data storage facility … would need some more thought that just unlimiting the fields.

I think we should iterate on this in smaller steps. Right now we have a useful but limited API. The proposed change will make it easier to work with. There are clear indicators that this will be useful. I suggest we go this step and see what we need to improve next.

A app-private API and admin UI would be nice but those can be parallel or follow up efforts.

> Not to forget the misuse potential for an essentially unlimited data sharing service.

In terms of misuse, it is not limited right know either. AFAIK there is no limit in the number of key-value pairs one app can store. And AFAIK we don't have any indicators that this API is targeted for by bad actors.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/6297#issuecomment-3224061764
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/openstreetmap-website/issues/6297/3224061764 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20250826/0b9ea7c2/attachment.htm>