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?
Related
I have a daemon that executes some commands every two days. When it encounters any error, I want it to notify me. I know that bash can look up the /var/mail/user and tell me if there any new messages in this file. But I never used messages before. I think I have to use the mail command to do that.
However when I try to look up information about the usage of the command, I only read about sending actual emails, not local messages to users. So how would I send a message to myself, so that when I execute mail I'd get You have new mail.
If all you need is to be notified by your automated task, you could use something else than mails. Chatbots, for instance.
I personally use nimrod : https://www.nimrod-messenger.io
It's messenger only but other chat systems are planned.
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 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.
In a project I'm currently working on, we send some small info across the wire to WP7 device when we send a raw notification.
When the application is in a tombstone state and the user receives the toast message, we can't add the extra baggage in the toast. So we figured we need a way to resend the notification once the user entered the application again.
Anybody has any experience or possible solution for this problem. We are currently looking at a sort of handshaking between client and server. But it all seems a bit drastic for me.
Kind regards,
Tom
I would suggest to stop using rawNotifications and use only toast.
To handle the case when the app has been started using a toast notification, query the server at app startup to check if there's pending data.
For notifications sent while the app is running, you can detect them using the ShellToastNotificationReceived event of your channel. When the event is triggered, query the server to retrieve the payload.
I have a stand alone SMS Sender application that needs to send messages to certain mobile numbers. The messages to be sent can go over 1000 or more. Upon testing the app, I encountered a warning dialog, which I understand is a native warning from android OS, saying that a large number of messages are being sent whenever the app is sending the 101st (and so on) message. It will only send the message if I click on OK. I need to bypass this warning. Does anybody know a work-around. I'm using API 7.
Its rather old, but there is rate-limit information here: it requires root, so I think you're probably out of luck there. The check appears to default to 100 messages every hour: after that the check is triggered.