We have set up HealthChecks in Cloudflare that use Slack's webhooks for informing our teams in a Slack workspaces about changes of some server's health conditions.
Initially, this went fine, but then, time after time, the different Cloudflare notifications started to create double output in our respective workspaces.
Cloudflare's dev were able to proof that they only call the webhook api once per message, but nevertheless, they appear immediately twice, as if the same message would be duplicated and then sent to the channel.
And so the fact that deleting the notification on the Cloudflare- side and creating a new one did not change the phenomenon came to no surprise.
Deleting the webhook for the Slack workspace and creating a new one and assinging it to the notifications in Cloudflare helps, though. But only for a limited undetermined time.
Does anyone have experience with this phenomenon and can tell me why this is and/or how I can prevent the Cloudflare notifications from appearing twice each in our Slack workspaces?
Related
I can use FCM console to send messages to all users or certain users at a certain time.
Now I want the app send a message to specified users when their in-game energy is full. How to realize it with FCM? And can I know the messages' sends, opens, conversions?
Sending a message to a user can only be done from a trusted environment, such as the Firebase console, or a place where you can trust that the code running is yours (such as your development machine, a server that you control, or something like Cloud Functions/Cloud Run).
For examples of how to send a message by calling FCM's API, see the documentation on building send requests, and this sample use-case of notifying the user when something interesting happens using Cloud Functions.
I'm trying to generate alerts based on notifications from Taiga project management software (when a user creates a project for example). These alerts will arrive to a specific Rocket.chat channel.
For this I am using the incoming Rocketchat webhooks: https://docs.rocket.chat/administrator-guides/integrations/
So I created the incoming webhook and entered the data into Taiga:
Configuring the webhook in Taiga
Once all this is done I check that the message arrives at the destination correctly:
Example of a notification message
Indeed, the message is received but it doesn't show any information. When a user history, an issue or any modification that leads to an alert is created, it is received in rocketchat but it doesn't show any information (empty message).
Payload sended by Taiga to Rocketchat
Does anyone know why he won't show me any information?
Thank you very much in advance
Greetings.
Do you really want to post notifications to a Rocket Chat channel, when a taiga user created a project in taiga? I would not know, how you can do that. But, as far as I can see, your screenshot shows the configuration of a generic webhook in a project after that project has been created. Therefore, I hope it is sufficient to post notifications from that project to your Rocket Chat channel. Here is my answer for this case:
I observed a similar behavior. Using the generic webhook, I could only trigger empty posts in my Rocket Chat channel by clicking on "test" for that webhook.
However, the Rocket Chat API seems to be compatible with the Slack API, cf. https://github.com/RocketChat/Rocket.Chat/issues/1728#issuecomment-166669379.
In contrast to the generic webhook, the Slack plugin for taiga (https://github.com/taigaio/taiga-contrib-slack) worked out of the box (https://tree.taiga.io/support/contrib-plugins/slack-integration/).
Only my browser gave me some hassle, because it cached the taiga webpage and after installing the Slack plugin a simple page reload was not enough to display the "Plugins" entry in the "Admin" menu of the project. "Shift+reload" did the job. But apart from that standard issue, everything worked.
We have an application that currently supports users integrating their Google accounts to allow us to index their Gmail, Google Drive and Google Calendar content. We use the Google OAuth process to ask for these permissions, and had gone through Google's verification process in the past to support this.
Recently, Google rolled out a new OAuth verification process for restricted scopes (which now include reading gmail and calendar). We've been engaged in completing the new process for weeks now, and they've been very slow to respond, and have even temporarily blocked us from authorizing new users. Our latest communication with them had them claiming that we were a "development" app and that we should submit for verification when we are in production. I responded to them saying that we are a production application, just have an invite-only process to let new users in, but have 1000s of users and are expecting to grow very quickly in the new few months. Given the amount of frustration their support has already caused me, I'd really like to get in touch with a real person there. Does anyone have any suggestions for how to get in touch them?
If anyone from Google is on this forum, I'd also love to get some help. This is holding up us letting in new users into our product.
Have already responded to the thread saying that we're a production app. Have also forwarded the thread to oauth-feedback#google.com.
Scenario: Spotify user on the native desktop application is adding and removing songs from the currently playing playlist.
I'm curious if it's possible for me to detect when any addition/removal happens? Basically need a trigger to tell me the playlist has changed without having to continuously poll Spotify's API to see if anything changed. Looking for a solution that could be used either via the Spotify API or something hack-ish using spotilocal or listening on Spotify's 4070 port.
Looking for a solution that could be used either via the Spotify API
or something hack-ish using spotilocal or listening on Spotify's 4070
port.
I wouldn't recommend this approach since the mentioned APIs may change without notice. It's not publicly supported so there's no commitment from Spotify to avoid breaking changes. It also requires the user to have the Spotify desktop application installed.
As you've noticed, since there's currently no way to subscribe to changes in a playlist, e.g. by a Websocket or HTTP PubSub interface like PubSubHubbub, your application would be forced to poll for changes. If you go down this path, I strongly recommend that you make use of the ETags and snapshot_id provided in the Playlist response.
Declaring how ETags are implemented in the Web API deserves a longer response and should be on the developer site. There's however a useful Working With Playlists guide on there that explains snapshots and some other things related to playlists.
It's also worth mentioning that all applications are rate limited, so I urge anyone polling to be aware of this and poll less rather than more. Obviously only poll when the application is actively used by the user, and only poll the playlist if it's actively viewed. You know you're being rate limited if you retrieve a 429 Too Many Requests response.
I have been able to successfully create push notifications and I have also received responses from the feedback service, so I am confident that my configuration is correct, but I was wondering, how long after a device has been made inactive, will it be picked up by the Apple Push Notification Service.
When I first polled the feedback service, I received details on devices which were inactive several days ago. Now, while testing, when I uninstall the application and occasionally poll the feedback service, I'm not receiving any results.
Any idea on how long it takes to update would be useful, as I'm no longer sure if the issue is else where in my code or if I'm just testing too soon.
Issues with Using the Feedback Service
If you remove your app from your device and then send a push notification to it, you would expect to have the device token rejected, and the invalidated device token should appear on the feedback service. However, if this was the last push-enabled app on the device, it will not show up in the feedback service. This is because deleting the last app tears down the persistent connection to the push service before the notice of the deletion can be sent.
You can work around this by leaving at least one push-enabled app on the device in order to keep the persistent connection up. Just install any free push-enabled app from the App Store and you should then be able to delete your app and see it appear in the feedback service.
source:
http://developer.apple.com/library/ios/technotes/tn2010/tn2265.html#TNTAG34
After further investigation elsewhere, I discovered people suggesting that for testing feedback service, there should be two instances of the app on the iPhone. Test the feedback service by removing 1 of these and then attempt to send notifications to this removed app.
When I do this, the feedback service responds very quickly.
I do not have exact timings, but on my system, it feels like it is responding straight away after I make a call to attempt to push a notification and then immediately make a call to the feedback service.