[openstreetmap/openstreetmap-website] Proposal for Messaging API (Issue #4509)
Milan Cvetkovic
notifications at github.com
Fri Feb 9 17:04:32 UTC 2024
> > We plan to work on transitioning OSM web site to use the Messaging API instead of directly accessing the content of the database.
>
> As @tomhughes anticipates, that's a "hard no" from me on this approach. 😄 We already do this for a couple of parts of the website (e.g. Notes) and we're working on specifically undoing this. It's overcomplicated, it's unnecessary indirection and causes way more hassle for little to no tangible benefit.
My suggestion was to make use Message API from web site as a proof of concept. I was not aware of (failed) attempts to do similar things in the past. As suggested, we will not use Message API from web site.
>
> So I'm in favour of a Messages API (nb not 'Messaging') but the web interface should continue to be a straightforward server-side-html / html-over-the-wire implementation like the rest of the site.
Agreed.
Will also change the naming to refer to Messages instead of Messaging.
> ...
> I hope we can build a proper notifications system in the near future, and refactor all our existing event notifications to use it.
To clarify, the efforts related to this github issue are _only_ with regards to direct messages to and from the users. There is no attempt to (partially) fix the notification of any kind, including the notifications about received direct messages.
> > * one for reading messages, and an additional scope for creating new messages and sending them.
>
> It's worth clarifying which scope you think "change read status" should be included in, I could be persuaded either way.
This is what I had in mind:
- `message_consume` to be able to read, messages, update their status to read/unread or deleted. Affects only messages owned by the user.
- `message_send` - to be able to send messages to other users. Affects other users as well.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/4509#issuecomment-1936280722
You are receiving this because you are subscribed to this thread.
Message ID: <openstreetmap/openstreetmap-website/issues/4509/1936280722 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20240209/aad38886/attachment.htm>
More information about the rails-dev
mailing list