partial uid match, auto write & nfc texting with OTR

[TameOfGroans]

each tag has a unique identifier. Often tags purchased in quantity have sequentially identifiers. Each write also can increment an on nfc counter.

For nfc conversing could it make sense to log identifier base [partial match], and write count, to allow tackling multiple conversation partners in app? Further provide option to log threaded conversation thus far [preferably local encryption]?

Better yet OTR for nfc texting [analog of Xmpp Texting with OTR]

[mofosyne]

Interesting. Well don't forget that most tags are 888bytes so minimizing
metadata is a priority (thus optional timestamp.

Also hard to guard against spoofing of previous conversation, because
anyone can edit the tag with the right software.

But good idea on write count and threaded conversations. I am short on time
however, but will accept any code contributions over git (with credits to
you as well)

For more advanced features, it would be useful if targeting cards like the
8k desfire. There will be enough room to start thinking advance features.
Only issue is cost for now (but good if it's in a widely accessed place.

Cheers and keep it coming. Any luck with the tags?
On 18/04/2015 7:56 am, "TameOfGroans" notifications@github.com wrote:

each tag has a unique identifier. Often tags purchased in quantity have
sequentially identifiers. Each write also can increment an on nfc counter.

For nfc conversing could it make sense to log identifier base [partial
match], and write count, to allow tackling multiple conversation partners
in app? Further provide option to log threaded conversation thus far
[preferably local encryption]?

Better yet OTR for nfc texting [analog of Xmpp Texting with OTR]

—
Reply to this email directly or view it on GitHub
#1.