| 00:45.13 | *** join/#qi-hardware planasb (~planasb@78-61-86-243.static.zebra.lt) |
| 00:45.13 | *** join/#qi-hardware planasb (~planasb@unaffiliated/planasb) |
| 00:49.21 | *** join/#qi-hardware erichvk__ (~esh@ppp118-210-212-13.lns20.adl6.internode.on.net) |
| 01:22.20 | *** join/#qi-hardware strawberyargon (~starcard@host-78-151-194-165.as13285.net) |
| 01:29.32 | *** join/#qi-hardware strawberyargon (~starcard@host-78-151-194-165.as13285.net) |
| 02:45.48 | DocScrutinizer05 | basically the idea resp point of NFC is to sort-of 'replace' pairing like in BT by mere physical proximity. Augmented concepts involve e.g. shaking both devices (stacked) with one (same) hand in sync, creating a "shared secret" from acceleration |
| 02:49.29 | DocScrutinizer05 | I personally rather would have specified the mechanical interaction/linking between both devices as "knock one device with the other several times" - using timestamps and impact pulse shape this would allow shared secret without the need to hand your device to somebody else |
| 02:52.29 | DocScrutinizer05 | additionally one device could playback an audio (good old FSK-2400Hz code, or sth like that) the very moment both devices touch/impact, the other device can record this via mic and play the response on next impact |
| 02:55.55 | DocScrutinizer05 | when device receives a NFC signal trying to "pair" without subsequent "device-kiss" within a - say - 5s, it can yell an alarm for suspected intrusion attempt |
| 03:06.04 | wpwrak | yeah, three knocks is probably all you really need. but hey, then those nfc chips would be useless again :) |
| 03:07.15 | DocScrutinizer05 | nah, you still need NFC to communicate between the two devices |
| 03:14.50 | wpwrak | you could use BT for that, too |
| 04:12.01 | DocScrutinizer05 | afaik BT doesn't work in any 'open mode' (without pairing) |
| 04:13.48 | DocScrutinizer05 | so the missing features of NFC are the negative features of BT - funny, isn't it? ;-) |
| 04:14.20 | DocScrutinizer05 | also perfectly explains why e.g. Nokia uses NFC for BT pairing |
| 04:54.28 | DocScrutinizer05 | with BT you have an additional problem to select the right peer to pair to, when there are more than one other BT devices visible |
| 04:56.11 | DocScrutinizer05 | so even when you do the rather nonsensical "0000" pairing secret key stunt like nowadays many BT devices do, you still need to select *which* device to pair to |
| 05:07.05 | wpwrak | you could just try all you can reach |
| 05:08.53 | wpwrak | much like NFC does :) |
| 05:10.32 | *** join/#qi-hardware strawberyargon (~starcard@host-78-151-194-165.as13285.net) |
| 05:45.56 | *** join/#qi-hardware DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 11:25.08 | *** join/#qi-hardware eintopf_ (~eintopf@unaffiliated/eintopf) |
| 11:36.58 | *** join/#qi-hardware dandon (~dandon@185.16.52.81) |
| 12:50.32 | *** join/#qi-hardware wej (~j@2a03:1b20:3:f011::9e) |
| 16:34.19 | *** join/#qi-hardware wildlander (~wildlande@unaffiliated/wildlander) |
| 16:35.11 | *** join/#qi-hardware wildlander (~wildlande@unaffiliated/wildlander) |
| 22:10.15 | *** join/#qi-hardware sb0 (~lekernel@210006059234.ctinets.com) |