User talk:Wallewekw
Welcome!
[edit]Hello, Wallewekw, and welcome to Wikipedia! Thank you for your contributions. I hope you like the place and decide to stay. Here are a few links to pages you might find helpful:
You may also want to complete the Wikipedia Adventure, an interactive tour that will help you learn the basics of editing Wikipedia. You can visit the Teahouse to ask questions or seek help.
Please remember to sign your messages on talk pages by typing four tildes (~~~~); this will automatically insert your username and the date. If you need help, check out Wikipedia:Questions, ask me on my talk page, or , and a volunteer should respond shortly. Again, welcome! Johnuniq (talk) 01:31, 12 March 2019 (UTC)
Thanks, but boy, what a stupid, non-intuitive implementation of "talk"
[edit]First, thanks to User:Johnuniq for his direct answer to my question about importing an external Wiki. It was a good, useful response.
Secondly, while I am very glad -- thrilled! -- to see Wikipedia re-focussing on discussion via Talk pages... based on what I see, a lead zeppelin has more chance of flying. This comes across like a caveman's idea of how a bicycle would work.
- You need a simple, obvious 'Reply' function, with a button that actually says 'Reply'. NO requirement for manually editing of existing text.
- Replies need to automatically maintain threading, so that discussions are easy to add and follow. Again, NO requirement for manually editing of existing text, or trying to manually try to figure out where to put things. People should not have to understand Wiki concepts in order to reply or to discuss Wiki content.
Nearly all of the long discussion on Talk pages seems to miss those two top, absolutely key points, and without them, IMHO, the whole thing is doomed.
I browsed the Talk discussion. Couldn't see a simple way of contributing that didn't involve editing the existing thread, so... to h*** with it. Kind of makes my point.
Oh, and please don't tell me I'm doing it wrong. When people don't understand a UI, you don't try to fix the people. You fix the UI. First principle of documentation.