frigginglorious has quit [Ping timeout: 250 seconds]
adam_free2air has joined #qaul.net
<mathju>
spacekookie: that's a nice way of putting it :-)
_whitelogger has joined #qaul.net
frigginglorious has joined #qaul.net
frigginglorious has quit [Client Quit]
mahmudov has joined #qaul.net
mahtob has joined #qaul.net
mahmudov has quit [Ping timeout: 265 seconds]
mahtob has quit [Quit: Leaving]
mahtob has joined #qaul.net
mahtob has quit [Remote host closed the connection]
mahmudov has joined #qaul.net
<spacekookie>
Right, so on master there's no a basic usable implementation of the new message and user stores
<spacekookie>
I removed the "next" function from the API and RPC layer because it's being replaced by subsciptions, that aren't fully implemented yet, but that shouldn't take long
<amanjeev>
mathju: I always try but one or the other meeting takes over around noon my time :(
<amanjeev>
But it is always on my radar! I am subscribed to the mailing list. :)))
mahmudov has quit [Read error: No route to host]
mahmudov has joined #qaul.net
<spacekookie>
mathju: when you interact with the chat service, do you ever want to get all unread messages independent of what room they're in? Or do you only care about messages based on the conversation room?
<mathju>
spacekookie: Hmm, I guess not ... , but there is no simple yes/no answer to this question.
<mathju>
* Preview of the last unread messages, displayed by room with only the last unread message per room.
<mathju>
* Show a list of all rooms ordered by last message received or sent, and display for each room the last message, wether read or unread.
<mathju>
Here what functionality I imagine:
<spacekookie>
Okay that makes sense
<spacekookie>
I'm currently writing the thing to store the room list and metadata
<spacekookie>
Then I can implement this which shouldn't be too hard
<spacekookie>
I'll let you know when I have an API draft so you can let me know if anything is missing
<mathju>
Cool! Thanks !!!
<mathju>
what is interesting for the notifications, is how many unread messages we have in total and how many per room.
<spacekookie>
Yea that makes sense
<spacekookie>
Maybe we could just put the amount of unread messages into the room metadata type that gets returned
<spacekookie>
It would be less useful for when the room is actually active (it should read 0), but could otherwise be good to like...convey the name and unread count at the same time
<mathju>
this would be nice, as it is mainly a preview thing.