OSviewer/What is being sent to the Viewer Server
From OpenSimulator
CodyCooper (Talk | contribs) |
CodyCooper (Talk | contribs) |
||
| (3 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
| + | {{ViewerQuicklinks}} | ||
{{ViewerReleaseInfo}} | {{ViewerReleaseInfo}} | ||
| + | |||
| + | |||
How OSviewers handles: | How OSviewers handles: | ||
-Viewer blocks | -Viewer blocks | ||
| Line 10: | Line 13: | ||
== Viewer Blocks == | == Viewer Blocks == | ||
| − | File : [{{#var:vdataurl}}releases.xml | + | File : [{{#var:vdataurl}}releases.xml releases.xml] |
| + | |||
This file lists viewer versions which we have implemented a block. When the viewer launches it checks this file to see if its version is on this list. If it is.. it will not login and will display to the user a reason we can edit as to why it is not allowed. This is how we implement viewer blocks and as you can see it is not a virus or Trojan or backdoor to the viewer. | This file lists viewer versions which we have implemented a block. When the viewer launches it checks this file to see if its version is on this list. If it is.. it will not login and will display to the user a reason we can edit as to why it is not allowed. This is how we implement viewer blocks and as you can see it is not a virus or Trojan or backdoor to the viewer. | ||
It is important for us to have this capability because of the usage of the viewer. If there is enough users that it is easily possible we could release an update with a bug which could knock a grid offline, so we need to be able to block releases in a hurry. More recently however we are using it to block old out of date versions due to pressure from content creators who have customers buying merchandise but not seeing it correctly due to these customers being on old viewer versions. This capability is us being responsible.. period. | It is important for us to have this capability because of the usage of the viewer. If there is enough users that it is easily possible we could release an update with a bug which could knock a grid offline, so we need to be able to block releases in a hurry. More recently however we are using it to block old out of date versions due to pressure from content creators who have customers buying merchandise but not seeing it correctly due to these customers being on old viewer versions. This capability is us being responsible.. period. | ||
== Message of the Day == | == Message of the Day == | ||
| − | File : [{{#var:vdataurl}}data.xml | + | File : [{{#var:vdataurl}}data.xml data.xml] |
| + | |||
This file contains the Message of the Day. This is the message you see on screen along with the login progress indicator after you click login. This gives us the ability to communicate important information and messages to all our users at once. We use this to notify you of important things like new releases and events that benefit you and/or charities. | This file contains the Message of the Day. This is the message you see on screen along with the login progress indicator after you click login. This gives us the ability to communicate important information and messages to all our users at once. We use this to notify you of important things like new releases and events that benefit you and/or charities. | ||
== Official team members and support groups == | == Official team members and support groups == | ||
| − | File : [{{#var:vdataurl}}agents.xml | + | File : [{{#var:vdataurl}}agents.xml agents.xml] |
| + | |||
This file contains a list of all of our staff. When you open the profile of one of our staff you will see either “Support”, or “Developer” in the payment info used box. This is in place so that YOU know who is official and who is not since many claim to be part of our team and try to scam folks. It also allows our staff to request system information from you while in world (Which you have to approve when requested). It also loads up which groups are our official support groups and is how in our groups at the top is an option you can enable to include what version you are running next to your name in group chats. This makes providing support for you easier since we will know what version you are running. | This file contains a list of all of our staff. When you open the profile of one of our staff you will see either “Support”, or “Developer” in the payment info used box. This is in place so that YOU know who is official and who is not since many claim to be part of our team and try to scam folks. It also allows our staff to request system information from you while in world (Which you have to approve when requested). It also loads up which groups are our official support groups and is how in our groups at the top is an option you can enable to include what version you are running next to your name in group chats. This makes providing support for you easier since we will know what version you are running. | ||
== Grid Manager == | == Grid Manager == | ||
| − | File : [{{#var:vdataurl}}grids.xml | + | File : [{{#var:vdataurl}}grids.xml grids.xml] |
| + | |||
This is the list the viewer loads in order to offer default grids in the viewer. With this we are able to remotely add new grids to the viewer grid manager without having to issue viewer updates. | This is the list the viewer loads in order to offer default grids in the viewer. With this we are able to remotely add new grids to the viewer grid manager without having to issue viewer updates. | ||
Latest revision as of 06:10, 10 December 2018
How OSviewers handles: -Viewer blocks -Message Of The Day -Official team members and support groups -Grid Manager
When the OSviewer viewer launches it “reads” a couple files on our server which give it some instructions. These files can be seen below along with what instructions they provide the viewer and why. All of this is transparent and always has been. (NONE of the login information you input like username and password are sent to our server. This data is sent only to your grid and we NEVER read or store this information.)
Contents |
[edit] Viewer Blocks
File : releases.xml
This file lists viewer versions which we have implemented a block. When the viewer launches it checks this file to see if its version is on this list. If it is.. it will not login and will display to the user a reason we can edit as to why it is not allowed. This is how we implement viewer blocks and as you can see it is not a virus or Trojan or backdoor to the viewer.
It is important for us to have this capability because of the usage of the viewer. If there is enough users that it is easily possible we could release an update with a bug which could knock a grid offline, so we need to be able to block releases in a hurry. More recently however we are using it to block old out of date versions due to pressure from content creators who have customers buying merchandise but not seeing it correctly due to these customers being on old viewer versions. This capability is us being responsible.. period.
[edit] Message of the Day
File : data.xml
This file contains the Message of the Day. This is the message you see on screen along with the login progress indicator after you click login. This gives us the ability to communicate important information and messages to all our users at once. We use this to notify you of important things like new releases and events that benefit you and/or charities.
[edit] Official team members and support groups
File : agents.xml
This file contains a list of all of our staff. When you open the profile of one of our staff you will see either “Support”, or “Developer” in the payment info used box. This is in place so that YOU know who is official and who is not since many claim to be part of our team and try to scam folks. It also allows our staff to request system information from you while in world (Which you have to approve when requested). It also loads up which groups are our official support groups and is how in our groups at the top is an option you can enable to include what version you are running next to your name in group chats. This makes providing support for you easier since we will know what version you are running.
[edit] Grid Manager
File : grids.xml
This is the list the viewer loads in order to offer default grids in the viewer. With this we are able to remotely add new grids to the viewer grid manager without having to issue viewer updates.
