Standardised inter-cyborg protocol
06:39 <GarethTheGreat> we should both agree on a standard control module
06:39 <GarethTheGreat> if it can be standardised we could combine resources more easily
06:39 <Diethyl> yeah there are some similarities , I mean you have influenced me
06:40 <Diethyl> but there are a lot of extra things that I've added , that I'm certain no one has thought of yet
06:40 <GarethTheGreat> i'm going to build around intel edison just because it's an off the shelf part
06:40 <GarethTheGreat> any extras can be added in the bluetooth network
06:40 <Diethyl> it would be nice to standardize things or at least communication protocalls
06:40 <GarethTheGreat> bluetooth already exists
06:40 <GarethTheGreat> we could standardise on top of that
06:41 <Diethyl> I mean more in the way of exchanging data physically
06:41 <GarethTheGreat> well, realistically it has to be wireless
06:41 <GarethTheGreat> and why reinvent the wheel?
06:41 <GarethTheGreat> bluetooth and wifi already exist
06:41 <Diethyl> so when we are in public we can sense other cyborgs around us
06:41 <GarethTheGreat> ah
06:41 <GarethTheGreat> that'd be cool
06:42 <Diethyl> that and a handshake
06:42 <GarethTheGreat> brb
06:42 <Diethyl> to exchange data
06:42 <Diethyl> okay
06:43 <Diethyl> basically a protocall to exchange keys for a two way varification system
06:44 <Diethyl> I think it would be fun to be able to have the handshake actually be a physical handshake
06:47 <GarethTheGreat> could have each control module broadcast an ad-hoc wifi network by default named "CyborgNet"
06:48 <Diethyl> I'm thinking the implant would be somewhere in the forearm near the elbow , it seems like it would cause less problems there
06:48 <GarethTheGreat> have a UDP broadcast that contains basic details
06:48 <GarethTheGreat> name, supported features/implants, etc
06:48 <Diethyl> you would do a forearm handshake and you would be aligning the rfid on your hand with the reader on the other persons forearm
06:49 <GarethTheGreat> mind if i copy/paste these logs to the forums?
06:49 <GarethTheGreat> it's a cool idea that could do with some input
06:49 <Diethyl> yeah that would be awesome
Tagged:
Comments
An ad-hoc wifi network broadcast by an implant (the control module for my exocortex project) with the SSID CyborgNet, where each node broadcasts a UDP beacon advertising it's presence and giving details (user's name, list of implants etc, basic biographical data and optionally current GPS co-ordinates).
Combined with the subvocal recognition and bone conduction transducer this could also be used for silent communication cyborg-to-cyborg, and if both have an eyetap then realtime video streaming could be shared along with other arbitrary data.
Theoretically all of this stuff could be done with wearables to get mainstream appeal and it's the kind of thing that could be crowd funded on kickstarter or similar.
So I'm going to have the transducer (hopefully implanted at grind fest) transmit any phone auto to my implant. It also has a mic on it, so all you really need to do is come up with some kind of a connection between phones (in my case). But I really do like the edison idea. If a standard was set I think it would be cool if everyones implants connected and became a mess network.
Do you think a phone or a dedicated device is better to act as the hub/server for the cyborg body?
On another note, constantly broadcasting Wi-Fi is going to put a fair drain on battery systems. By the time this actually gets into the prototyping phase, I expect that we'll have developed graphene super-caps far enough to actually utilize them in a design.
As for wifi, well i'd be using it constantly anyway.
You could easily build this as a wearable, at least for proof of concept.
Basic housing encased on the forearm and transmission coming through on the palm. NFC would make it low-ish power, direct, and possibly more secure than transmitting all this data over WiFi.
You're effectively just exchanging a contact card. Combined with some decent AR glasses, you could communicate quietly across the protocol. You could even use phrase lists to communicate without speaking.
As for comms, see my exocortex thread - subvocal is what i'm looking into.
I really plan to go ahead with building a general-purpose embedded computer suitable for implantation for precisely this reason.
Need more CPU? Stick another implant in or use a wearable or an internet link, no need to pull the primary out.
Mobile internet is getting good enough now that it's feasible to do the heavy lifting on a remote server.
I think it would be wise to have some sort of active troubleshooting element on the hub that attempted to fix the error generated by a module, before it breaks the connection.