I think you should ignore everything in the other and separator categories when counting characters. Otherwise people will just use a different invisible character.
Posts made by fatbull
-
RE: (invalid title)
-
RE: Outdated Onebox Preview
Testing...
Edit: Apparently I can't onebox posts in this thread so I can't demonstrate it.
-
RE: Default quoting behaviour cannot quote code.
- Inline code works, but should not according to @codinghorror's comment above.
- Quoted code blocks don't work, but that was expected.
- A blank line magically "fixes" the code, but cuts the quote in half.
- A line of text "fixes" that again, but adds gibberish where my avatar should be.
- Somehow another line of code makes it even worse.
Here's a screenshot of the post's source, preview, and result:
Filed under: Markdown: 1, Sanity: 0
-
RE: Default quoting behaviour cannot quote code.
Testing...
Inline:
text `code` text
Block:
@fatbull said:
```
codeAdding a blank line: @fatbull said:<blockquote>``` code ```</blockquote> Adding text: @fatbull said:<blockquote>text
code
Adding more code: @fatbull said:<blockquote>text
code
code
-
RE: Random jumps on topic load
1. Open homepage
2. Scroll down a bit (trigger loading)
3. Click any random topic
4. Click the back button- Click the forward button
- Click the back button
- goto 5
When I do this, first the old page scrolls, then the new page loads.
-
Inconsistent links in "Likes" column
Open a large topic (more than 50 posts) by clicking on the ❤ link in the "Likes" column.
- Topic list: The topic opens in summary mode.
- Suggested topics: The topic opens normally.
-
RE: Poll: How do you use the forum software?
I receive my content via interpretive dance. They read each post and re-enact it.
Can you recommend an OCR package?
Filed under: Orgiastic Content Reenactment
-
*(**foo** bar)* still ignores bolding
Continuing the discussion from (foo bar) ignores bolding:
*(**foo** bar)* still ignores bolding
(foo bar) still ignores bolding
-
RE: Poll: How do you use the forum software?
Usually mouse wheel (if available) or Space/Shift+Space (otherwise).
-
RE: Progress bar doesn't show correct number of bottom-most post
Why don't you just show post numbers for each post? There's enough free space below the avatars. Then it's obvious which posts are visible and the progress bar doesn't have to be "smart" any more.
-
RE: Post indicator stops showing post X/Y after 999 posts
I'm not complaining about the lack of colors. I'm complaining about the lack of contrast.
For example, borders are very faint (#E9E9E9 vs. #FFFFFF).
-
RE: Post indicator stops showing post X/Y after 999 posts
Maybe I'm green/grey color blind?
It's more likely that you're grey/white color blind. I don't blame you. Most colors on this site are just slightly different shades of white.
I hate it.
-
Missing parentheses after link
Input:
[foo](http://example.org/)(foo) [bar](http://example.org/)(bar )
Expected:
Actual:
-
New posts show up in edit activity
My edit activity was open in another tab when I posted this. The new post was added to my edit activity, but disappeared when I reloaded the page.
-
Wrong post number in progress bar with End key
- Go to Poll: Remove bugs from front page.
- Press End twice.
-
RE: Poll: Remove bugs from front page
By using mute here a bunch of topics are going to be stuck in muted state which is bad.
Indeed.
I just unmuted Meta/Bug again and spent a few minutes unmuting new unread topics. Of course, they are no longer unread by now because the mute/track/watch dropdown is at the bottom.
-
RE: Poll: Remove bugs from front page
I don't think of this as a per-user setting, I think of it as a per-category setting that only admins can set.
Well, with a per-user setting and a per-category default you could, at the same time, ...
- show bread-and-butter categories by default and let users opt-out by muting them (e.g., Side Bar WTF) and
- hide less popular categories by default and let users opt-in by unmuting them (e.g., Meta/Bugs or subforums in foreign languages).
- Just yank category X off the latest page.
The latter seems to be the general intent when people use the feature.
I agree, but it's probably not that easy. There are a few cases where the current design makes no sense IMHO.
As an experiment, I muted the Meta/Bug category.
- Bug topics are now hidden from All Categories, but they still appear in the Meta category. They should be hidden there, too.
- All topics from muted categories are hidden. Watched topics should be visible regardless.
- I'm not sure if tracked topics should be visible as well. If yes, the "Automatically track topics" feature should ignore muted categories.
- I agree that
@username
mentions should work. It's a way to invite people to the one interesting topic in an otherwise uninteresting category. - Muted categories should be optional when searching.
-
RE: Category security takes no notice of manually set trust levels.
My understanding is that you still want anonymous lurkers to be able to read bugs, if you want that, you are talking about a new feature.
IMO this feature already exists. If you mute a category, its topics won't appear in the Latest list, but you can still access them. The only thing missing is a way to make categories Muted by default. Registered users can set it back to Regular/Tracking/Watching if desired.
-
RE: Category security takes no notice of manually set trust levels.
Double-left-click+drag from "p" to "1", right-click, open link.
Filed under: Shortest sequence of clicks, mouse movements, and keypresses to install Firefox not included.
-
RE: Broken images in edit history with Markdown view
@zogstrip This bug can be exploited. I've sent an email to team@discourse.org.
-
RE: Broken images in edit history with Markdown view
Markdown view is fixed, but HTML view still seems to be broken.
-
Undo undoes twice
Create a new post and type:
- A ("" → "a")
- Ctrl+Z ("a" → "")
- Ctrl+Y ("" → "a")
- B ("a" → "ab")
- Ctrl+Z ("ab" → "")
- Ctrl+Y ("" → "ab")
- C ("ab" → "abc")
- Ctrl+Z ("abc" → "a")
- Ctrl+Y ("a" → "abc")
- Backspace ("abc" → "ab")
- Ctrl+Z (nothing happens)
- Ctrl+Y (nothing happens)
- D ("ab" → "abd")
- Ctrl+Z ("abd" → "abc")
- Ctrl+Y ("abc" → "abd")
-
RE: FAQ requests.
The new "Bug" color is too similar to the page background. It is no longer recognizable as a category name.
-
Order of post actions
Is there a reason why post actions are ordered the way they currently are? I'd rather group related actions (where
|
is a vertical separator):Like Flag | Share Bookmark | Edit Delete Admin | Reply
Also, please don't hide the Like button. Disable it instead.
-
RE: Can't ctrl+click post datestamps
I usually Ctrl+👆 when I'm using my laptop because its touchpad doesn't have a middle button.
-
RE: System "downloaded local copies of images" job mangles img tags
Done.
Also, the RegExps don't catch every possibility. For example, it is allowed to add whitespace around
[img]
tags. I'm sure there are many more subtle differences between this and the actual parser.Wouldn't it be a lot easier to substitute images after a post has been "cooked"?
-
RE: Broken images in edit history with Markdown view
This applies to HTML view as well. The
<img>
tag is indented (i.e. in a code block) so it should never be rendered. -
RE: Unicode (of course)
Now if they could only fix Notepad to recognize LF line endings properly so I don't have to futz around with it's CRLF nonsense...
Try Notepad2. It handles different line endings and encodings just fine and has a number of useful features, but it's less bloated than other editors (it's not an IDE).
-
Control characters break RSS
Bug: Control characters break RSS feeds.
Repro:
- Post garbage: Here's an U+001B.
- Open RSS feed: http://what.thedailywtf.com/t/control-characters-break-rss/704.rss
-
Broken images in edit history with Markdown view
Bug: The edit history window displays broken images. It should not display images at all.
Repro: Open the edit history of System "downloaded local copies of images" job mangles img tags:
Edit: Why did it post an early draft instead of the final version?
-
RE: System "downloaded local copies of images" job mangles img tags
Yes, you can.
How do I report it? I'd rather not discuss this in public.
-
RE: Is using Discourse to track bugs a WTF?
You'll know it is fixed because your bug topic was closed
In theory. In practice, maybe you introduced a typo here, used a wrong color there, or made an off-by-one error somewhere else. Or maybe the repro wasn't clear enough and an edge case has been overlooked. IMHO minor issues like that don't justify a new topic.
Could you please wait a little longer before you close bug topics? Maybe a week after deployment?
-
RE: Is using Discourse to track bugs a WTF?
From a general software dev process standpoint, bugs/issues should not be modified/discussed/etc after deployment to production.
I'm a Discourse user, not a Discourse developer. Whatever changes have been made, I won't notice until after deployment to this site. Only then I can determine if my bug has been properly fixed. If it hasn't, I have to create a new topic about the same topic because the old topic has already been closed. What's the point of that?
-
RE: Is using Discourse to track bugs a WTF?
Status is indicated by whether the bug topic is currently open or closed.
No!
Some topics in the meta/bug category have already been closed. It is now impossible to discuss those fixes or reopen the bugs (at least for ordinary users). Closing a bug is necessary, but not sufficient for closing the discussion.
IMHO using Discourse to discuss bugs is not a WTF, but using Discourse in this way to track them is.
-
RE: Why does the URL change as I scroll through a topic?
How many results did you expect there to be for "confidence"? And wouldn't most people simply use the address bar for 1) domain name full or partial matches or 2) web search terms? I just think it's a really weird and unusual use case to expect to navigate in the address bar via random keyword matches on web page
<title>
tags...Note that the topic title is also part of the URL. Do you think it's a really weird and unusual use case to expect to navigate in the address bar via random keyword matches on web page addresses?
IMHO you should change the URL only when necessary (e.g., onbeforeunload) and not when scrolling.
-
RE: *(**foo** bar)* ignores bolding
_(**foo** bar)_
(foo bar)
*(__foo__ bar)*
(foo bar)
-
RE: Some proposed Discourse improvements for TDWTF
Only way to allow for this feature would be to provide another super intuitive way to mark a topic read.
Yes, please.
- A "mark topic read" button in the to-be-done progress bar popup
- A "mark read until here" button for each post
- (Should this button appear for "read" posts as well so you can "unread" or "rewind" a topic?)
- An indication of the "reading position" (Is the current post in the "read" or "unread" part of a topic?)
-
RE: Some proposed Discourse improvements for TDWTF
I follow about the request for dealing with "reading holes"
We do track exactly which posts your read and which not, so technically this is not too complicated, but, it makes marking mega topics "read" much more tedious...
Is that really necessary? Wouldn't a simple counter be sufficient?
Let's call it an "automatic bookmark":
- Initially, when a user visits a topic for the first time, bookmark the first post.
- When the user reads the bookmarked post, move the bookmark to the next post.
- When the user reads any other post, do nothing.
- Going to the "first unread post" takes the user straight to the bookmarked post.
- Marking a topic as "read" simply moves the bookmark to the end of the topic.
Seems straightforward. Am I missing something?
(I assumed
last_read_post_number
was more or less already doing this. That's why I wanted to change it.) -
RE: Some proposed Discourse improvements for TDWTF
Every link to the topic in the topic list, is already this.
By "explicit" I meant a link on the topic page itself (in its nav popup).
Exists on the unread tab, at the bottom.
That's a "mark forum unread" button, not a "mark topic unread" button. (Yes, I realize moving to the end of a topic currently has that effect, but that's exactly what I want to change.)
In general I feel most of the other points would be addressed by better, more explicit pop up nav when clicking the topic progress bar.
Feel? Most? Fine. Let me elaborate:
- Alice is a (new) forum user and just started reading Discourse and our reaction to it.
- After post 53 she decides to take a break and goes to lunch.
- In the meantime, Bob shares a link to post 210.
- Alice follows the link and likes the post.
- The next day, Alice wants to continue reading that topic, so she clicks on its link on the topic list.
- The forum software helpfully redirects her to post 211.
- Alice realizes that's not where she left off yesterday.
- Unfortunately, she cannot even vaguely remember the post's number, what it was about, or who wrote it because it was not particularly sexy/hilarious.
- But she knows that it was an earlier post, so she scrolls up. And up. And up. And dies a slow, agonizing death. Poor Alice.
Most of the time, Alice really wants to read topics from top to bottom, so the forum should actively support that and redirect her to post 54, not the middle of nowhere. A magical link in a popup isn't going to fix that.
FWIW, what I suggest might even be a small change to a single line of code. It may nevertheless turn out to be a bad idea, but we're not going to find out just by searching our feelings. I'm too busy/lazy to set up a dev env right now, and I already spent far too much time browsing the code, but maybe someone else is willing to give it a try?