The Official Good Ideas Thread™
-
Doesn't seem like they allow hotlinking. I copied to Discourse:
<img src="/uploads/default/15690/7f45d2ed9acd2016.png" width="636" height="367">
+Ϩ
Heh...I just saw this and was coming here (giggity) to post!
-
That's why you wear armour!
The armor1 may protect them from falling, but does it protect them from firing?
1 Spelled the way Crome's en-US speelchucker likes it
-
-
Energy crisis solved!
-
That's the worst product name ever.
—"Oh, gee ma, a wankband all off my own?! This is the best Christmas ever!"
—"That's right son, now you can quit using mine, which you never washed after you finished with it..."
*family hug*
-
Disgusting.
Have a like
-
"That's right son, now you can quit using mine, which you never washed after you finished with it...
...but that's OK, I like the taste."
"Is that why you've been serving broccoli every night?"
blushes
-
-
-
I'm not generally a fan of breast implants, but maybe I've been too hasty:
-
Practical!
Maybe I've been too hasty too.
-
Maybe I've been too hasty too.
Watch it again and contemplate just how thoroughly practical it is…
-
May be good for absorbing recoil, but doesn't do shit for accuracy…
Unless you're looking down the sights, it's not worth bothering.
-
doesn't do shit for accuracy
I was too busy studying the “practicality” to worry about such minor things.
-
Anyone else hear that? Sounds faintly like something just went over his head.
-
Not only did it get fixed in Python in a day's time, the Python devs welcomed further automated analysis of the CPython codebase :)
QFT
-
further automated analysis of the CPython codebase
Ooh, ooh, did they discovered that it implements locking really badly?!?
Filed under: not that you need a robot to discover that...
-
Good idea: writing an announcement about a major fixed bug rather than putting one line of text in some patch notes somewhere:
Today we fixed a subtle pathfinding bug that had been in the game for a while.
We get many reports of issues in the game, and the trickiest ones are the reports of subtle, often fleeting timing issues that result in incorrect hero or spell behavior. The bug we fixed today was inside the pathfinding system, but it manifested in extremely rare cases around blink dagger usage. We’ve seen reports of weirdness around blink dagger usage for a long time, but every time we spent some time digging into it, we couldn’t reproduce the events in those reports. A couple of weeks ago we decided to add a lot more tracking data to replays, so that the next time we received a match ID it would tell us more.
Early this week, we got lucky. Or perhaps you could say Loda got very unlucky. In Esportal Dota 2 League game #2 between The Alliance and Ninjas in Pyjamas, Loda reproduced the pathfinding bug at 18:26 game time. As Slardar, Loda had given a move to position order near some trees, and the generated path included an erroneous sharp turn at the very last step. Just as Slardar reached this last step, Loda activated his blink dagger. However, since Slardar was incorrectly trying to turn at the same moment, he was no longer within the required 11.5 degrees of facing the target position. Many players forget that your Hero does have to face towards the blink target before the blink actually starts. Exactly 0.07 seconds later, before Slardar had completed turning back towards the blink target, Loda cast Slithereen Crush, which replaced the blink dagger order. Sorry Loda!
Once we received the report of this occurring, fixing the bug was straightforward, because we finally had what we needed: a match ID containing the bug at a known time, and a new replay with the full unit and command information for each player. It took only a few hours to carefully analyze that replay and figure out exactly what was going on, compared to the many prior days fruitlessly spent combing over code and user reports looking for clues. There may still be other bugs that result in weirdness around blink daggers, and it’ll take more replays to catch them, but at least we know that this one is no more.
So, if you’re one of the many players out there that are great at noticing the really fine details in this massively complex game we all love, make sure your reports include a match ID and rough game time at which the bug occurred, since replays are now much more helpful in debugging these rare issues. That information can be the difference between a bug being fixed in a day and a bug that plagues us for months.
-
Good idea: writing an announcement about a major fixed bug rather than putting one line of text in some patch notes somewhere:
Even better idea: putting the equivalent information in the commit history itself. No, not the chatty bits, but the info about what sequence of events caused it and how to hunt down equivalent stuff. Why? Because blogs too often get discontinued or moved without a good redirect system put in place. (Alternatively, issue DOIs for the blog entries! )
Test cases are good too, but rarely say much about the higher-level issues about how the bug coupled to other features to cause trouble.
-
Bravely jump forward and hope for the best
-
-
Would anyone like to explain to me why fullscreening a video and restoring it jumps me back ~100 posts and breaks scrolling until I refresh the tab?
Filed under: other than, y'know, the usual...
-
Would anyone like to explain to me why fullscreening a video and restoring it jumps me back ~100 posts and breaks scrolling until I refresh the tab?
Fullscreening doesn't mesh well with infiniscroll.
-
Fullscreening doesn't mesh well with infiniscroll.
Which is a shame, because base-jumping geese require all of the pixels!
-
Which is a shame, because base-jumping geese require all of the pixels!
When I was first watching it, I was like: "This video is perfect for the bad ideas thread.... oh... ok, I guess it's the good Ideas thread then."
-
I don't know who came up with the idea of prefixing thropics with a relevant Unicode character, but I'm going to say it's a good idea.
I have to ask though, why this thropic is currently prefixed with [size=40]💁[/size] (helpdesk).
Why not [size=40]💡[/size] (electric light bulb)?
-
Which is a shame, because base-jumping geese require all of the pixels!
Try opening the vid in a new tab, and fullscreening THAT. Yeah, you have to train yourself to do it. But it preserves your place.
-
Also, fucking BBC made it not available in the US. Anyone got a proxy?
-
I like it, and I have the power. So implemented!
-
Why not
💡
(electric light bulb)?
Because electric light bulbs don't look like that any more. They're all spirally-wirally twisty-wisty now.
The icon you used looks like a downward-pointing penis.
-
Because electric light bulbs don't look like that any more. They're all spirally-wirally twisty-wisty now.
The icon you used looks like a downward-pointing penis.
I present to you: the first person ever failing a Rorschach test!
-
They're all spirally-wirally twisty-wisty now.
Surprisingly, there doesn’t seem to be any Unicode characters for CFL and LED lights. Is the Unicode consortium even trying?
-
Boobs. Is there anything they can't do?
-
I don't know who came up with the idea of prefixing thropics with a relevant Unicode character, but I'm going to say it's a good idea.
:hand:
I wasn't sure whether you all would find it amusing or annoying, so I didn't exaggerate and only prefixed the titles of the most active topics. Glad to hear I'm not the only one who likes the idea.
I have to ask though, why this thropic is currently prefixed with
💁
(helpdesk).
Why not
💡
(electric light bulb)?
Because I wanted to use mostly WTFy* unicode characters. (Those which make you wonder about the drug habits of the members of the Unicode committee.)
* WTF as in "Why the fuck does this character even exist?"
-
Those which make you wonder about the drug habits of the members of the Unicode committee.
are you talking about the whole spec?
-
are you talking about the whole spec?
I think there wasn't that much drug use involved in the Unicode spec (outside the emoji, which are obviously deeply connected to hallucinogens). It's overall more related to stupid little academic disputes through the humanities, together with incorporation of some really stupid things from custom fonts that caught on widely.
-
Unicode should probably not have both Ω and Ω. One is enough.
-
Unicode should probably not have both Ω and Ω. One is enough.
I'm assuming one of those is OHM SIGN and the other is CAPITAL GREEK LETTER OMEGA?
But they're completely unrelated concepts—I can't possibly imagine how you'd get one confused with the other...
-
One is enough.
𝖨𝖿 𝗐𝖾 𝗐𝖾𝗋𝖾 𝗍𝖺𝗅𝗄𝗂𝗇𝗀 𝖺𝖻𝗈𝗎𝗍 𝖴+𝟣𝖣𝟧𝖠𝟢-𝖴+𝟣𝖣𝟩𝖤𝖡, 𝖨'𝖽 𝖺𝗀𝗋𝖾𝖾.
Filed under: plz check raw, that was a lot of effort for a minimal payoff...
-
Do we have a "fascinating inventions thread" yet?
-
One is enough.
What sort of horse has only one foot? Even two is not enough for the common case!
-
Who put the downward-pointing penis in the title?
-
Would 🏆 be more suitable?
-
But the ohm sign is a capital greek letter omega. Just like the sign for grams is a lowercase latin letter g. We don't need a unicode character for "gram sign".
Edit: I realize now that I may have whooshed, but just in case I didn't...
-
I need a Unicode character for my username, since it's obviously different than the Unicode characters it's composed of.
-
They should have never made unicode characters for accented letters. But I guess it's more important to support 1:1 conversion from every obscure character set than to have Unicode make any sense at all.
-
-
Or a one-foot-tall / one-foot-long horse.
-
But then again, he doesn't need any shoes, so we're already redundant!
-
Nothing would be more suitable.