Just because a thread is read-only does not mean that the thread can't be used by the general public. We do use it - to find out who has had a name change and what they changed it to. The thread clearly and easily conveys the information it was created for, and is easy for Ming or whoever to update as they go. It is not just Ming who uses the thread, either. Besides the fact that he is not the only person to post in the thread (Mark and DanQ both have), the thread wasn't created for him, it was created for us. There are 1200+ views to that thread for a reason.
A link in the member page would be static. It would not change depending upon how many people had their names changed since you last checked. A thread, however, displays if a new entry is made in it - it is therefore easy to see at a glance if there are new changes since you last went to the community forum.
Besides, any alternate implementation of this feature would require Mark or Dan to spend even more of their precious spare time changing the members page, possibly even needing to edit the database. Plus the required testing. And for what end-result? To have one less thread in the Community forum that some people aren't interested in reading.
I don't see how changing the current situation could be justified.
A link in the member page would be static. It would not change depending upon how many people had their names changed since you last checked. A thread, however, displays if a new entry is made in it - it is therefore easy to see at a glance if there are new changes since you last went to the community forum.
Besides, any alternate implementation of this feature would require Mark or Dan to spend even more of their precious spare time changing the members page, possibly even needing to edit the database. Plus the required testing. And for what end-result? To have one less thread in the Community forum that some people aren't interested in reading.
I don't see how changing the current situation could be justified.
Comment