Feel free to suggest alternate wording @chgoliz and @noahdjango!
Be the change you wish to see, etc!
Feel free to suggest alternate wording @chgoliz and @noahdjango!
Be the change you wish to see, etc!
I took a stab at it.
I guess what was most confusing to me was, when the menu pops up and we traditionally read from the top down, the first explanation immediately tells us to read the next one. this seemed backwards. explaining each option fully and not in reference to one you havenāt even read yet seemed more like reading and less like doing algebra. meh, to me itās better.
Watching
you will be notified of every new post within this topic, and the count of unread and new posts will also appear next to the topicās listing.
Tracking
you will be notified of any replies to your posts and also if your @name is mentioned. the count of all unread and new posts will also appear next to the topicās listing.
(but I donāt know how you officially refer to what Iām calling a ālisting.ā)
I kept wanting to refer to āthe thread,ā too, but I guess you donāt use that word since the whole threaded-vs-flat-comments debate?
do you think itās better, @chgoliz?
Yesā¦excellent point!
BTW, when I hit ā?ā I only get the shortcuts menu, not the definitions you originally provided a few posts above. So thereās that.
Hereās how Iād add to your changes:
I think the redundancy makes it clearer, and after all the point of a definitions list is to provide clarity.
well, thatās because ?
is the key command to view the listing of keyboard shortcuts. I think youāre confusing two separate threads weāre in. whoops, Iām not remembering this thread properly. however, I was trying to point out that the definitions are available from within a button that is always on the thread, nothing to do with the ?
list. if you look at the screencap above, you see the definitions are coming out of a button that, relative to your post at the time, was at the bottom of the comments and above the Suggested Topics box at the very bottom. That button is always thereāfor me, anyway. if you donāt see it, maybe thatās to do with your browser/mobile view/zoom in view.
anyway, as to the definition: youāre right. Iām guilty of trying to avoid that redundancy in the explanation, but I shouldnāt have. Youāre right to include it.
EDIT: strikethrusāsorry! it was both of us confused.
Oh, I see. I thought you were somehow pulling up the definitions as part of the shortcuts menu. Yeah, Iāve got that button tooā¦no problems there.
the irony is that I was editing that post for clarity right when you responded. but you understood me anyway because you are a smart
Okay, how the hell do you strike?
I googled all kinds of stuff about markdown but couldnāt find any mention of it.
http://daringfireball.net/projects/markdown/syntax#html
For any markup that is not covered by Markdownās syntax, you simply use HTML itself. Thereās no need to preface it or delimit it to indicate that youāre switching from Markdown to HTML; you just use the tags.
Dammit Woo!
Would some kind of summary of the formatting possibilities linked to on this page even be helpful?
I think I would have appreciated such a document when I first came here but I see reference above to the idiom about those who need help not seeking it.
Also, in my attempt to discover how to format comments on the BBS, Iāve discovered that to fully understand Discourse, I will have to learn Java and Ruby, get a better understanding of programming etc. That sort of self discovery might be more valuable if sought out oneself?
Itās all out there for anyone to google and Stackexchange seems to be a vast and bottomless resource for the interested and inclined partyā¦
I think there might be an interesting philosophical point concerning the value of work underlying this comment but I admit, itās quite tenuous.
Hmm, I hope thatās not true!
We do need a native formatting help page in Discourse for sure, but for now, hopefully http://superuser.com/editing-help should suffice!
Mostly I like hearing about (and observing) what people consistently find confusing, have trouble figuring out, etc. This topic is mostly about advanced usage.
My misunderstanding but perhaps also badly worded.
I didnāt mean that as a user I would have to learn programming but I thought Iād read that the resources Discourse was developed with included those languages.
[quote=āchgoliz, post:38, topic:15328ā]Watching
You will be notified of every new post within this topic, including replies to your posts and if your @name is mentioned. The count of unread and new posts will also appear next to the topicās listing.
Tracking
You will be notified of any replies to your posts and also if your @name is mentioned. The count of all unread and new posts will also appear next to the topicās listing.
[/quote]
The āincluding replies to your postsā in the first part seems awfully terribly redundant to me, since āevery new post within this topicā has to include replies to your posts, doesnāt it?
So I will change to this
Watching
You will be notified of every new post in this topic. The count of unread and new posts will also appear next to the topicās listing.
Tracking
You will be notified only if someone mentions your @name or replies to your post. The count of unread and new posts will also appear next to the topicās listing.
I think āthreadā is a needlessly complex, computer geek word.
Walk up to a person on the street and ask themā¦
What do you think about that thread?
⦠and theyāre likely to give you {insert cute confused dog picture here} look. Now if you ask them ā¦
What do you think about that topic?
⦠they might actually understand you.
Perfect!
We also added some better glyphs to help understand tracking and watching:
(that was on a PM so āregularā which has no glyph is not there)
I am running into some bugs here. I canāt undo likes any moreā¦?
just liked and unlikes your comment several times - will try liking it and un-liking it later.
40 min later and I cannot unlike your post
@Tribune and @MarjaE I cannot remember the time limit, but after a certain amount of time, I believe you cannot unlike comment if you have liked it. @codinghorror can provide more insight.