I have a slack app created where users are interacting with App.
Many times, I am seeing when we open an app conversation, it starts from the first-ever message on that channel instead of starting from the oldest unread message.
This is happening very frequently. Is there any configuration to always make it return to unread messages rather than from start?
Related
From the docs it is clear that message delivery is not guaranteed by django-channels. I want to implement a way in my chat app so that there is a guarantee that messages are delivered to the client.
I am using redis, if that matter. When I say messages I don't mean chat text messages. I haven't implemented that part and don't need that for now. I just have video call feature. What gets lost sometimes is when users join the room the room members list doesn't reach them. So I want to do something like:
Client connects.
Servers creates a record of the event in step 3 below.
Server sends the list of room members event to the client.
Client process and acknowledges the list.
Server on receiving the acknowledgment from the client marks the list sent event as SUCCESS or something.
My questions are.
Is this approach good?
And should I use a new model to store the message events so that server can know which messages to sent and which have been already sent successfully or is there anyway to do it in redis db?
I am new to this so I maybe overlooking something that you as experienced guys know of. Please guide me with your precious inputs.
Thanks
I have written a simple applescript script to go through a list of phone numbers and send an SMS using Messages app on OSX. This all works great but Messages stores every sent message and I don't want it to do that. I've unchecked the only option in Messages preferences to not save the messages on exit but this seems to do nothing. It still saves the messages.
I don't mind adding to my apple script to 'tell' messages to delete the messages but I don't know how to do this. Any ideas?
Sinch seems to serve the purpose find for sending messages but is there an example, perhaps using Parse, where missed messages accumulate in an inbox and allow for responding to the missed message and keeping the thread of messages?
The messages will be delivered to the client as soon as you launch the app, then you can save it to parse if you like.
I'm learning to use iron.io MQ push queues. I'm pushing some messages with Laravel php framework and everything works. However, just to round up my knowledge, I would like to see the raw contents of these messages. In my iron.io account I can see the total number of messages sent, but I can't find a place where to inspect individual messages and their contents. I'm wondering weather Laravel is sending some ID's or anything like that..
Laravel is using IronMQ's Push Queues and since push queues are delivered immediately, they don't stick around upon successful delivery. Although, you can create an error queue to inspect messages that can't be delivered successfully.
I have a simple messaging system on my site. I would like to implement limits on messages. For basic users, users can have store a maximum of 250 messages in their inbox and supporters can store a maximum of 3000 messages.
My question is about the UI aspects.
If a basic user already has 250 messages:
would you block another user from being able to send them a message until they have deleted some messages?
Or would you put the new message in a queue and not show it until a user has deleted some messages?
Would you tell them they have new messages waiting but they can't read them until they've deleted some messages?
What would be your approach?
I would suggest an automatic delete that the oldest messages are automatically removed when newer messages arrive.
Edit: See comment below.
Also, besides this method, you could make a way to save some messages or make them favorite to prevent auto-deleting them.