| *** Merbot` has joined #sailfishos-push | 09:44 | |
| tbr | :D | 09:44 |
|---|---|---|
| *** Merbot` is now known as Merbot | 09:44 | |
| *** ChanServ sets mode: -s+tc | 09:45 | |
| Stskeeps | [11:45] -ChanServ(ChanServ@services.)- Flags +AFRfiorstv were set on DM8TBR in #sailfishos-push. | 09:46 |
| tbr | tnx | 09:46 |
| Stskeeps | just do ze needful from now on, i'm on not-publically-told holiday so i may vanish at any time | 09:46 |
| *** tbr changes topic to "Discussion about push notifications on SailfishOS | For MQTT developer test accounts, message tbr" | 09:47 | |
| tbr | *nod* | 09:47 |
| Stskeeps | feel free to add a 'official' | 09:47 |
| *** tbr changes topic to "Official discussion about push notifications on SailfishOS | For MQTT developer test accounts, message tbr" | 09:47 | |
| *** kimmoli has joined #sailfishos-push | 09:48 | |
| kimmoli | \o | 09:48 |
| tbr | 'sup | 09:51 |
| kimmoli | had to kill vm-headless to get mersdk started again | 09:55 |
| kimmoli | hmm.. there is libmosquittopp-devel too? isnt that for c++ -- -maybe better for Qt | 10:02 |
| kimmoli | and founded as /#include <mosquittopp.h> | 10:04 |
| kimmoli | it will need also libmosquitto-devel seems so | 10:06 |
| kimmoli | mybe | 10:07 |
| tbr | yes, I mentioned that yesterday | 10:09 |
| tbr | but you had it already working with the C API | 10:09 |
| kimmoli | i was too hätänen | 10:13 |
| kimmoli | did you get pyhton to work? | 10:14 |
| kimmoli | obviously g+ | 10:15 |
| tbr | yes | 10:27 |
| tbr | was soooper simple, as I already had some code that I could kang from the toilet | 10:27 |
| tbr | also the python-mqtt docs are good | 10:28 |
| tbr | the only things I'd need to add would be a notification sound and vibration and I'd have my irssi notifier ready to go on the jolla side | 10:28 |
| kimmoli | oo | 10:29 |
| kimmoli | not much irc ++ G+ i see, no new members here | 10:29 |
| tbr | the irssi side shouldn't hurt either as I have a nice code base from the XMPP notifier that I maintain for irssi | 10:30 |
| tbr | just need to find some perl mqtt binding | 10:30 |
| kimmoli | perl... mmm..... | 10:31 |
| *** smoku_ has joined #sailfishos-push | 10:33 | |
| tbr | witamy | 10:33 |
| smoku_ | hi | 10:33 |
| smoku_ | Stskeeps: grats :) | 10:34 |
| tbr | smoku_: I guess you'll want some accounts for playing? | 10:36 |
| Stskeeps | o/ smoku_ | 10:37 |
| smoku_ | tbr: it's Stskeeps indoctrinating you with polish? ;-) | 10:39 |
| Stskeeps | tbr probably speaks better polish than me | 10:39 |
| Stskeeps | :P | 10:39 |
| smoku_ | tbr: I don't have an application for MQTT yet, so thanks... but I am interested in the domain | 10:40 |
| tbr | ok | 10:40 |
| smoku_ | oh... in that case | 10:40 |
| smoku_ | tbr: cześć :) | 10:40 |
| tbr | siema :) | 10:41 |
| smoku_ | dobrze | 10:42 |
| kimmoli | aha | 10:42 |
| tbr | I wanted to have sensible push notifications since Meego Community Edition | 10:43 |
| tbr | For a while I wanted to use XMPP and telepathy as the transport | 10:43 |
| tbr | but MQTT seems well suited and less overhead | 10:43 |
| tbr | also supports QoS | 10:43 |
| kimmoli | oo, my qt app did publish | 10:44 |
| tbr | my use cases are (IRC) notifications to my mobile device | 10:44 |
| smoku_ | XMPP sucks as a push transport | 10:44 |
| tbr | preferably propagated further to my smartwatch too | 10:44 |
| kimmoli | first make just simple test gui to publish and subscribe | 10:45 |
| * kimmoli makes | 10:45 | |
| tbr | yes, I know. It was more of a convenience thing. "platform already has XMPP and telepathy" | 10:45 |
| smoku_ | it's great for pub-sub as an additional feature once you keep an established connection already | 10:45 |
| smoku_ | but just for pub-sub - it has heavy overhead | 10:45 |
| smoku_ | btw, as I'm not familiar with MQTT - is it real push, or just plain periodically-pull game as always? | 10:48 |
| tbr | from what I've grokked so far it is an open TCP connection and the server will send data as soon as it gets it | 10:49 |
| *** coderus has joined #sailfishos-push | 10:49 | |
| coderus | :) | 10:49 |
| kimmoli | \o | 10:50 |
| tbr | apparently it was also intended for realtime/SCADA applications... | 10:50 |
| tbr | lo | 10:50 |
| coderus | give me link to mqtt docs pleast | 10:50 |
| coderus | please* | 10:50 |
| tbr | smoku:18084c01-e401-4920-833a-6f008c0b5c63 | 10:51 |
| tbr | smoku_read:f7c382c1-78e7-4cdf-95a8-c93d23134df0 | 10:51 |
| tbr | sorry | 10:51 |
| * tbr resets those credentials ;) | 10:51 | |
| tbr | http://mosquitto.org/ | 10:51 |
| tbr | coderus: that page links to what you need | 10:51 |
| smoku_ | coderus: http://mosquitto.org/man/mqtt-7.html | 10:52 |
| kimmoli | tbr: public passwords? | 10:53 |
| tbr | kimmoli: was a paste mistake, those have been reset | 10:53 |
| kimmoli | :p | 10:54 |
| tbr | btw: the devaamo.fi server also accepts unauthenticated connections on port 1884 for testing, but is limited and not intended for "production" use | 10:55 |
| * tbr ponders idly where in the mer wiki hierarchy he should anchor push notifications intended for use in mer utilizing projects (sailfish, nemo, etc) | 11:01 | |
| smoku_ | tbr: what is your idea for these push notifications? do you want to have an app receiving them or some background service? | 11:04 |
| tbr | smoku_: my current idea is to have a on device message broker of some sort that deals with the MQTT side and exposes dbus. that way it needs only ONE TCP connection. | 11:05 |
| tbr | but for exploration, testing, special cases using MQTT directly from inside an app might be useful too | 11:06 |
| kimmoli | i will publish the mqtt-test app soon,, when i get the credentials stored outside from sources first | 11:07 |
| smoku_ | ONE TCP connection to central broker. who will maintain this broker and its topic hierarchy? | 11:07 |
| tbr | currently I do. It runs on my private hardware. As it aligns well it is hosted under the domain name of Devaamo. | 11:10 |
| tbr | for a case where we implement per device authentication it will need some more elaborate authentication infrastructure though. Currently it's a manually maintained ACL and credential file each. | 11:11 |
| tbr | at that point also the question arises if we automate and use e.g. the device IMEI or if we have the user perform an additional manual step. | 11:12 |
| tbr | it's essentially a security question: whatsapp style insecurity, but ease OR more security, but a few steps to set up. | 11:13 |
| tbr | the good thing is, that there is an intermediate use case: broadcast | 11:13 |
| tbr | for that we can have anonymous clients connect to the broker and subscribe to sailfish/broadcast/... topics | 11:14 |
| tbr | writing to those is limited to certain accounts by ACL | 11:14 |
| kimmoli | oo | 11:27 |
| kimmoli | https://github.com/kimmoli/mqtt-test | 11:28 |
| kimmoli | not yet c++ api | 11:28 |
| kimmoli | but works, needs libmosquitto-devel and libmosquitto1 packages to be installed on sdk | 11:29 |
| kimmoli | iirc libmosquitto-devel pulls that other withit | 11:29 |
| kimmoli | but waiting tbr wiki (?) | 11:29 |
| tbr | soon™. just agreed with lbt where to put it | 11:30 |
| smoku_ | tbr: app-store integration seems to work well for android/ios. app-store client provides credentials to the device and app-store backend provides topic hierarchy for devs to use in their apps | 11:33 |
| smoku_ | tbr: also, I could envision credentials "pluggable" to the device broker service by installed apps - when you install an app, it provides broker address and credentials to the service and it opens a connection to broker and shares access to it over DBUS | 11:35 |
| smoku_ | (app store client could be one of that sources) | 11:36 |
| tbr | *nod* very good info | 11:37 |
| tbr | I'm not very familiar with how this works on other platforms | 11:37 |
| tbr | ideally it would integrate with the jolla account OAUTH | 11:37 |
| * smoku_ agrees | 11:38 | |
| tbr | https://wiki.merproject.org/wiki/Middleware/PushNotifications | 11:52 |
| tbr | kimmoli: wiki page now available | 11:52 |
| kimmoli | tbr: ok | 11:58 |
| kimmoli | hmm is it mosquitto_sub -d -h devaamo.fi -t sailfish/broadcast/# | 12:00 |
| kimmoli | how to publish there ? | 12:01 |
| tbr | I manually enable accounts to publish to particular topics there on request | 12:08 |
| kimmoli | aa ok | 12:09 |
| tbr | I should put up some generic test broadcast topics there | 12:10 |
| kimmoli | could you enable e.g. sailfish/broadcast/test to everyone ? | 12:10 |
| tbr | something like current time | 12:10 |
| tbr | enabled | 12:12 |
| kimmoli | öö, now getting Connection refused | 12:15 |
| tbr | ugh | 12:15 |
| kimmoli | Error: Yhteyttõ ei voi muodostaa, koska kohdekone ei salli sitõ. | 12:15 |
| tbr | let me check if I broke it | 12:15 |
| kimmoli | says windows client | 12:15 |
| tbr | yes I did | 12:15 |
| kimmoli | :) i got get some icecream | 12:16 |
| tbr | back in service | 12:16 |
| kimmoli | cant broadcast to .../test | 12:17 |
| kimmoli | should i? | 12:17 |
| tbr | let me try it. I'm still not solid at those ACLs | 12:21 |
| tbr | try again | 12:22 |
| kimmoli | Client mosqsub/11972-KL2011 received PUBLISH (d0, q0, r0, m0, 'sailfish/broadcast/test', ... (11 bytes)) | 12:23 |
| kimmoli | sailfish/broadcast/test hello world | 12:23 |
| tbr | I switched to per-user enabling, as there is no good way to enable this for all authenticated users, but disable for anonymous | 12:24 |
| kimmoli | ok | 12:25 |
| tbr | in the long run I want to look into a flexible authentication and ACL backend | 12:35 |
| kimmoli | one helpful link for api, http://mosquitto.org/api/files/mosquitto-h.html | 12:59 |
| *** s1gk1ll has joined #sailfishos-push | 15:03 | |
| *** ChanServ sets mode: -o Stskeeps | 20:34 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!