:wtf: How can this be so wrong??? (AKA the Discopocalypse thread)
-
@izzion said in How can this be so wrong??? (AKA the Discopocalypse thread):
UPDATE for Discourse rolls out into testing
My money is on never. Discourse testing???
Filed under: The animated ROFL emoticon we used to have was better.
-
@JBert step 4 (delete the topic without resolving the issue) appears to be missing from the list?
this is poe's law for bugtracking isn't it? got to be.
-
GitHub Issues to Discourse... why would you do that
-
@AlexMedia said in How can this be so wrong??? (AKA the Discopocalypse thread):
GitHub Issues to Discourse... why would you do that
step 4.
-
@JBert said in How can this be so wrong??? (AKA the Discopocalypse thread):
Cheers to @cpradio for making issue tracking more "social" and "community-oriented" (my words, not his)!
Eh. I'm sure someone out there has a reason for its existance, isn't and wasn't my place to figure that part out. I was simply asked to design, architect and build it. So I did :)
-
@cpradio said in How can this be so wrong??? (AKA the Discopocalypse thread):
I'm sure someone out there has a reason for its existance, isn't and wasn't my place to figure that part out. I was simply asked to design, architect and build it. So I did
I can sympathize. This is how I feel about my job 99% of the time. :D
-
@cpradio You work for Big Discourse now?
-
@AlexMedia said in How can this be so wrong??? (AKA the Discopocalypse thread):
GitHub Issues to Discourse... why would you do that
Maybe someone at GitHub got fed up with Jeff's bullshit and told him "it's time to migrate".
Filed under: no longer welcome here
-
Discourse now bans users by itself. They love to ban users, don't they?
https://meta.discourse.org/t/why-my-discourses-syster-always-block-users-itself/46122
-
@candlejack1 said in How can this be so wrong??? (AKA the Discopocalypse thread):
Discourse now bans users by itself.
I think that functionality has existed for quite some time already.
-
@aliceif said in How can this be so wrong??? (AKA the Discopocalypse thread):
functionality
It's like the opposite of an unintentional feature.
An intentional bug.
-
So, the guy set the
auto_block_first_post_regex
to a 15 kB regex and complains when Discourse blocks users based on the outcome of that regex.
-
@AlexMedia said in How can this be so wrong??? (AKA the Discopocalypse thread):
So, the guy set the auto_block_first_post_regex to a 15 kB regex and complains when Discourse blocks users based on the outcome of that regex.
.*
(negate if needed, etc.) is much shorter and would cause something similar.
-
@AlexMedia said in How can this be so wrong??? (AKA the Discopocalypse thread):
So, the guy set the
auto_block_first_post_regex
to a 15 kB regex and complains when Discourse blocks users based on the outcome of that regex.I'm really interested in what that 15kB regex is now.
http://stackoverflow.com/a/2245312/2664560 is only 6k.
-
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
15kB regex
I had a problem, so I decided to use a regex. Now I have 15k problems.
-
@HardwareGeek Still a better love story than Discourse.
-
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
@AlexMedia said in How can this be so wrong??? (AKA the Discopocalypse thread):
So, the guy set the
auto_block_first_post_regex
to a 15 kB regex and complains when Discourse blocks users based on the outcome of that regex.I'm really interested in what that 15kB regex is now.
It's the same regex twice, but once in upper case and once in lowercase.
-
@aliceif said in How can this be so wrong??? (AKA the Discopocalypse thread):
@cpradio You work for Big Discourse now?
Yes and No? I'm not "staff" more like a consultant hired to fulfill projects a customer wants or desires that the team itself does not have immediately availability for (hopefully that makes sense).
It is my understanding, there are a few of us that are doing these odd and end jobs, another is one that I know of is creating multiple themes that can be shipped out of the box.
-
@cpradio said in How can this be so wrong??? (AKA the Discopocalypse thread):
another is one that I know of is creating multiple themes that can be shipped out of the box.
I look forward to those shipping, so we can read here about how they randomly publically expose Whispers.
-
@Lorne-Kates said in How can this be so wrong??? (AKA the Discopocalypse thread):
I look forward to those shipping, so we can read here about how they randomly publically expose Whispers.
I have no idea exactly what type of themes are being built, so yes, it is possible to do that. I'd bet more on pieces of those themes constantly breaking due to rewrites of the topic listings, post output, widgetizing items, etc. But, that shouldn't come to be too much of a surprise. It took several months before someone realized the "solved" class is no longer on the post that was marked as solving the topic.
-
@cpradio said in How can this be so wrong??? (AKA the Discopocalypse thread):
odd and end jobs
ITYM @end jobs.
-
@cpradio said in How can this be so wrong??? (AKA the Discopocalypse thread):
It took several months before someone realized the "solved" class is no longer on the post that was marked as solving the topic.
< Insert "Why would you change that?!?" meme here >
Filed under: If it ain't broken, break it anyway
-
So... what's happening today in meta.fail land?
https://meta.discourse.org/t/email-sidekiq-error-no-implicit-conversion-of-nil-into-string/45137
I'm experiencing a problem where emails aren't sending. I am on the 1.5 stable release. Is there any chance that the fix for this.
To tell you the truth, "stable" is not all that stable. I suggest updating to the beta. #closedwontfix #banned #notwelcomehereanymore
-
-
The workaround is to put a space in front of the URL so it does not embed / onebox. Google Doc oneboxes are rather broken.So let me get this straight... You already know about the bug, you admit it's horribly broken, and all you have to say is "put a space in front of the url"? Not, we are currently looking at a fix, etc.
Hmmm... they could really do with a QA department...
-
Speaking of bugs that will never get fixed...
In this topic, 3 users posted: @jomaxro, @codinghorror, and @cpradio. However, on the latest view, only myself and @codinghorror's avatars are shown.
Yep this bug has been around since the dawn of Discourse
Yes it's one of those bugs that drives me crazy because I have no idea how it can happen, and I can't ever reproduce it.
-
@DoctorJones said in How can this be so wrong??? (AKA the Discopocalypse thread):
I'm experiencing a problem where emails aren't sending. I am on the 1.5 stable release. Is there any chance that the fix for this.
I would have asked in the original thread but it's closed
-
Meta.fail is like a wtf treasure trove.
So. Much. Fun.
-
Today we have another delicate truffle to enjoy from meta.fail...
https://meta.discourse.org/t/avatar-images-and-posted-images/46549
Yesterday I noticed that we are having some trouble with images in threads not showing up and avatar images as well. We are using aws with ss3.
We've started to get the same. Lot's of our users avatars at various sizes are now going grey/not found.
Can you upload some of the problem images here so we can test them?
Several posts with detailed troubleshooting information
It seems to be an issue with S3.
tumbleweed.gif
What's the best way forward here? Is S3 dropped from being supported, as in we should go back to local storage to be more like how the Discourse team hosts and we'd have less of these types of issues?
Hard to say -- did you want to purchase a hosting contract? It'd be easier for us to support you in great detail if you were a customer.
No...
It is currently a weekend, so unless you are a paid customer, you might need to wait for others to have time to get to your free support request. I apologize if this is inconvenient for you.
-
@DoctorJones that read like he's trying to be a proper, attentive, customer focussed type, but just can't help but let his dickhead nature shine through
-
@Jaloopa said in How can this be so wrong??? (AKA the Discopocalypse thread):
@DoctorJones that read like he's
trying to be a proper, attentive, customer focussed type, but just can't help but let his dickhead nature shine throughJeffFTFY ^.^
-
I like the part where the OP suggests Discourse isn't for them
-
another refugee?
-
@HardwareGeek said in How can this be so wrong??? (AKA the Discopocalypse thread):
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
15kB regex
I had a problem, so I decided to use a regex. Now I have 15k problems.
I'm pretty sure that the problems-to-regex-length equation is not linear.
@Lorne-Kates said in How can this be so wrong??? (AKA the Discopocalypse thread):
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
I'm really interested in what that 15kB regex is now.
It's the same regex twice, but once in upper case and once in lowercase.
Filed under: Math is hard
-
@pydsigner the extra 3k is pure problems
-
@Jaloopa said in How can this be so wrong??? (AKA the Discopocalypse thread):
@pydsigner the extra 3k is pure problems
It isn't 50/50 because Upper case letters are bigger, so they take up more space.
-
Discourse has a reverse-@Tsaukpaetra bug! Notifications for all the (one) admins!!!
ok, so that was a stretch. whatever. discourse bug, funny, ha ha
-
@candlejack1 said in How can this be so wrong??? (AKA the Discopocalypse thread):
Discourse now bans users by itself. They love to ban users, don't they?
Yo, dawg, I heard you like bans, so I put one in your forum!
-
@izzion said in How can this be so wrong??? (AKA the Discopocalypse thread):
Notifications for all the (one) admins!!!
Probably an issue with the notification CDN.
-
@izzion said in How can this be so wrong??? (AKA the Discopocalypse thread):
@Tsaukpaetra bug
What was/is that?
-
Today in fail land...
: Our forum is encountering some UX problems with Discourse polls. Our users aren't finding them intuitive.
: Where is your evidence of these problems? I have literally never heard any of these complaints before from our 400+ hosted customers, or here on meta. I appreciate the effort, but "because you said so" is a weird way to propose changes.
<snarky-comment>Yeah, the only valid way to propose changes is "becauseyouJeff said so"</snarky-comment>
: I apologise but this is all the evidence I can offer. Keep in mind that not having heard of these from 400+ hosted customers does not prove the inexistence of the problems either. Just for the record: This is not about me.I'm surprised this topic hasn't been memory holed yet...
-
@izzion said in How can this be so wrong??? (AKA the Discopocalypse thread):
something seems buggy
you_don't_say
-
Here's another gem...
: Couldn't we just switch to a decent WYSIWYG editor? There are some pretty decent ones out there...
: That would be extremely difficult, as we couldn't be arsed to layer our code properly. We could do it for around $100'000 - $120'000 if you fancy stumping up the cash.Seriously guys, that's some very impressive work.
It's usually quite easy to just drop a new editor into a system. It takes some serious hard work and dedication to manage to tightly couple to your editor as much as you guys have. Bravo!
-
@DoctorJones said in How can this be so wrong??? (AKA the Discopocalypse thread):
: We could do it for around $100'000 - $120'000
-
this is like saying I prefer MySQL, can't you guys just switch your database from Postgres to MySQL?
Maybe it is, but it should be like saying "I prefer a different presentation layer. Can you switch the view in your MVC to look different?"
-
: We've disabled "uncategorized" posts on our installation, but it still allows admins to create them. We had a situation where an admin made a post that nobody saw.
: This is by design and perfectly normal.
: This is an embarrassment.
: I also disagree with the default behaviour on this. Could we please have an option like "allow admins to post to uncategorised"?
: That sounds like too much work... /memory-hole /ban-user /not-welcome-any-moreI wish I was kidding about the memory hole part. I didn't take a screencap for posterity because it seemed like such a reasonable post.
So if you run this configuration, nobody can see admin posts by default. It doesn't even warn the admin that they haven't selected a category, it just allows them to post into a memory hole. That's some clever shit right there.
How anyone could defend a retarded design like this is beyond me.
Update:
The post has now re-appeared! Screenshot for posterity just incase:
It's likely that the post disappeared due to a Discourse bug rather than being memory-holed. I can't imagine Jeff un-memory-holing something.
-
PS: The description of the "Read guidelines" badge ends with "Be nice!" You just closed a topic in which I had replied without leaving a comment about why you close it. Just to let you know: That did not feel nice.
Jeez...the guy even has PRs for his fixes!
-
@DoctorJones said in How can this be so wrong??? (AKA the Discopocalypse thread):
So if you run this configuration, nobody can see admin posts by default. It doesn't even warn the admin that they haven't selected a category, it just allows them to post into a memory hole. That's some clever shit right there.
I remember having this problem multiple times.
-
@Zecc I'm pretty sure it was @Tsaukpaetra who was begging to get inundated with mentions because he never really has any to see in his menu. CBA to find the thread...
-
Alas NodeBBgun's notification menu is not appropriate for that, or I'd send @Tsaukpaetra a nyantification cat.