| *** flux <flux!flux@coffee.modeemi.fi> has joined #sailfishos-push | 04:45 | |
| flux | soo, to actually get a popup message to my user I suppose I need a particular client for it? | 16:18 |
|---|---|---|
| flux | most easily implemented with a shell script running mosquitto-client and dbus-send? | 16:19 |
| kimmoli | https://github.com/dm8tbr/irssi-mqtt-sailfish | 16:27 |
| kimmoli | my fork seems to have some deps fixed, and tuned notification for sf2.0 https://github.com/kimmoli/irssi-mqtt-sailfish | 16:29 |
| tbr | no pull requests? pah! | 16:29 |
| kimmoli | as requested https://github.com/dm8tbr/irssi-mqtt-sailfish/pull/3 | 16:30 |
| kimmoli | actually there was one alreday | 16:31 |
| kimmoli | not squashed | 16:31 |
| flux | so when I roam from wifi to 3g and vice versa, I've set up a script to reconnect my openvpn | 16:33 |
| flux | is this something I would like to hack to work with the mqtt client, or does it work out of the box? | 16:34 |
| flux | I guess the default value mqtt_keepalive = 210 in the .py suggests there's going to be at worse 210 second delay in reconnecting in that situation? | 16:34 |
| tbr | it will reconnect automagically | 16:35 |
| flux | instantaneously or after a timeout? | 16:36 |
| tbr | after timeout or when the TCP connection is lost | 16:37 |
| flux | not long ago a new feature arrived at the linux kernel: the ability to disconnect connections over an interface that has been brought down | 16:39 |
| flux | but I guess it'll be a while till it reached the Jolla :) | 16:39 |
| flux | in the meanwhile, a more active role (by monitoring the dbus) will dramatically improve the latency involved.. | 16:40 |
| tbr | well, I think that was always possible to reset TCP connections on ifdown | 16:41 |
| flux | I think it's _possible_ by injecting TCP reset packets, but how else is that possible? | 16:43 |
| tbr | IIRC it's a /proc/net parameter | 16:45 |
| flux | so I've been playing with the mosquitto_sub/pub. is there a way to receive messages that were published while disconncted? | 18:06 |
| flux | ok, in the publishing end I need to use qos 1 or 2 (ie. -q 1), as well as in the receiving gend, but also with mosquitto_sub I must use -c to prevent it from flusing the queue on input | 18:14 |
| flux | oh and the receiving end must use a client identifier (-i test) | 18:15 |
| tbr | yeah, there are quite a few moving parts. make sure to test thei behaviour to make sure they match you expectations | 19:08 |
| flux | gah, I made a debian package for my hack.. to remember that jolla runs on rpm :) | 19:33 |
| flux | there is no license in the irssi-mqtt-sailfish repo.. | 19:38 |
| flux | oops, missed it 8-) | 20:02 |
| *** ced117 <ced117!~ced117@opensuse/member/ced117> has quit IRC (Quit: Quitte) | 21:07 | |
| flux | the irssi script is a bit dangerous to use in shared hosting, given it passes the password in the command line to the external process.. | 21:08 |
| *** flux <flux!flux@coffee.modeemi.fi> has quit IRC (Read error: Connection reset by peer) | 22:03 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!