What is Reddit's opinion of OneSignal?

From 3.5 billion Reddit comments

>The Idle Detection API is subject to user permission, which can be found in Chrome 94 settings. The user can specify whether or not sites are allowed to ask "to know when you're actively using device". A concern with such settings though is that sites may try to coerce the user by blocking certain content unless the permission is granted.

Exactly. We're already seeing abusive, misleading prompts ("press allow notifications to verify that you are not a robot") about notifications. The same will happen here.

Every added opt-in alert will also further alert fatigue, where people just keep pressing allow until they get to the site.

If you're in the Bay Area (we're located in San Mateo), we use Rust to send over 4 billion push notifications a day, with up to bursts of 800K+ per second. Our stack is a mixture of Ruby, Rust, and Go.

See backend / senior backend engineering roles at https://onesignal.com/careers.

Joe, our CTO and also author of alacritty, wrote up a (slightly out-of-date) post about our team for a different role as well: https://onesignal.com/blog/onesignal-is-hiring-a-distributed-systems-architect/.

I'm happy to refer you and anyone on /r/rust, just send me a DM if you're interested and able to work in the area!

For anyone interested, here's a direct link to our Rust opening. Note that the job title does not include Rust since we found it was detrimental in attracting people not already familiar with the language. It is however very much a Rust job.

The actual cost of sending the remote push notification is free. I believe the true cost would be the servers needed to scrape reddit's api endpoints for each installed Apollo app user (let's say every minute) and send push the notifications to users whose endpoint data changes (for example, when you get a new PM). Unless reddit has a new streaming api that I'm unaware of.

I think he's is definitely overestimating the cost of servers. I don't know the actually DAU/install-base, polling frequency, or other metrics to know the full cost benefit analysis... but it's 2018 and cloud compute resources are very cheap. If architected correctly it should be fractions of fractions of a cent per user per month.

/u/iamthatis you should make a post in /r/aws if you have any server architecture questions. I'm sure you'd get a lot of feedback considering you make one of the hottest reddit apps right now. You could honestly even write the whole system on AWS Lambda but EC2 hourly will definitely be cheaper than per function execution.

I think you should only do remote push notifications. And it should be an exclusively Pro feature. A subscription model for push notifications, no matter how cheap, is going to fail before even hitting the ground. Build remote push notifications into Pro and convert more users.

That was a really great article and I'm really glad you posted it! I hope I can actually apply all this stuff in practice. I'll definitely keep an eye on your site!

One advice/request about the site: you should implement browser push notifications when a new post come out. This way it will be much easier to not miss any new content. If you are using WordPress, then there are a lot of ready-made free plugins for that, e.g.:

https://onesignal.com/

https://pushed.co/

And many others. The site is very pleasant visually, I like the art style you are using.

Email is still very worth it. That being said, Push Notifications have been something I have been playing around with.

We added them to Merch Informer about a month ago and so far I cannot really figure out why I did not do them a LOT earlier. I never accept push notifications personally, but apparently everyone else does if they like your content. Amazing way to drive people right back to your site without spending a dime.

Setting everything up takes about 10-15 minutes and I used https://onesignal.com which is free and straight forward.

I have used onesignal in the past. what you do is:

1. On the mobile app you register the user with the service (they provide an sdk) and get an id
2. Store that id on your end
3. Use their rest api with the id of the user to send notification
4. ?????
5. Profit

There's no default at all actually, so it's not really true that everyone was automatically opted out either.

iOS asks you the first the time an app tries to track you, and both options are presented equally with the user required to pick one. The option is presented front and center when needed, it's not buried in a menu somewhere.

The prompt looks like this: https://onesignal.com/blog/content/images/2021/04/prompt.jpg

That looks like a similar issue to this issue, mentioned in this post as having been fixed on nightly.

Is onesignal GDPR compliant yet? Haven’t looked at them recently but last I checked they were illegal to use within the EU and couldn’t offer us a plan which was legal after contacting them. It has been 18 months now, I’m just out of date on this.

Firebase is also a good option though. GDPR compliant and a well supported react native library.

Edit: okay they are compliant now: https://onesignal.com/blog/onesignal-sdk-and-documentation-changes-for-gdpr/

I integrated both onesignal and Firebase, and onesignal was fantastic (both easy and a great platform)

You can use a notification previewer/generator for the notification at least. Something like this page will allow you to at least mock up the notification.

For the 'app' itself, I'd just grab an image of an iPhone and use photoshop to mock up the app. Alternatively, you could use a WYSIWYG editor for mobile site development, but that may be more involved/difficult than just creating an image using photoshop or similar.

I'm currently swimming towards Android after jumping off the sinking ship that was Windows Phone. If there's one thing I learned is that there's safety in numbers. If there's a bug specific to Samsung's UI for example, only Samsung users will notice and report it. If there's a problem with stock android, every android phone will probably have it. Also, this

I haven't used it yet, but I plan on trying out OneSignal. It's free and it looks promising. Maybe if anyone here has used it before, they can share their experiences/opinions.

We just recently tried OneSignal. We haven't evaluated pricing yet (they say it's free but I'm not sure if there are any hidden costs), but technically it's relatively straightforward to migrate from Parse, they even provide an import tool for that.

Add me to the list that can't connect via the app.

I can connect through browser on my phone on the same network using my PC's internal network IP. I can't connect via phone browser using the IP shown when trying to Register a Tautulli Server.

I have added OneSignal.com to my pi whitelist.

My PC is running a VPN.

outlook and other advanced email apps should offer you to have a specific sound per contact. push notifications are anyway supported by them. i wonder why you want to make it so complicated.

else: https://onesignal.com/

I'm hitting this same error with Tautulli v2.6.10 and onesignal.com whitelisted on my Pihole. Disabling the pihole, restarting Tautulli via webui and restarting the app don't seem to help. I'm probably missing something basic, is there anything else I should try?

It seems to partially register, I have an entry under "registered devices" on the server but the app is still saying it's not conencted.

I have used both OneSignal and Webpushr. I like webpushr better and I am glad it exists. There was no other viable option other than onesignal for a long time and they exploited their monopoly. Please read the following before you use OneSignal: what onesignal does with your data. more on what they claim they did and will no longer do.

gdeglin seems to be singing "we are the market leader, we have 72% market share, everyone uses Onesignal, and therefore you should too..." and "everyone else is bad and evil, everyone else is a copier, bla, bla" everywhere and all forums but has failed, and continues to avoid, to address legitimate and valid concerns such as: I hope the boy finally addresses these.

1- Where and to whom was subscriber data sold and for how much? What did advertisers do with that data? How could onesignal sell their customers data? What were you thinking?

2- Why is there no mention of annual contracts on their pricing page? Why do they continue to surprise & trap customers on annual contracts?

After a long time trying to get this to work, here's my two cents:

If you are sure that your network can access OneSignal.com and you are getting no errors in the logs, next go to your android phone under notifications for the Tautulli app. There you will find an option to called "Storage & Cache". I clicked on "Clear storage" and tried again and finally it worked. Hope it helps.

For anyone using OneSignal, we recently released support for Mac Catalyst push notifications: https://onesignal.com/blog/onesignal-supports-mac-catalyst-build/

This is marked solved, but I don't see any solution.

I have also whitelisted onesignal.com in pfblockerng (similar to pihole, but for pfsense) with no change. If you scan the QR code and go back, you can view the server as long as the QR code is still up. Once you close or cancel the scan the app also stops working.

Few thoughts:

1. Some of your button links aren't working properly.
2. The site can use some tightening up - too much empty space in some areas - ex: header
3. I'd recommend you use Grammarly to fix some of your spelling/grammar issues.
4. Consider setting up push notifications via a platform like OneSignal.

What type of products are you considering selling? I see you use Wordpress, Woocommerce integrated with Printly can provide fast drop shipping for a fashion site like yours.

If you need some Wordpress guidance just LMK. I work with it professionally on a daily basis.

Hi! I'm one of the cofounders of OneSignal, so obviously I'm a bit biased, but I just saw this and wanted to share my perspective.

We started OneSignal after previously running a mobile game studio (That built games in Unity) because existing tools had limitations, bugs, or were just way too expensive. A big focus of ours has always been making it easy for any developer, large or small, to send more effective notifications.

The badge count thing you noticed is a great example. We knew that incrementing badges was a problem for a lot of smaller companies, so we spent a bunch of time building a system to do it on our side. The initial implementation required keeping track of separate counter for every single device that installed an app. We then made it a simple field on our dashboard and API that anyone could use. Another example is images -- any of our customers, free or paid, can upload an image for a notification and have it served from our CDN.

We've recently grown our team a lot, so we're rolling out cool features faster than ever before. Earlier this week we launched in-app messages, and already it's being used by about 1000 apps. https://onesignal.com/in-app

I hope you'll try us out! If you run into any issues, please feel free to reach out to our support team and we'll be here to help out.

This could be the OneSignal push notifications. I don't know if this exists for Windows but on a Mac you can subscribe to website notifications so you're notified when new content is published even if your browser isn't running.

In Safari there's a setting to "allow websites to ask for permission to send push notifications".

This should be working fine. Are you able to load this site from both your phone and your computer running Tautulli?

https://onesignal.com/api/v1/notifications

You should get an error message

{"errors":["app_id not found. You may be missing a Content-Type: application/json header."]}

You're ignoring two things.

One, Apple had more to gain by having a isolated marketplace.

Two, the browser ecosystem is not the same as it was 10 years ago.

u/tobimacoss elaborated on One, but I'm going to point out some stuff in two.

Web Audio API lets developers create and alter sounds.

WebGL does 3d without a plugin.

Web Sockets allowed for socket creation, and WebRTC allowed for both video/audio chat and some networking.

WebAssembly makes a lot of processing intensive applications feasible in web apps.

For instance Warbrokers.io is a bit of fun and that uses WebAssembly through the unity engine, plus WebGL.

Now onto the point about PWA apps.

Appcache as first implemented in HTML5 kinda sucked because it wasn't flexible or contain enough storage space.

Web pages lacked notification api so they couldn't alert the user without annoying popups.

IOS still didn't have reliable notification or offline support in web apps, but supporting service workers would fix that problem and give them a vendor neutral way of doing it, which means support for apps that already exist.

https://onesignal.com/blog/when-will-web-push-be-supported-in-ios/

If you look at the things that have changed from 10 years ago, you'd realize that the Web Ecosystem is a lot more mature and capable of handling app development. It's the main reason Adobe is dropping flash support.

Granted the web will never be a perfect replacement for native apps, but it's constantly improving.

I could probably list more things that didn't exist in browsers in 2008 by using google search, but I think I got the point across.

As far as I'm concerned, it's not the same as 2008 because the platform itself has had 10 years of growth.

Look into using a mBaaS like Firebase to manager the users and the data and a push notification service like OneSignal for sending messages to groups. Parse would have been great for this, but it just shut down.

OneSignal is something we're looking into since it handles cross-platform support, including major web browsers, and is priced as "Totally free". Not sure yet about the freeness but it's got some cool features, dashboard, etc.