Meta.d is sad
-
based on random factors
Given this badge requires discodev action... maybe it's insubordination
-
Yeah, still not sure how you not banned guys pulled that off... I would accuse you of paying Jeff to let you stay... but that would be an insult I would not try even here.
actually it's probably the phones i gifted @sam back when we were actually trying to get decent experience on winphone and they didn't have the hardware to test on.
i won't lie, i'm beginning to regret using my Amazon Rewards Points on that....
-
I think my low activity is what saved me. That and I never Burnsified.
-
So, how's bug reporting going on meta.d these days? LET'S LOOK. (You'll have to assume that all times are offset from 2015-09-29 8:33am EST. You'll also have to assume all the times are wrong, because Discourse)
Most recently reported:
http://i.imgur.com/rFKI1xl.pngImporting data? Oh you poor, unfortunate soul. /cc @ben_lubar
BUG REPORT****strong text: Click "Sort by date". Read a post. Click back. Sorting is no longer by date. SHOULD I POST ON META.DERP?!??!?!?!!!11
**BUG REPORT 2:**strong text: There is only "sort by recent activity" and not "sort by start date". AM I THINKING WRONG LIKE A PROGRAMMAAAAR?
Back to the show... okay, I was going to pick just the top 5. But there's so many fun bugs! Instead here's a curated selected of some of the bugs with activity after the DiscopocalpseWTF.
Of note, number of bugs regarding whispers: ZERO. It must be a perfect feature I WILL FUCKING BAN YOU IF YOU SAY OTHERWISE NEGATIVE ASSHOLES!
(note: I'll paraphrase as much as possible, because fuck these are fun-- and do screenshots only when beneficial)
-
#Bug: SMTP password field does not escape comment sign (hash)
First reported in December '14. Putting a # in discourse.conf causes it to crash.
Jeff's solution: Don't use # in your SMTP password you're doing it wrong! Add a comment to discourse.conf telling people not to.
Sam's solution: I'll just fix the parser.
Jeff's response: I SAID NOT TO IT WILL CAUSE CONFUSION! It isn't worth it for the very marginal benefit of having # in their password.There are THREE users reporting this bug. Jeff just expects them, and everyone else using Discourse, to change their SMTP password to something less secure-- and to update every single other SMTP-enabled application they own's configuration. DISCOURSE!
-
#Heisenbug: can’t delete user without post in rapid succession of deleting users without posts
User is trying to delete multiple spammers at once (imported from other forum). There is no way of deleting multiple users at once in Discourse. Randomly, clicking on "delete user" will cause an error.
Jeff's solution****strong text: You're doing it wrong. Why do you have so many spammers? Use Akismet!
Hey, does Onebox work for banned users?
-
Nothing like a potential security catastrophe. (Well, one of many, thanks for the link youknowwho)
#Usernames in admin URLs cause routing problems
Register a user list. Login as the administrator, go to the users list, open the details for this user. Notice that you are on admin/users/list. Reload the page. You get to the list of all users, since admin/users/list actually matches this route.
Sam's solution: we really should stop with the "fancy" url thing in admin... /admin/users/1/sam ... is a perfectly fine URL for an admin interface, plus knowing the user_id is actually handy sometimes when it comes to admin tasks.
Jeff's solution: THAT WOULD TAKE HOURS OF WORK!!!! I will just add "list" to the list of disallowed usernames.
So next upgrade, someone can register a DIFFERENT banned name, and any already registered user named "list" is fucked. Wanna bet it gets implemented wrong as .list. instead of ^list$, and everyone with list in their name gets banned in 1.5?
edit: :ninja:
-
I was going to save this one for last, but there's an even better one coming next.
Here's my Strong Text****strong text bug report, including Jeff's previous response.
http://i.imgur.com/gCi9bBe.png
So all you need to do is upgrade discourse AGAIN to get a different set of WYSIWYG errors.
-
You are pretty hard to please. You submit a bug-report. Jeff tells you: "Not a priority" then two weeks later eviltrout started working on stuff and Jeff tells you that your bug will be fixed in a future version. He even names the version itself...
Filed Under: I really don't see a problem in this specific instance
-
And now for the cream de la cream. This one-- okay, if you guys haven't read any other post of mine, this one is the one to read.
Okay, are you ready?
#Email security/obscurity for moderators is inconsistent
Well, what's that? Security and Obscurity sounds about right. But for Moderators? How bad could it be?
Bug report:
The user list hides emails (except for self, obscured), has a button to show them, and pressing that logs a "viewed email" event for each user on the page (I think - I didn't actually try this on my instance).
However the Emails/All tab shows them all straight up in clear text (obscured in the screenshot), even for emails that weren't sent.
It seems these two pages ought to use similar enforcement mechanisms or the security is for nought?Inconsistent security implementation. How shall we handle it?
Jeff* WE SHOULD REMOVE MODERATOR ACCESS TO THAT PAGE!!!!
cpradio ("senior tester") notes: "uhh, but we use that page a lot to track down spammers and advertisers who abuse the forum...."
Lorne's Prediction****strong text: Moderators will have that feature vanish in 1.5, spammers will rule the world.
Fuck all this shit. I'm done with meta.derp for the day.
Link:
-
@Lorne_Kates said:
Jeff's solution: THAT WOULD TAKE HOURS OF WORK!!!! I will just add "list" to the list of disallowed usernames.
Yeah, but c'mon, it's a pointless name. This one should be a classic. Linky:
NB: Please click on that. I added my username to the url. I think it would be funny if I can get some sharing badges while suspended.
-
@Lorne_Kates said:
Inconsistent security implementation. How shall we handle it?
I've wondered about that page, too.
-
Part of the process which includes reclassifying bugs as UX issues.
Don't forget the bugs that got memory holed
-
-
Don't forget the bugs that got memory holed
I don't remember ANY bugs that were ever memory holed, citizen.
-
You are pretty hard to please. You submit a bug-report. Jeff tells you: "Not a priority" then two weeks later eviltrout started working on stuff and Jeff tells you that your bug will be fixed in a future version. He even names the version itself...
Filed Under: I really don't see a problem in this specific instance
Not exactly. Jeff dismissed it with a "training wheels" insult. Then went on to say that a different dev is doing "a little work" (rather than a massive re-engineer) to implement a different WYSIWYG editor.
So even though it's a massive re-engineering effort, we'll drop in a completely untested and brand new WYSIWYG editor in less than the span of 1 minor release. It won't be tested. I'm not even saying it's going to fix the bug****strong text. But it will be in Ember.
(Though really, you'll only care about it being in Ember if you're a developer. End users don't understand that. WHO IS THIS FOR!!?!?!?!?!?!?!?!)
-
-
That email thing is beautiful. There's three places where a moderator (not admin) can get a user's email address:
- The user list page, where a button must be pressed and logs an audit event. This affects all users so there's no selectivity.
- The email logs page, where it's always visible directly no matter what
- The user's profile page, where a button must be pressed if a setting has enabled the button, otherwise it's impossible.
I mean I'm sort of used to some things not making total sense here, but this is something of a even for my quite Discourse-hardened mind...
-
It's a silly inconsistency, but I'm willing to see more disco-participation in that thread before condemning them on this account. I have high hopes, but you never know. Sometimes they just fix the damn bugs.
-
Oh I fully expect this to get fixed. And I think the first step in that is probably to remove access to the email logs for moderators as Jeff suggested...
-
Much as I like kibitzing here and sometimes get my blood pressure up over the workings of meta.d, I'm in the "keep Discourse" camp. I've been playing around with the nodeBB test installation, and ... well. I'm not convinced. Just as context for my bitching above.
-
You are a spammer and you are bad and you should feel bad! No, you can't know which post caused your classification, since obviously spammers should never be given the chance to fix the problem!
-
Users get confused if you give them too much information - it's the Discophilosophy.
-
@codlnghorror said:
Yes, that is as designed. Presumably you know what you just posted, since you just typed it in with your human being fingers, yes? :hand:
Jeff just can't help replying to reasonable requests with snark
@Bones said:
Thanks, if this happens again, I'll just look through my post history and see what's missing.
The fact that the user needs to do that is a massive indicator of failure. "Oh I'll just manually find out by trawling through all of my posts and attempt to spot which one is missing". That's obviously the sane Jeff-approved solution.
-
[quote=jeff]convert the editor to Ember[/quote]
Isn't the whole front end done in Ember already? Why is/was the editor different™?
-
To be fair, my understanding of Akismet is that it's only used as a pre-processor for very-low-TL users, so presumably they either don't have many posts to trawl through or they are in fact spammers.
Still a dumb "UI" decision though.
-
I think my low activity is what saved me. That and I never Burnsified.
Still got banned :(
-
I think my low activity is what saved me. That and I never Burnsified.
I strongly suspect that it's just your low activity. I happen to know of one Burnsified but unbanned account still on meta.d.
-
It's really weird; my last activity was here:
https://meta.discourse.org/t/trouble-with-vagrant/32412/1
and here:
You'd think that'd be fresh enough to get banned over...
-
@Lorne_Kates said:
Sam's solution: I'll just
fixmash up theparsertoxic hellstew of regexen.Filed under: reading between the lines...
-
@Lorne_Kates said:
Sam's solution: I'll just
jam another noodle into the toxic hellstew of regexen.fixmash up theparserFTFTFY
-
Yeah, but c'mon, it's a pointless name. This one should be a classic. Linky:
In Discourse 2.0, the only available username is
codinghorror
.Filed under: c'mon, what other usernames aren't pointless?
-
-
Hey! There I am! @anon25879736! Woohoo!
-
Hey! There I am! @anon25879736! Woohoo!
Someone should abuse @Darkmatter's XSS attack and get some of us unbanned and de-anonymized.
-
....I wonder how many posts we made total, if 130+ of them got liked by discodevs....
I had at least 20 bug topics. 1 got hidden for security reasons (they didn't want other people finding the security hole) and 1 got mega-jeffed. As a result, I was only eligible for the Tester badge. ¯\_(°°)_/¯
-
It's really weird; my last activity was here:
You'd think that'd be fresh enough to get banned over...
I think I see it though... your bugs are in the form of a question...
"Gosh, I may not understand how this is supposed to work... is this a bug?"
Which let's him find the bug.... classic leading from below.
Filed under: At least Jeff can
recognizereact to a lady propositioning him on a bus
-
Fair enough. Half of getting ahead in QA is knowing how to talk to
egotistical jerkwardsdevelopers
-
And I think the first step in that is probably to remove access to the email logs for moderators as Jeff suggested...
Ding ding ding! We have a winner!
-
Ohhh so the anon with the Senior Tester was @aliceif then?
I definitely had less than 20, and I got the top
-
Ohhh so the anon with the Senior Tester was @aliceif then?
Yeah, I never got the Senior Tester . I should have, but Jeff.
-
Patch:
-
Hmm, this guy's avatar is hatted TDWTF-style and he hasn't been banned yet?
-
How to warn this guy off without getting anon'd....
-
Way to bury the lede. New discodev!
-
They're multiplying
-
He looks like a greaser extra from Happy Days.
-
So Discourse is now (not actually) a bugtracker, forum, Q&A, and wiki. It's only a matter of time before someone tries to use it as an operating system or database platform.
-
@codinghorror said:
but that takes potentially hours of engineering effort, whereas
Plus, I don't think there's any engineering effort involved, since AFAICT, nobody there actually knows how to engineer anything.blacklisting a pointless username like "list" takes me about 30 secondsif you'd spent some engineering time up front thinking about how things might fail, you'd have saved yourself even more hours of fixing broken shit.
-
Hmm, this guy's avatar is hatted TDWTF-style and he hasn't been banned yet?
No it isn't. It's a cheap imitation. Perfect for a CoFounder of Dicksores