OnlineStatus in groups general tab (with OpenSimulator)

For the most part, code exists as sole documentation, but there do exist several sites documenting pieces of the protocol, though most of those are already parts of opensim. There's always freenode irc channel #opensim-dev if you need help, and we're in #singularityviewer most of the time, patience is always required when visiting our irc channels, a lot of us are usually idle and will be available to answer later.

I totally agree that grid devs should correct this ASAP Beeing dev and owner myself, it was the 1970-01-01, what I stumbled and tried to correct. Found out that the XmlRpcCall from Flotsam module of OpenSim isnt even passing this value and trying to fix this brought me to here. But lets not view it from viewer devs or grid devs side, but from the user side: grid not talking at all is not 1970-01-01, it is "unknown" ... grid talking the wrong language is also "unknown" until it learns the correct language users should not suffer cause of this with a viewer crash.

This might be a bit off topic here now, but is there somewhere a reference page to read how the viewer sends or expect to read values for certain things? E.g. besides of this group online status also the "most recent" column in the object list of the "about land" tab, but there are several others I would wish to send the viewer the correct information

Greetz
FoTo50

Comment by: i...@powerdesign.at

Unknown means unknown by the grid (database broke somehow) or to the user (not part of group, must join to see)
Invalid values sent by the grid will NEVER parse correctly, and therefore the best thing to do is to guide the grid developers to correct this ASAP so that they will, because the grid wants us to know, it's not unknown, the grid just isn't speaking in the right language yet.

Heh, ok, is better than currently But I think in case of invalid values displaying just "unknown" and not crashing at all would be the expected behaviour in this case, no?

Comment by: i...@powerdesign.at

Alright, better than flat out crash is crashing with a message explaining the crash so the grid devs can fix it, so that's what we'll do.