The Warning at the start, who wrote that and why?
It is a bit of a turn-off.
Some aspects of Discourse seem odd. That is a good example.
What is the point of these top commentary messages?
Best wishes
TT
1 Like
yeah, I think that was @pmario? Hopefully he can give us some more background here on his thoughts.
I agree: I don’t think “staff messages” should be used other than in very small circumstances. It could just as well have been a comment.
@TiddlyTweeter there is no grand plan and @moderators are figuring it out as we go as well – thanks for kicking off this thread.
1 Like
I didn’t want to use a comment, because comments don’t disappear if deleted. Staff-messages can be removed without “message deleted” artefacts.
The point is, the message should be “a bit of a turn off”. That’s why I used a staff-message an not a user-comment.
The Showcase category should point to editions, that highlight examples of wikis that should be able to be used by users.
Many users don’t have a closer look at what they download, if it is posted as a Showcase. Showcase for me means, that it is a special wiki, ready for me to use if I do like it.
The problem with the mentioned wiki is, that it is an example linked to a pull request. It’s not sure if and how this PR will be merged. It’s highly experimental.
If someone uses this wiki for production it is guaranteed to fail in the future. That’s exactly, what the message says. I do like the PR and I support it at GitHub until it is ready to be merged. If it is merged I would be happy to have it mentioned publicly.
I hadn’t seen the banner but I think @TiddlyTweeter’s concerns are reasonable: such warnings should indicate that they come from the admins, and provide a link for further questions.
The wording of the warning is also important. In this case “can not” doesn’t carry quite the right meaning. I’d suggest that we develop standard wordings for the situations that warrant banners, and not leave it up to individual admins to try to come up with the best wording in the spur of the moment.
1 Like
I can change it to “should not” can remove the “Warning” at the beginning, but I think it would indicate that it’s fine to ignore the warning at all.
I can also remove the warning completely and let the community deal with the problems when they come up.
Thanks @pmario I think the idea of a warning banner is reasonable; we just need to agree the policies governing their usage and wording, so that there is transparency and the community can understand what’s going on.
1 Like
I think the note is a good idea. Tongue in cheek: “Forearming” instead of “warning”?
TiddlyTalk seemingly aiming to be all things to all people, it would be good to have some process to update important “heads-up” information like that.
At some point, the warning will no longer apply. So who/how/when/etc. related to updating the information, or just removing the information when it no longer applies?
Doing Wikipedia-like updating of TiddlyTalk sniffs like a hellish undertaking to me. In my mind, easier with a wiki than with a discussion forum, but whatever floats leaders’/curators’ boats.
Although I very much dislike Discourse (sensory overload every time I face TiddlyTalk), I think many aspects that may be off-putting are just natural “growing pains” as leaders/curators/admin figure things out.
To me, the growing pains are greater and will take longer to iron out because of trying to make TiddlyTalk all things (discussion forum, wiki, blog) all at once. Eventually, I’m sure all of the stars/moon/ducks will align neatly.
For regular Joe/Joanne-newbie-user, TiddlyTalk must seem busy. In my mind, not sure it is easy for a newcomer to jump in. Maybe that will get ironed out too.
1 Like
@pmario since you wrote it and I trust you, I know you must have had good reasons!
The problem is transparency, I think . Having pretty “heavy” messages like that happen at the top of threads without linkage to the moderator’s reasoning is a bit intimidating I think.
Just a comment
TT
Anything can be used for production use. People use duck (yes, it is “duck”) tape for all sorts of things that it shouldn’t be used for, including heating ducts. Just down the road someone will have to deal with the sticky residue and mess.
Maybe “… is not recommended for …”
or the bureaucratically vague
“Avoid use in a production environment.”
1 Like
Showcase is “here is a cool thing done with TW”. It’s a marketing channel. Some of the things won’t be stuff that anyone else can run at all — but merely something to look at and be inspired by. Your description is different than mine so we’ll have to decide.
If we had an Editions category (like the Plugins category) I agree that holding things to a higher bar makes sense.
I think it would help if we edited the About page to make this more clear. I also want to encourage more people to post screenshots — for what I think a Showcase should do.
We could also fully moderate that category so things don’t go live in that category until approved by a Showcase moderator team — so every post has a screenshot, certain info filled out, etc. What do you think @pmario?