We are hence glad to report that we were part of the masses that hugged Signal to death during a mass migration to the Signal platform, especially after Elon Musk’s tweet.įor those of you living under a rock, Signal is an instant messenger just like Whatsapp. While Whatsapp claims that the privacy policy change will only affect Whatsapp Business users, we had already wanted to migrate away from Whatsapp ever since Facebook acquired it so the policy change by Whatsapp simply acted as a catalyst. The friends that I have are… strange, to say the least.Ī while ago, I, ModelConverge and nikhilr migrated to Signal, to escape from the privacy policy change imposed by Whatsapp. dump ( campaigns, f, default = set_default )įrom_ = os.
With open ( 'campaigns.json', 'w' ) as f : # If number is on do not contact list, ignore requestįor x in donotcontact :
route ( '/text_inbound', methods = )Ĭlient = signalwire_client ( os. # Listen on route '/text_inbound' for inbound text messages on GET/POST. If not, we will add them to our campaign.json file and send them a message to thank them for subscribing. If the number is already subscribed, we will send them a message to let them know. Here we will loop through all of the campaigns in the campaign.json file. The next part is how to handle opt-in messaging.
We will then use the send_email(body) function to send an email to an administrator that the subscriber has opted out of further messaging. If it does, we will add them to the do not contact list and send them an unsubscribed message. Then we will check if the message body includes any version of "unsubscribe" or "remove" or "stop". We will check to make sure that the number is not on the do not contact list - if it is, we will ignore the request.
We will open both the campaigns.json file and the donotcontact.json file, and get the body and from number parameters from the HTTP request. The first part of this route is for handling opt-out messaging. Now that we have defined the two necessary functions that we will call in this process, we can move on to our routes that will handle GET/POST requests! The first route we will use is /text_inbound which will accept GET/POST requests for inbound text messages.
0 kommentar(er)
