showcase your favourite first world problems
Best posts made by fatbull
-
RE: The Official First World Problems Threadβ’
-
RE: How One Stupid Tweet Blew Up Justine Saccoβs Life (article)
Twitter makes it even easier to fuck up, since you only have 140 characters to work with and have to compress everything down to that.
Now I am become Twitter, destroyer of words.
The views, opinions and positions expressed by the author in this post do not necessarily reflect the views, opinions and positions of the author of this post.
-
Missing parentheses after link
Input:
[foo](http://example.org/)(foo) [bar](http://example.org/)(bar )
Expected:
Actual:
-
RE: The "fa-spin" Testing Thread
Span, span, span, span, lovely span, wonderful span ...
-
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: Unix Haters' Club
Ah, the "everything is a $thing" mentality.
Why, yes, everything is a stream of bytes. If something can be stored on a computer, it can be dumped as a stream of bytes. That's trivial. The reverse direction is the problem. A stream of bytes is not a pretty much anything else.
In any Real Programming Languageβ’ you have data types. In Java, for example, everything (or almost everything) is an Object, but you can easily cast it back to String[], List<?>, InputStream, or whatever it is. And even if you have an actual stream of bytes, there is usually an obvious way to parse it and turn it into something useful.
Try that in a shell script. No, that stream of bytes
find
just dumped is not an array of file names. It's just a stream of bytes. Really. We separate file names with 0x0A bytes, but those could be part of filenames, too, so you can never be sure. It's just a stream of bytes, after all. You cangrep
it,sed
it,cut
it, or write it to a file if you want, but it's still just a stream of bytes. Don't you dare process it! Because there is no way to actually do that safely and portably.
Filed under: Apparently escaping strings is NP hard.
-
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).
-
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: Unix Haters' Club
Filed under: An easy mistake to make, I mean, the keys are right next to each other.
A few weeks ago I managed to delete a script I had been working on all day and was about to add/commit, just by running
git clean -fx
instead ofgit clean -fX
.
Filed under: I was able to recover it from Eclipse's Local History, though.
-
RE: Some proposed Discourse improvements for TDWTF
Why not?
Pick a reasonable default height (e.g., 10em) and add placeholders for all other posts before and after the current view. When a post is rendered for the first time, adjust the layout as necessary. When a post is unloaded, keep a placeholder with the same height.
Of course that's not 100% accurate, but it is certainly feasible, and probably less confusing than the current behavior.
-
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.
-
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
-
RE: A "don't do wrong broken shit" checkbox in Visual Studio? You wish.
As the saying goes, every feature you can't turn off is a bug.
-
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: 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?
-
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")
-
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: Am I the dumb? Why are we rolling our own Destroy logic?
@tsaukpaetra What happens if you call Dequeue() on an empty queue? Who frees the memory after the dtor has been called? It might be a better idea to use InterlockedExchange or an event or a critical section or something similar to synchronize access to that flag.
-
Title has already been used posted in Side Bar WTF
-
RE: Firefox Users Can't Keep Up, all your grumpy cats are mine.
Every time I read one of those misspellings I imagine this guy saying it.
Filed under: Guybrush Atwood
-
RE: Some proposed Discourse improvements for TDWTF
I'm just not convinced that average people really want to move to arbitrary posts in the stream that often
I have to agree here. How am I supposed to know the number of the post I want to jump to? Guess? Memorize?Moving around quickly and efficiently is important, especially in long discussions, but jumping by typing random numbers is just a kludge.
But seriously, I was thinking maybe clicking / tapping on the progress bar expands it substantially (up) to show a bunch of things:
-
date ranges of activity, with targets to move to
-
arbitrary move to post number entry box
-
move top
-
move bottom
-
move top 20%
-
move bottom 20%
Jump targets I would find useful:-
move to top/bottom
-
move to first unread post
-
a list of my own/bookmarked/liked posts in this topic
-
move by Β±50 posts
-
maybe date ranges
-