| |
|
I have interpreted Haus' posts above to indicate that the possibility of Tom making small non time consuming changes is not completely outside of the realm of possibility.
Well, it's not beyond the realms of possibiility, but precedent suggests that it might not happen - if I recall correctly, when the recently updated functionality was introduced, it led to a degree of unhappy comment to the effect that this was nice, but it was not any of the things that were being requested. However, we could make a list of specific, small changes we might ask to be made, as long as we understand that:
1) The only person who will be able to access the back end to make them is Tom (and theoretically Cal).
2) As such, if Tom does not have time to do it or is not sure how to do it - or indeed does not _want_ to do it - then it will not be done.
3) This means that things that may seem quite easy to the outside observer may be, functionally, impossible.
So, based on this model and on experience, there is a better-than-normal chance that any proposed change will not happen.
That said, if you fancy it, you might do it by, say, starting a thread titled "specific, small actions to be put in place before any chance to admissions", and list change, reason and benefit. So, as an example.
CHANGE: Applicants have to type in random set of letters and numbers arranged on a coloured background to validate their entry.
REASON: Bots, spammers and trolls can otherwise easily and automatically register large numbers of suits without countermeasures.
BENEFIT: Suits will not be registered as easily by trolls, spammers and bots, without significantly increasing the complication of registering a single suit for legal use.
CHANGE: Instead of allowing users to set their own passwords, a randomly-generated password is sent to their registered email address.
REASON: Currently, the process of validating users' unique email address is handled by a human being. Without this human interface, false email addresses could be used to generate very large numbers of suits.
BENEFIT: Each suit would be tied to a specific email address, which will not slow the registration of a single suit for legal usage to any significant degree, but will slow mass registration of suits for illegal purposes.
CHANGE: Only one suit can be registered per session (using cookies, e.g.).
REASON: Only one suit, generally, should need to be registered per session by any user.
BENEFIT: Mass registration of suits for illegal purposes would be made slightly more difficult and time-consuming, without affecting the experience of registering a single suit for legal uses.
CHANGE: Creation of a page containing terms and conditions, which need to be agreed to using a checkbox before registration can complete.
And so on.
However, if you do so you should accept that the chances of these very sensible, relatively simple-looking changes actually being made are from the lessons of history slim to none. |
|
|
