OBSERVER fits header field addition request

Glabella

Could you add an to the subs fit header an OBSERVER or OBSERVER_EMAIL FITS header field that is passed from SeeStar App when executing an imaging session that creates subs. This potentially small request would improve provenance tracking for multi-user telescopes ensuring consistent metadata across your imaging platforms. Since Seestar app already authenticates users by email this could be a minimal addition with huge rewards forthcoming. With your newly added NETWORKING workflow this can align greatly with your future direction. Whether it’s the email or additional nickname field whichever is verifiably unique and authenticated would be ideal. I hope you will give due consideration to this request. Truly; Happy Seestar S50 user.

Support@Seestar

Of course, I hope the team can implement this as soon as possible after evaluation.

marvindj

Please do not put my email address in any FITS information. Use nickname instead.

Glabella

marvindj curious if you send your fit images to others or why you would be concerned. It wouldn’t be associated in the header with any password either. Perhaps if it’s set to not be supplied but only if one toggles it for inclusion into the header. However curious though as to who gets access to your email from a fit file in any event

marvindj

marvindj The last thing I need is for a fits file to escape out into the wild and suddenly my email address is exposed. It's not just gaining access, it's being flooded with spam. Non starter. Also, who knows who could hack this Telescope Network and obtain files that would be stored in a ZWO cloud (I'm assuming this will be made available with the Telescope Network).

Glabella

If for some reason, people don’t want their email or their unique identifier in the fits header then perhaps this could be set to null by default and only if the user toggles t in the Seestar app to be inserted.

marvindj

Also, the FITS header already uniquely identifies your Seestar by appending the serial number. That's enough info (in my opinion), but I understand why you'd like a more recognizable label. NICKNAME works.

Glabella

marvindj I guess I don’t get you. Your email is already on ZWO servers to be able to respond to this thread . Are you telling me that your email is not already out there with any commercial Enterprises for example… Google Facebook Microsoft , your own ISP?

marvindj

The less personal data the better. If that doesn't resonate with you, then ya, I guess you don't get my position. NICKNAME type label is fine. My email address is not.

marvindj

And a quick look at the SS app, there already exist A NICKNAME field in the account security section. Map that into a fits header field if this request is to be accepted. use your email address if you choose. Leave blank if you choose. Win-Win....