Re: Tapatalk alternative for Elkarte boards?
Reply #15 – December 14, 2019, 09:10:15 pm
I'm continuing to play a bit with this and I actually now have basic web push working ... I know that is not very exciting but to get it to work seemed like a lot of effort, or at least a lot of library dependencies. Lets see, phpasn1, guzzle, webpush, sodium, http-message, getallheaders, base64url, and web-token with a variety of signature algos. I've culled this to 340 files in 67 directories LOL. All made a bit more difficult on 1.1 as our autoloader is not really PSR compliant like it is on 2.0, meaning I've probably missed a few namespaces etc. You need php7.1+ with the following extensions mbsrting, curl, openssl, and gmp. I had not heard of gmp before but you need it to have this all work. Probably not an issue if you are have your own VPN but probably an issue for a shared hosting setup. Like i said, to get it to work requires a few libs/dependencies to be installed (all tucked away under ElkArte's sources/ext directory) The test is just a simple webpage with a button, press the button and you get a notification, not yet tied in with Elk other than it is running under ElkArte as a webpage. To actually make it useful is a bunch more work and actual integration. Next I think I may look at Firebase Cloud Messaging, a google API solution which should be easier to setup, well maybe, I guess I'll see.
Re: Tapatalk alternative for Elkarte boards?
Reply #17 – December 15, 2019, 09:00:14 am
Thanks, I'll give that a read. I'm sure that since they have the same GMP requirement, and issues with Apple, its the setup I now have working.
Re: Tapatalk alternative for Elkarte boards?
Reply #25 – December 22, 2019, 06:18:04 pm
I should probably break the push notifications thing out to its own thread. Anyway just a quick update, I played around with the google firebase service and decided it was a generally a PITA. I did get it working on chrome but Fx seemed to have some issues. The documentation just stinks, half of it is for the old version, 1/2 for the new so figuring out what to do was needlessly difficult. Plus its google so either the service would become successful and they would start charging for it or it would not take off and they would drop it. For 1.1.7 I made a PR that should address some issues, it updates to a newer version of the notification script, adds a service worker which in my testing worked well with android / chrome, tried to make the ajax polling more persistent, plus a couple of other minor things. For 2.0 we can consider doing the change over to full "push" like xenforo has and I do have that working but have not spent any time integrating that into the core, hoping that the 1.1.7 updates get us close enough to what is needed. So thats kind of it for now or at least until 1.1.7 gets finalized.