@matkoniecz never wrote that a block message should be shown on _login_, but on
_entering the site_, i.e. the user may already be logged in but accesses some
page on the osm.org website, e.g. the oauth page. But fair enough, I propose to
change the text of this issue to:
---
> **Expected:**
>
> that may not be popular with clients that have invested a lot here in
> optimising the flow
Looking at JOSM, I seem to remember that they *used to* have some "fully
automatic" authorization where you'd input the username and password into JOSM
itself and JOSM would then fake towards the OSM w
Well, it looks like you found the bug?
If you send yourself a message, it is unread in the inbox until you mark it as
read.
--
Reply to this email directly or view it on GitHub:
https://github.com/opens
But not documented in https://wiki.openstreetmap.org/wiki/API_v0.6
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/4509#issuecomment-2582868756
You are receiving this because you are subscribed to this thread.
Message ID:
_
### URL
https://master.apis.dev.openstreetmap.org/api/0.6/user/messages
### How to reproduce the issue?
1. **Send yourself a message**
`POST https://master.apis.dev.openstreetmap.org/api/0.6/user/messages`
Body: `recipient_id=, title=Test123, body=Test123`
Headers: `Authorization=Beare
Many of the use cases covered by this issue/PR are currently solved with hash
tags (e.g. #surveyme) and tools are currently made to take these into account.
Tools would need to be adapted to support tags as well.
The advantage of having tags implemented like this properly would be that there
co
