4 ms·
"Kill cord" is jargon from jetskis, powerboats and treadmills, which often have a cord you attach to your body that cuts power if you are thrown off. [1] On Li
by michaelt 7y ago
"Kill cord" is jargon from jetskis, powerboats and treadmills, which often have a cord you attach to your body that cuts power if you are thrown off. [1]
On Linux there is blueproximity [2] that can lock (and if you like, unlock) your computer based on the proximity of a bluetooth device. My personal experience is that Bluetooth is frustratingly unreliable, and this package was no exception. But it's there if you'd like to try it!
[1] https://www.rya.org.uk/knowledge-advice/safe-boating/look-after-yourself/Pages/kill-cord.aspx https://www.rya.org.uk/knowledge-advice/safe-boating/look-af...
[2] http://www.daniloaz.com/en/automatically-lock-unlock-your-screen-by-bluetooth-device-proximity/ http://www.daniloaz.com/en/automatically-lock-unlock-your-sc...
- hutzlibu 7y agoIs it possible that the bluetooth unreliability was a driver issue and others work fine? In other words, did you test different bluetooth devices?
- michaelt 7y agoI only tested with my smartphone, as it's the only bluetooth device I reliably carry with me. I'm sure there are configurations that work - blueproximity probably worked well for its author, or they wouldn't have released it! And I gather Windows offers "Dynamic lock" which locks the screen based on bluetooth. However, having experienced bluetooth unreliability with Linux, Windows, Android and iPhone; and with mice, GPS receivers, cars, access control systems and sports watches; I am confident the unreliability was not unique to a single bluetooth device.
- Jamwinner 7y agoI used blueprox for years with no fuss. Might try a different bt dongle.
- Nextgrid 7y agoBluetooth on Linux is an unprecedented abomination. You’d think most of it would be similar to network interfaces, handled by the kernel with commands such as ip, iptables, etc to configure it? Wrong! Instead it’s mostly done in userspace and the tools to talk to it are using D-Bus which is an opaque, inconsistent, hard to understand mess which you can’t easily interact with programmatically. As horrible as BT itself is I’d give the protocol itself a break in this case and focus on the terrible implementation.
- jmercouris 7y agoD-Bus is not part of the problem... it is just the common bus for communication between user processes. It is in fact a very straightforwards and well implemented specification.
- catalogia 7y agoThe debacle that was kdbus (and the technical motivation behind it in the first place) makes me wonder about that 'well implemented' part.
- bsder 7y ago> D-Bus is not part of the problem Only in the sense that the bluetooth maintainers never completed the port to D-Bus. So, 25% of what you need to do with bluetooth needs to be done via kernel anyway. Bluetooth on Linux is a prime example of how open source can fail.
- shakna 7y agoThe Bluetooth stack itself is an overcomplicated, terrible specification that leads to most Bluetooth chips have an _incomplete_ port of their own vital functionality. It isn't shocking that the thing to talk to them isn't complete.