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

[Tobias]

tordans created an issue (openstreetmap/openstreetmap-website#6297)



More and more OSM applications use the OSM user preferences API to store user specific settings.
Docs: https://wiki.openstreetmap.org/wiki/API_v0.6#Preferences_of_the_logged-in_user:_GET|PUT|DELETE_/api/0.6/user/preferences

This API allows to store key-value pairs that can be accessed by all editors that are allowed to read the preferences.

The problem is, that the character limits for this preferences values is the same as for OSM tags (255 characters).

This makes storing preferences harder than it needs to be, because apps need to split the values into multiple "tags" and then come up with a good key-naming schema to later merge those keys again.

Apps that – to my knowledge – struggle with the current setup are…
- [MapComplete](https://github.com/pietervdvn/MapComplete) @pietervdvn
- [Overpass turbo](https://github.com/tyrasd/overpass-turbo) @tyrasd 
- And iD in the near future

Given that the user preferences API is not directly related to the map data key-value system, I propose to increase the limit for this API and allow a lot more characters.

IMO this can be done without a version increase given that we can expect apps to only load their own keys and they will know what they put into them.

---

Just to be clear, this issue is only about the user/preferences endpoint, not a general increase in the limit, which is discussed in https://github.com/openstreetmap/openstreetmap-website/issues/2025 


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

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