Psst....
-
-
A user's post count in the OP and on their user card leak that they made a "private" post in the topic as well.
-
Maybe it's a whisper? The "jump to" link shows number 29, and the visible posts are 28 and 30.
Confirmed:
-
From that thread:
Aww, whispers are hard.
-
Really?This one of @abarker's looked like it was a reply to a particular post?
Was a reply to another whisper.
-
I translated that post as follows: "We have a hacked to hell architecture, so actually getting this to work is impossible."
-
@hungrier said:
Maybe it's a whisper? The "jump to" link shows number 29, and the visible posts are 28 and 30.
Confirmed:
PMd this to @cpradio at meta.d. Figured I don't want to fly above the radar right now.
-
Ah, good find, @cpradio. He found us via discourse, IIRC, but he's One of Us.
Thanks! And I found most of those within Meta to boot!
PMd this to @cpradio at meta.d. Figured I don't want to fly above the radar right now.I'll update that topic accordingly.
-
pretending to be a bug tracker.
Because real bug trackers don't allow you to remove all traces of a bug you want to pretend doesn't exist.
-
I'll update that topic accordingly.
Aw, I was really hoping this would be reported first by a big, high-profile customer who was really pissed that confidential information got leaked. :(
-
Aw, I was really hoping this would be reported first by a big, high-profile customer who was really pissed that confidential information got leaked.
You are assuming their "high profile customers" will use it!
-
One can hope.
-
@HardwareGeek said:
Aw, I was really hoping this would be reported first by a big, high-profile customer who was really pissed that confidential information got leaked.
You are assuming their "high profile customers" will use it!
-
Well, I've already warned our community not to because of the leaks I found just watching Meta... so I'm not sure how many will be using it (at least any time soon)
I bet there is at least a couple more outlets too, I haven't tried finding them via search yet
-
That is the "high profile customer" I was specifically thinking of, yes.
-
Another semi-leakage
-
I wonder if they're visible in the JS-free/crawler version of the site?
Can't figure out how to disable javascript on anything offhand...
-
Doesn't look like it.
-
What happens if you mention someone who's not staff in a whisper?
-
@loopback0, can you hear me?
-
Let's test that idea:
-
Let's test that idea:
No mention, but it jumped to the top of the topic list with a blue circle, and now I have:
-
-
"originally thought" implies they actually thought about it in the first place.
-
So, about 8 hours:
They've fixed the discobools?
I'm sure those should be
false
andt
....
-
-
I'll fucking transgress Jeff.
Easy there fella. Beware of the cooties.
it is a bug
obfuscatorrepository pretending to be a bug tracker.FTFY
-
Zero is a legitimate number.
-
-
Zero is a legitimate number.
Remind me, what comes next in the following series...
XII
XI
X
IX
VIII
VII
VI
V
IIII
()III
II
I
...XII
is not an acceptable answer...
-
I wasn't talking about number concepts before mid 19th century. (Neither about their representations.) Btw, 1 (''one'') wasn't a proper number then, either.
(And the IIII comes from the use of the abbreviation IV for Jupiter (IVPPITER), and they didn't want to (ab)use the name of a deity for something mundane as a clock.)
-
And the IIII comes from the use of the abbreviation IV for Jupiter (IVPPITER), and they didn't want to (ab)use the name of a deity for something mundane as a clock
That's one**emphasized text explanation. Here's another:
Clock makers choose whichever number they feel is more aesthetically appealing and they often go with IIII because it balances better with VIII on the other side and makes the clock look more symmetrical. By the same token they use IX and not VIIII for 9 because it matches the III on the other side better.
-
LOL. We're the woodwork now.
-
https://what.thedailywtf.com/uploads/default/7354/fa95f206c5647e36.JPG
Filed under: No idea who posted this or where, Googles had it
-
-
-
That's, like, almost work...
This any better?
TOSHIBA P20 | N/Amm F2.5 1/8 ISO200 | 2014:09:30 23:37:21 | DVWare 1.0
As can be visually ascertained from the screenshot, it must be at least 9 months old - the greens are not blue enough and the blues are not grey enough...
-
You are assuming their "high profile customers" will use it!
I thought the only raisin this waste of resources was implemented over, say, bug-fixes, is because those mythical "paying customers" wanted it?
@meta.derp said:
#1 turns out is SUPER hard. I am thinking about it but it might require a large refactor
- Whispers are easy
- The way you're doing whispers is hard
2a) Even though you claimed they were easy - When you need to completely refactor a feature you wrote and released less that [del]1 week[/del]6 discodays ago, you need to burn the whole architecture to the ground
3a) Why are you starting again? I said burn it all to the ground. Then salt the earth. Then walk away in shame and never return.
@alicef said:
What happens if you set it to NULL?
It's a checkbox in the interface.Your point being? This is Discourse. There's a way for null to get in. And you can bet that way back out doesn't pass through TypecheckVille
And why did the thing to cancel the upload turn into a blue cross?
Cancelling uploads is a to dismissing other user's valid points with an image meme.
SO then, our options are:
- Wait for the next discoupdate, so that nothing will be fixed, more features will go away, more bugs will be introduced, and the UI will be completely fucked over?
- Roll back to the previous version which, as was pointed out in another thread, actually performs better than this "improved performance" version? **
** I would not be surprised if rolling back is impossible because the upgrade irreversibly fucked up the database structure somehow...
Filed under: How're those new forums coming along?
-
@Lorne_Kates said:
Your point being? This is Discourse. There's a way for null to get in. And you can bet that way back out doesn't pass through TypecheckVille
I'm not a tester at heart. I don't have the patience to find a way in. I let others do all the work and then sit back and laugh at the results. I checked, and that's a legit benefit of my privilege.
-
Bug: notifications page, when refreshed, doesn't show me which tab I'm on.
Should I file a bug on meta.derp?
http://i.imgur.com/HeKsXLK.png
edit**emphasized text: even better. The "All" red highlight does show. For about 0.5 seconds. Then some other style or script kicks in and hides****strong text the selected style on All.
Should I also filed that bug on meta.derp?
-
Messages does the same. Unless you're an Admin, then you see both tabs as normal.
edit: although it shows on meta.dickface so... *shrug*.
-
edit: although it shows on meta.dickface so... shrug.
That's because it was only recently fixed ;)
-
@Lorne_Kates said:
I thought the only raisin this waste of resources was implemented over, say, bug-fixes, is because those mythical "paying customers" wanted it?
You forgot the "or the powers that be over Discourse see value in it even if the customers haven't requested it yet". I don't recall how Whisper came about, I just know it was brought up and quickly happened within a discoweek.
-
@loopback0 said:
edit: although it shows on meta.dickface so... shrug.
That's because it was only recently fixed ;)
Oh and the saddest thing about it, I noticed it when they did the glyphs in the avatar/user menu, but I thought it was intentional since there were now "glyphs for easy access". sigh, seems some of the reprogramming is affecting me in a very negative way...
-
seems some of the reprogramming is affecting me in a very negative way...
Discourse syndrome.
-
That's because it was only recently fixed
D00d...they had it broken in "stable!"
I don't recall how Whisper came about, I just know it was brought up and quickly happened within a discoweek.
A customer requested it.
What's funny is how quickly the truly awful QA they have was exposed after the ban.
glyphs for easy access
-
"originally thought" implies they actually thought
about itin the first place.FTFY
-
IIII()
Well the moron who designed that clock obviously didn't want an upside down IV getting confused with an upside down VI. Because why put the numbers up the right way?
Or it could be that "balancing" thing.
-
@Onyx said:
That's, like, almost work...
This any better?
TOSHIBA P20 | N/Amm F2.5 1/8 ISO200 | 2014:09:30 23:37:21 | DVWare 1.0
As can be visually ascertained from the screenshot, it must be at least 9 months old - the greens are not blue enough and the blues are not grey enough...
Wow, that white balance is off. Also, the flash didn't fire. And it's ~12 months old (even your EXIF capture showed that).
-
What's funny is how quickly the truly awful QA they have was exposed after the ban.
Funny but predictable, as we were their de facto QA department.