Situation: In every tour I mention that the participants should not use the navigation in data-derp, but follow the path of the houses and tables.
There are two reasons for this:
- Firstly, I want to keep track of the cohort and
- secondly, we want to be able to add additional content that is not reflected in data-derp.
In addition to mentioning it in the sessions, I always write this instruction in the chat. Nevertheless, there is at least one candidate in every tour who overlooks this information and is confused as a result.
Possible solution:
To prevent this confusion, it would be nice if the links to data-derp from gather.town would open without the navigation.
Technical implementation:
As a draft I wrote a feature, that disables the navigation when the page is called with a query parameter nav=false.
Discussion
The downside is that we have to edit every link in gather.town to add the new parameter.
Maybe it is possible to check for the referer, but I do not want to do this during a course and we also deal with iFrames, that could lead to misbehaviour of that feature. So a query parameter is the best solution in my opinion.
Situation: In every tour I mention that the participants should not use the navigation in data-derp, but follow the path of the houses and tables.
There are two reasons for this:
In addition to mentioning it in the sessions, I always write this instruction in the chat. Nevertheless, there is at least one candidate in every tour who overlooks this information and is confused as a result.
Possible solution:
To prevent this confusion, it would be nice if the links to data-derp from gather.town would open without the navigation.
Technical implementation:
As a draft I wrote a feature, that disables the navigation when the page is called with a query parameter
nav=false.Discussion
The downside is that we have to edit every link in gather.town to add the new parameter.
Maybe it is possible to check for the referer, but I do not want to do this during a course and we also deal with iFrames, that could lead to misbehaviour of that feature. So a query parameter is the best solution in my opinion.