@Edent what's so bad about <div> ... or: Why do you want to avoid them?

[plactagonic@f.cz]

@fbinin it started to be a standard on multiple government issued documents in EU.

It used to be that you needed to fill all the information in some form or someone else filled it for you. Now with NFC chip you just put it on reader and everything is already filled in.

They didn't collect anything different that they collected before, it just saves time.

[defectivewings@infosec.exchange]

@Edent
I had this same problem with my keycards in our datacenter! I originally had two cards on the same lanyard, one for each datacenter, but I was unable to get the readers to accept me. Once I separated them, they each worked properly.

[peturdainn@mastodon.social]

@rlonstein not really, I've done a project with a reader that handled ISO/IEC 14443 and 15693, and for both protocols there is collision handling possible: the reader will tell you that more than one tag answered to an inventory scan, and the n there's a defined algorithm to scan with a mask of UID bits so you can find all tags in the field.
My guess is that whoever implemented the gates just lets the read fail if a collision is detected.
@sjjh @Edent

[rlonstein@social.stonetools.tech]

@peturdainn @sjjh @Edent Cool. I knew it should be possible 😁 The prox card system was not mine and the reader I acquired was cheap and limited (there were somewhat frosty discussions with the building management at the time which is why I looked into it...). For the Skye devices, iirc, this was circa 2013, they did the right thing with reporting multiple tags but for NFC it was unreliable-- not to mention undesirable for our purpose-- to handle more than one MiFARE-style card at once.

[peturdainn@mastodon.social]

@rlonstein while this standard is neatly hidden behind swiss francs (ISO) there's this TI application note that spills the details:
https://www.ti.com/lit/an/sloa136/sloa136.pdf
When I wrote 'reader' earlier I meant the RF chip, because this is pretty low level stuff so if your reading equipment doesn't implement it there's no chance you can handle it...
@sjjh @Edent

[jamescrakemerani@hostux.social]

@Edent When I was younger (under 18), I remember that generally you can't use egates as a minor. Normally in UK airports I was directed to speak to one of the border control agents instead. But I remember in Canada they never checked. So every single time I entered the country, I would be forced to use the egate even though I knew it would fail (not telling me why but I eventually guessed it was because of my age).

[xgebi@hachyderm.io]

@Edent GrapheneOS has not been on my radar when I flashed my phone almost three years ago.

Tbh in the past three months they've raised my eyebrows a bit too many times.

[mjr@masto.bike]

@GrapheneOS but will you unban @Edent? That's the acid test here IMO.

[grapheneos@grapheneos.social]

@mjr @Edent Our team should not be getting personally attacked with name calling and insults because we wrote a sentence saying an encrypted email service is problematic without elaborating beyond that where we said it.

It's enough that that these services use web apps for them to be problematic. When Chrome apps were killed off, Signal didn't turn it into a web app because it would trust the web server to provide the correct code. Matrix, E2EE email, etc. largely get used via web apps.

[taziden@mstdn.fr]

@Edent what makes you think it's a "team"? A team implies it's more than one person.

[edent@mastodon.social]

@taziden Looking at the account's posting history, it appears almost non-stop. Well over a hundred in the last 24 hours alone.

If that isn't a team, then it is someone who isn't getting enough sleep.

[iris@neuromatch.social]

@GrapheneOS @Edent jumping in as an outsider: GrapheneOS, you realize that criticisms of behavior that this account is currently exhibiting are not personal attacks on individuals running the account, and that describing behavior as "hostile" is not the same as name-calling? As an account representing an organization, you can expect to be held to higher standards of being able to take cricicism without lashing out in response, moreover, and that's also not what I'm seeing here. This is not reflecting well on you.

[damien@layer8.space]

@GrapheneOS I have no involvement beyond what is posted here, but for the record:

1. Your reactions/replies ensure that I would not want to ever touch your project. If that's your goal, please carry on without changing anything.

2. I don't see any hate directed anywhere, by anyone, in any direction. This is not Twitter. There are some adults in the room capable of reading and forming their own opinions.

@Edent

[grapheneos@grapheneos.social]

@iris @Edent Suspensions were made on our forum due to personal attacks on our team including name calling and insults. Those were directed towards our team and specific people, not towards the project. Ongoing harassment was being alluded to as part of it. The suspensions which were made are not permanent but rather will be lifted one by one as the moderation team reviews what happened and talks to the people involved so that the situation doesn't happen again.

[grapheneos@grapheneos.social]

@damien @Edent Suspensions were made on our forum due to personal attacks on our team including name calling and insults. Those were directed towards our team and specific people, not towards the project. Ongoing harassment was being alluded to as part of it. The suspensions which were made are not permanent but rather will be lifted one by one as the moderation team reviews what happened and talks to the people involved so that the situation doesn't happen again.

[iris@neuromatch.social]

@GrapheneOS @Edent Even if I take your word for all of what you just said, this back-and-forth is what I'm seeing by virtue of following your account, and your post that I replied to made multiple references to someone not being a good supporter of the project. Not a good look.

[grapheneos@grapheneos.social]

@iris @Edent Our team shouldn't be getting called names and insulted by our users on our forum because they think we were taking too long to reply to a question. Within the context of ongoing bullying and harassment towards our team, we didn't find that acceptable. We aren't sure what to do about it now. The people involved are welcome to work it out with us but we aren't comfortable simply moving on from that.

[grapheneos@grapheneos.social]

@damien We're working things out with him and the others from that thread who were suspended so we've removed our posts. You're welcome to do the same if you want but it's fine if you don't. We plan on removing these 2 replies regardless.

[grapheneos@grapheneos.social]

@iris We're working things out with him and the others from that thread who were suspended so we've removed our posts. You're welcome to do the same if you want but it's fine if you don't. We plan on removing these 3 replies regardless.

[mjr@masto.bike]

@GrapheneOS not what I asked and the post I've seen wasn't name-calling (it was a personal insult, which also shouldn't happen) and it wasn't @Edent who posted it. A life ban for liking a post that needs to be edited by moderators seems like a fairly wild overreaction. Will you unban @Edent, please?

I realise it's your forum, so your right to decide, but this act looks a tad extreme. Did @Edent even get a warning before that?