In our latest blog post, we cover Pushed’s Members-Only feature. This allows full control over subscribers and independent push notifications for each subscriber. https://t.co/WDEDron4gT
Interested in targeting users in Pushed? In this blog post we cover all the details of sending push notifications to specific users. https://t.co/aaXN0Q1J1g
And after this dramatic series of issues (all resolved now 😉), we’d like to introduce the latest version of our Pushed App for iOs. Added minor redesign and support for Dark Mode.
We would like to apologise for the inconvenience caused with the Pushed mobile apps outage. All of you have been very patience and understanding. Mistakes were made and we will do changes to ensure this does not happen again. 💪🏼💪🏼💪🏼
Our development team has successfully identified and fixed the issue affecting our iOs app. Fortunately, a really weird syntax error was the cause. For those asking, the issue was not related to the reported with Android this morning.
Our development team has successfully identified and fixed the issue with our Pushed Android app. App should be working as usual. No further action required from users.
https://t.co/VjS8JDO2jn
Our Android app is experiencing issues that affects a wide variety of devices and versions. We're working on it to fix the issue as soon as possible. We will be using twitter and our blog to update the status. https://t.co/VjS8JDO2jn
@rattazong@sash Yep, we’ve being doing improvements the whole afternoon to both mitigate issues of Google outage and to be completely independent in the future. 😉
@rattazong Hi @sash! Not really, it did not affect directly in that matter, but it certainly did not helped. Fortunately it is all good now. If you found any issue let us know and we will take a look. 🙂
Pushed in the Real World: Envoyer deployments
This week we feature a simple yet handy integration that will be useful for people using @laravelphp’s Envoyer service, to receive Pushed notifications on each deployment.
https://t.co/m1f3EpFFCN
#push#notification@laravelnews
How @github survived to, probably, one of the biggest DDoS attacks ever produced, with a peak of 1.35 terabytes/second via 126.9 million packets per second. Thanks for sharing @github. https://t.co/n5LGuebc36