Hector’s Introduction

[Pilgrimsmaster]

Well I don’t want to tread on @ODaily toes, So maybe you should just carry on with your tutorial and get some more reading that will get you a badge or two…
Good luck

[LndSqd]

Workin my next for contact info sharing
Got a thread I can look at for that?

[Eriequiet]

@LndSqd

Workin my next for contact info sharing
Got a thread I can look at for that?

I can start one I suppose, or I can add new info to roscos vCard thread

[anon3825968]

Automated vCard writer (with photo)

I’ve done some more research and testing, and I found a two ways to increase photo quality even more: 1/ Decrease the image saturation: the end result looks less colorful, but the size of the compressed image decreases significantly 2/ Change file format from JPEG to WEBP. I’ve done tests on a few Android cellphone, and it turns out they all support WEBP natively down to at least Android v5. And boy! is WEBP better than JPEG or what! For the same final size, a WEBP image has a higher resolutio…

Android-only solution. If you want iPhones to read your vCard also, host it somewhere on the internet and stick a simple URL on the chip. But that requires the recipient to have the internet, and it’s not as instantaneous.

You can stick a decent size and fairly recognizable photo on a NExT. Mine is 60x60 and my mug is really quite realistic.

[Eriequiet]

I’ll start a new thread in a second @anon3825968, was building a dummy account to show as an example

It’s a pretty nice platform I found, and pretty fast to boot (assuming stupid android users have nfc turned on and don’t give me lip)
Works for both android and iOS

I guess yea they need internet, but they could just retain the link until they eventually have internet

What’s that? They will never have internet? Well how am I friends with them?

I was going to try to break their “proprietary” ntag213s but in the end I thought better of it, just found a nice loop hole that defeats the need to break their tags

[anon3825968]

As you may know, I don’t like solutions that require the internet and third-parties for no good reason. And I enjoy the challenge of fitting a photo on a chip. My solution is just one solution.

Having said that, yesterday I shared my contacts with a customer (so, no internet and no Big Data involved) and 2 seconds after getting my contacts - and my photo - they hit “Sync with Google” or something like that on their phone, much to my dismay. So much for trying to avoid stupid…

[teamhensler]

I learned something new about biohacker I didn’t now biohacker is small organization.

Biohacking

[Eriequiet]

@teamhensler

Did you look at the “nEXT” , “xNT” , “xSIID” implants to see if those interest you?

[Eriequiet]

@teamhensler

Did you look at the chip implants I suggested?

[teamhensler]

I did the advanced tutorial I completed it

[teamhensler]

Yes I did see it’s a cool microchip

[Pilgrimsmaster]

@teamhensler

I did the advanced tutorial I completed it

Nice work.

It looks like you have got quite a few badges and also it looks like you have spent quite a bit of time reading.

What does @ODaily have you working on?

[teamhensler]

He said I’m good to go he help me A lot to be a great member on the form.

[Pilgrimsmaster]

@teamhensler

he help me A lot to be a great member on the form.

Yes he’s has. Nice one @ODaily

After all of your reading, (15 hours) are there any questions you still have?

[teamhensler]

When was spark two was released I try to research that and it doesn’t show up nothing for me I was curious do you know the answer @Pilgrimsmaster.

[Pilgrimsmaster]

Thanks you for asking a question i know the answer to!

The Spark 2 was released almost a year ago (November 2019)

The Spark (original) was updated to the Spark 2 for a few reasons, one of the biggest was a change from ISO15693 to ISO14443A.

Let me get you Amals offical response from when I asked him about it, to explain and expand on it further.

UPDATE

@Amal

Hah… yep… so the Spark 2 is a new chip coming out very soon. It is essentially the same as the Spark but operates on the ISO14443A protocol instead of ISO15693. The reason for this switch has to do with limited support for ISO15693 in 3 key areas;

RF Protocol

1. Android has an NFC bug that makes reading ISO15693 chips unstable. We have submitted the issue to Google and even shipped demo cards to the Android engineer in charge of NFC in Singapore, but their understanding of the problem is pretty “iffy” and so far it’s not resulted in any fix for my Pixel 2, nor many other phones people are having problems using to read their Spark.
2. Apple’s iOS 13 release introduced many updates to NFC, allowing great access to many more features like direct-write and other stuff. Unfortunately, they still limit ISO15693 and we cannot send the cryptographic challenge commands we need to send to the Spark from iOS 13 devices.
3. 3rd party devices like door locks and access control systems are typically not able to read ISO15693, even though the hardware inside probably could. Firmware and application development around these devices tends to focus on ISO14443A.

For these reasons, we changed the chip type for the Spark 2 to operate as an ISO14443A, NFC Type 4 chip.

Scan Once
The new Spark 2 has the ability to append a CMAC signature to the NDEF URL. This allows us to create a “Scan Once” option for Spark 2 users which lets a person scan your chip once, but not reload that data or forward it on to anyone else. For example, you have your Spark 2 configured to show your VivoKey profile, and someone scans your chip at a conference or something. They can see your information, but if they try to reload that page or forward that link to someone else, it will not load a second time. This could be helpful in situations like sharing medical data with key people at the scene, but not letting them reload it later or forward that link to anyone else. It keeps access to scan data relevant to the current situation.

Custom NDEF Data
In the future, Spark 2 users will be able to overwrite the NDEF data on the chip itself (through the VivoKey app). The user memory space will not be open for all apps to write data to the Spark 2, just the VivoKey app will have the security keys required to access user memory, but content on the chip can be changed from the unique VivoKey URL on the Spark 2, and that unique VivoKey URL can also be re-written back to the Spark 2 if desired.

[teamhensler]

I will read the whole thing later have one more question when was the first Implant was invented because I tried to research it it doesn’t show up nothing for me I try my hardest for two days yeah I cannot find nothing do you have an answer for that i’ve been curious.

[Pilgrimsmaster]

@teamhensler

when was the first Implant was invented

Pet “tracker” ID chips have been around for around 40 years I think, I don’t know the exact date, I would have to google that myself, Amal was one of the pioneers, having his first implant in 2005.
There was somebody else pre year 2000, but that was more of a proof of concept and they took it out.

I am not 100% on all of the above, let me find you a link with all the information

[Pilgrimsmaster]

Here you go, The Wikipedia page, should have most of the answers for you

Microchip implant (human)

[teamhensler]

Thank you for the information I would enjoy reading OK that is all my questions.