Given I have an alpha blank/white, and two substituted black/black sigs, I'd discourage black/black or white/white or transparent/transparent.

I do find the clash visually, even to other people when they see the transition of black white very distracting. I wear my b/w alpha on my thumb and if it happens to slip around from its usable position, which is basically chip side down inner and other thumb edge, The transparent looks good, with the black being very constrasting/distracting - more so that the silver on my alpha.

Could the transparent have a tinted aspect, i.e. so we could have two transparents but with a tint which means we can tell them apart!

Looking at a completely arbitrary rsa2048 certificate and an ecdsa P384 one (just because I have them handy) they are around 1600 and 1400 bytes respectively.

One time only, but was repeatable from my chrome session until I used the login to reply option, so I thought I should mention it.

I thought it was particularly interesting that the in topic 'login to reply' option behaved correctly but the main forum login did not. Presuambly they hit a different URI point and that is the source of the oddity.

Just had mine, delivered along side my ks2016 package - I'd two new one old my voucher so I'd had the alpha signature immediately the vouchers were issued..

Since we had the forum reskin last week, or whenever, I find that I consistently have 2 notifications being marked as unread/new. Using 'see all notifications' reports no notifications. Using mark all notifications as read, removes the current '2' count, until it reappears later, typically the next day.

For me clearing the notifications does clear them, until it brings them back, irrespective of f5/cache clearing. Admittedly they were not present today, though did reappear after my earlier report.

Since we had the forum reskin last week, or whenever, I find that I consistently have 2 notifications being marked as unread/new. Using 'see all notifications' reports no notifications. Using mark all notifications as read, removes the current '2' count, until it reappears later, typically the next day.

With my recent receipt of my KS2016 rings I've cleared down the tags I've registered in the unlock app to see if my Note 3 was any less likely to use smart lock for more than a few minutes (so far not so much). However I did notice with my horizon that several nfc capable apps on my phone into a frenzy of detection at one point recently, when I was not even trying to scan - so much so usual - however amongst the apps in question (nfc taginfo/nxp tagwriter/), was the nfc unlock app which had no rings registered, and if I'd not enabled a pin previously might have caused some difficulties.

Apologies if this has been covered to death already but since I'm one of those with stock android where smart lock works for minutes, I'm curious about the basic differences between the app versus smart lock.

So if I register a ring/facet/tag with the nfc unlock app I consume that facet's space to the tune of MIME:nfcringunlock/key, where in smartlock mode my tags are otherwise left free.

I'm curious why the nfc unlock version went with using a mime tag to trigger the unlock rather than some aspect of the ndef etc for the ring being registered.

I did configure mine, prior to switching to smart lock, to use my normal swipe pattern plus unlock nfc. Having removed all my registered rings leaving just the pin unlock in the nfc unlock I then had pattern + nfc ring password.

I recall that the username in the screen is all lower case, even if you submitted it from a mixed case email address, as I did.

Again as I recall when I mistakenly tried to register again with my ks2016 ones, using the lower case email address it told me I was already registered, per what the others are saying - only necessary once - though not obvious in the app itself..

All username lower case?

Removed all, then only added ks2016 ring same effect - works well for a short period then fails to play nicely with other there after.

Or my personal fav - your luggage unfortunately was damaged...

If they cannot have a master key for it they will just hacksaw or bolt cut it.