For kibitzing - TSAB gazetteer entry

[Cobalt Greywalker]

From Rob:

---

Then volunteers (such as A.C.) stepped up to maintain the thing...

---

It's not so much a hobby for A.C. but a necessity. The White Stallion's transponder (despite ANYTHING tried, including several complete replacements and a kitbash by both A.C. and the Professor) keeps randomly changing to be uncomfortably close to any other available ships (USSR Pachinko was one she rather cringed at). A.C. maintains a backup of the master list because she's been reduced to sending out emails to the other maintainers saying what the Stallion's current squark is, and how it is different to ship x.
From Kokuten:

---

The Ship Registry Database is a very open conventional MySQL type database (I'm not database savvy to provide more details), with the primary focus on access restrictions being to _track_ changes and requests, additions and decisions.

---

Pretty much how I envisinged it. I just added constant Interwave link so the various masters can deal with queries.

---

A "Ship Recognition Database" is vastly different from a "Ship Registry Database", also. Any station or ship with a sophisticated enough AI (or smart enough owner), is going to maintain a profile database of emissions, engine, sillouhette, IFF squawk, and various other cues for identifying ships. This data is likely to be shared on a fairly open database, and on an informal level.

---

This is also tied into the 'Encounters Log' any registered vessel/station keeps. People usually check them at dock and pump the unrecognised hits to the general recognition system so people are aware of unregistered ships in an area of space. The recognised but unknown ships get added to the ships recognition DB.
It depends on how paranoid the A.I./pilot/captain is whether the Encounter Log keeps any of the recognised ships afterward.