Interesting subject
For a forum, for example, I as the administrator can set some tests so that the user joining the system can be automatically judged to be 'human' and not some program trying to join just to post spam.
The test is usually a question that the user has to answer 'how many letters in this word' etc. just so that it would be hard for someone to write a script to get around it.
I did this manually to begin with and spent a lot of time deleting bogus 'users' but the simple question 'filter' above has so far been enough to keep the spammers at bay.
Here you can equate 'spammers' with nefarious users who have nothing better to do than to try to destroy your system ...
go figure.
Anyway this is part of the same principal, once you have 'trusted' users then there is always the chance that they might accidentally input some bad data, not that they mean to but in the case of your WiFi hotspots for example they might miss out a digit in the coordinates and you have bad data that filters down to everyone... perhaps a system where someone enters a WiFi hotspot and it is published to everyone but there is a 'confirmed' count which goes up as other users confirm that this WiFi hotspot exists?
For the school timetable it might be enough to limit the ability to edit and submit to a few 'trusted' users?
Good subject and quite fascinating!
:wav: