Discourse DMZ
-
Since we are on the topic of filing bugs in this Topic:
Something that bothers me and I can't remember if it has been adressed is the fact that scrolling breaks the "Quote"-Button (and the highlighted text)
That is really annoying since the Composer for a reply takes half my screen anyway. So to quote something multiline not only do I have to start out perfectly scrolled (since the composer is ON TOP of the Stream of content so some content I might have wanted to reply to seperately goes invisible) and even then sometimes I need to quote one half, quote the other half and merge them later on.Especially annoying on mobile where the composer takes 90% of my screen.
Filed Under: I am really curious... has that been reported somewhere? It seems like an obvious bug! | Yes, I can prevent this by using my keyboard-arrows to scroll.. I just found that out by playing around in this topic!
There is also something I'd really like to know from a developer on this project (like you).
There is one thing I completely don't get about the developement of Discourse and that is that you guys remove stuff instead of making things optional.
This always really confuses me when there are topics on meta that say "Should we remove further content from the Topic-list". Sometimes they even want to add things to it.
Then Jeff comes forth, says "No, this is not what I need" and it is more or less dismissed. And here is what I don't understand:
You guys are delivering a basic-package. You deliver the software, not the community or the way a comunity wants to interact with a software.
Why isn't everything easily configurable? I mean, yeah, I get you guys hate PHPBB-style designs that are overloaded with stuff. I really do. But why not leave the choice to the administrator you sell your product to?Real example: Heatmaps
I don't use them. pretty sure @matches doesn't use them, @arantor I have never seen liking them in Discourse either. Not sure about what @PJH thinks about them (because I am too lazy to search right now). @blakeyrat ... I can never tell what he likes. But it's part of Discourse so he probably hates it with a passion.
The heatmaps weren't there when we got the software.
At some point they were there, replaced some other column and we had to live with them. But the code for the other column is there! You guy wrote it. Maybe you removed it to keep the code clean. I don't know. But the thing is: instead of giving every site-admin the option to configure his local Discourse-instance the way he wants, you guys removed potential content.
Yeah, somebody could probably write a plugin to change that. But IMO you should not rely on other people writing plugins to undermine what you guys have been working for.Why do you guys do that? What is the philosophy. I am honestly really interested in an answer (not even trying to bash it, or anything).
Or is it configurable and I am just too stupid to realize?
Filed Under: Also my favorite bug: ;P gets converted, :D doesnt. You should know that one, since I sent it to you via PM (if you read that one)
Addendum: Sorry for the wall of text. I got carried away.
TL;DR: Scrolling breaks quoting and why is Discourse not 100% easily configurable.
Addendum2: @eviltrout, obviously :D
-
At some point they were there, replaced some other column and we had to live with them. But the code for the other column is there!
Worse with this one is that there was a comment about removing the unwanted column with CSS for the one person who posted saying they didn't like it, then suddenly within a day it was gone completely from all (updated) Discourse instances with no way of making it return.
-
Urban legend. I just posted the same thing as my ninja one post topic, minus the word 'shit' because I knew it would get deleted either way and I CBA to spend more time reporting bugs that are just going to be deleted.
-
It's just a copy of my ninja post here in one post, it would have been fine unless you opened my profile.
This is a key post in unraveling the facts!
though it's only the OP.
-
Might I recommend a maximum embedded object limit?
-
Real example: Heatmaps
I'm sure a bunch of other people, myself included, complained about them . I saw them as completely pointless and have custom CSS for local use to completely neuter them.
-
Having to hack your columns out via CSS is also not what I would call "configurable". (Not saying you implied that. I am just using this chance to stress this out).
There is an admin-system. And from what I have seen it doesn't even look all that bad (but @PJH should be the judge of that here, since I mostly only saw it from his Screenshots). They should improve that at some point. Make more stuff changeable.I am to this date not sure why TrustLevels are apparently to hard to make configurable. From what I understand it's simple string-replacement. But maybe it is. Maybe I am asking for impossible stuff. It's just that it seems like such a basic need for a software that is supposed to work as a foundation...
Filed Under: So far I mentioned 4 people this evening. Let's see if I can collect a set!
-
I know there's gold posts in here but do we have to talk about every single thing in one place?
Feel free to reply into a new topic. Just don't move stuff that's already here. Yes, we kind of get together and talk talk talk. It's what we do.
Fair enough, but if we're gonna say Jeff unfairly deleted his post in this particular case it seems pretty fair to me.
Could you or @Matches or someone with access to that post it somewhere here? Or was it just something like this:
http://what.thedailywtf.com/t/ninja-mini-nuke/2973/1
We just didn't want random meta users to crash
Seems like a better approach would have been to edit it down, leaving a description and acknowledging the bug.
Passive aggressive moderation is a barrier to civilized bug reporting.
-
Thanks for your post. Skimming them, a few are definitely fixed already. It's a weird way to catalog them for me so next week I'll triage and make sure they all have topics on meta that aren't closed so we can get them fixed. It'll take me some time and I've got a busy weekend, I just want to see for myself what was missed and how severe or is.
-
It's a weird way to catalog them for me so next week I'll triage and make sure they all have topics on meta that aren't closed so we can get them fixed.
Thank you.
-
The people I mentioned were just a representative selection from my head. I hereby apologize for not mentioning you in that post. Though I assumed you changed your local CSS anyway.
Filed Under: See that as a compliment if you will ;P
-
The 32k post doesn't crash browsers.
The profile, on the other hand.
-
The profile, on the other hand.
Your current profile? Is this the scrolling down the profile thing? I tried that for a few minutes, and it just got slow while the js was building the DOM or whatever. I posted some memory stats. What sort of browsers are you guys using? Are they 32-bits or something?
-
Seems like a better approach would have been to edit it down, leaving a description and acknowledging the bug.
Passive aggressive moderation is a barrier to civilized bug reporting.
I'd hardly call that bug report civilized. It had bowser in it and was designed to overload the memory of any client that opened it.
-
It reportedly crashes firefox and IE browsers. Chrome (even mobile) handles it fine.,
-
Bowser is an innocent bystandard from my embedded .hta. It's quite old (I copy/pasted from here directly)
-
It gets slower and slower and then stops working.
My Profile All-page can be scrolled to Jun13th if you get past that, your browser is better than:Firefox, Opera, Firefox Mobile (beta)
@riking mentioned it might be a bug using a custom groupeach() instead of each(), I think.
Filed Under: I tested with those browsers
Edit: Apparently I confuse Opera and Chrome constantly... but aren't they almost the same anyway?
-
It reportedly crashes firefox and IE browsers. Chrome (even mobile) handles it fine.,
Ah, that explains:
I'd hardly call that bug report civilized. It had bowser in it and was designed to overload the memory of any client that opened it.
Yeah, but like we've said, the passive aggressiveness didn't start there. I've had several of my posts deleted without warning and only noticed later. These were not trolling posts by any means (maybe one early post was).
-
Different kuro. Open my profile, the scrolling for the images doesn't crash chrome due to proper caching,
-
Having to hack your columns out via CSS is also not what I would call "configurable".
I agree, but it does at least leave the choice with the instance admin or users.Thanks for your post. Skimming them, a few are definitely fixed already. It's a weird way to catalog them for me so next week I'll triage and make sure they all have topics on meta that aren't closed so we can get them fixed. It'll take me some time and I've got a busy weekend, I just want to see for myself what was missed and how severe or is.
Thanks.
-
Why isn't everything easily configurable? I mean, yeah, I get you guys hate PHPBB-style designs that are overloaded with stuff. I really do. But why not leave the choice to the administrator you sell your product to?
Good question! Regarding the columns, when Jeff asked me to remove the likes column I pushed back a bit and we agreed to only remove it visually, while keeping the same backend API. If you use a plugin you can bring it back for your site.
During the activity column / heat map debacle Sam and I discussed the ultimate solution of just letting users pick their columns. When I removed the columns I purposely wrapped activity's logic in a web component so we could reuse it toward this goal.
So long term, we are definitely gonna let you choose whatever columns you want. Short term though, we'd had a LOT of feedback about the list being too cluttered and we wanted to alleviate a bit of that for V1.
-
I agree, but it does at least leave the choice with the instance admin or users.
While that is true it still confuses me. Because that is probably how I would build my own forum. For private use only. Just type it away and then hide things that are not needed anymore. That's why I called it hack.
Filed Under: Oh, Eviltrout answered, let's read ;P
-
My Profile All-page can be scrolled to Jun13th if you get past that, your browser is better than:
Firefox, Opera, Firefox Mobile (beta)
I made it to Jun 12th (Chrome x64). It's only a day further but you joined then so can't exactly go further.
-
My Profile All-page can be scrolled to Jun13th if you get past that, your browser is better than:
Firefox, Opera, Firefox Mobile (beta)
Yes, apparently it is. 64-bit Chrome 37 on linux. I got back to June 12th and this post:
http://what.thedailywtf.com/t/how-do-you-know-if-your-forum-software-is-trwtf/827/17
Pretty sure I went farther on my profile. RAM maxed out under 500MB scrolling through yours. You only have 1236 things listed as "All". Mine has over 47K. Bet you can't get past yesterday (maybe not even to it). I'm not past yesterday yet, and the tab (freshly opened for profile spelunking) is up to 690MB.
Still not past "1 day ago" and up to 800MB...loading new entries is pegging a core for about 30 seconds.
-
During the activity column / heat map debacle Sam and I discussed the ultimate solution of just letting users pick their columns. When I removed the columns I purposely wrapped activity's logic in a web component so we could reuse it toward this goal.
Yes, removing columns completely definitely seemed like a Jeff thing.
-
I'm fully aware that you can scroll most browsers to death on the user streams. It sucks and I'm unhappy with it. I think we're going to have to take another approach.
I wouldn't mind some kind of search there, maybe with date ranges in the query params. Then a user could get at most x results back, but also have better control for finding stuff.. Something like that
-
So long term, we are definitely gonna let you choose whatever columns you want. Short term though, we'd had a LOT of feedback about the list being too cluttered and we wanted to alleviate a bit of that for V1.
Okay, I understand that. I don't even want to argue that you guys obviously did a lot of thinking in stuff like that. And I guess it's good you guys didn't remove the column for good.
Maybe you (the Discourseteam) and me just have a different idea of what I Forum-platform is. Or what we consider 1.0 (for me that would have been the 1.0 breaker, I think)
Tough since it is in planning I am not going to harp on it. As I said, it was more me being curious than anything else.
I got back to June 12th
I made it to Jun 12th
either it has already been fixed to some degree, or my laptop and tablet suck really badly. I'll try it once more in a second (don't want to lose this post and I don't trust the drafts ;P)
Mine has over 47K.
Are you and @Arantor going for some kind of show-off?
-
I think we're going to have to take another approach.
Pages would solve the problem.
-
Yes, removing columns completely definitely seemed like a Jeff thing.
Right, but after over a year of constant complaints that the homepage was too busy. The UX of the topic list is still a a major issue.
-
either it has already been fixed to some degree, or my laptop and tablet suck really badly.
My machine is pretty beefy, especially compared to those. Quad core i7, 24G RAM.
-
FunFact: right now I got to August 12..... but I have 10 Discourse-tabs open... so I think I can be forgiven!
Filed Under: Maybe!
-
I wouldn't be against pages on the user stream, I just think a search would be more useful. I have many thousands of stream items, page 1233 versus 1244 is not very useful.
Being able to say, what post did I make in January with the word dog seems way better to me.
-
Right, but after over a year of constant complaints that the homepage was too busy. The UX of the topic list is still a a major issue.
I can understand that, but ripping stuff out in the immediate lead up to v1 seemed very inappropriate (back to feature freezes). Especially considering that many people are interested in different columns, obviously the long term decision to allow configuration is good. It just seemed odd that since there was already a configurable way to hide that stuff, the defaults didn't just change.
This would have spared us soooo much grief.
-
I just think a search would be more useful.
That's true. Nevertheless, leaving a feature in that's effectively a booby-trap is just asking for trouble. Either do the infini-scroll thing for reals or don't do it at all.
-
either it has already been fixed to some degree, or my laptop and tablet suck really badly
Both, maybe
When I last tried I made it back to when I first posted and I have more in the "All" section. Tab nearly hit 600MB IIRC though.but I have 10 Discourse-tabs open... so I think I can be forgiven!
Filed Under: Maybe!
Maybe indeed, considering how much a normal Discourse tab uses.
-
I think we could have handled it better. A lot of the debate should have been more clear it was about the default, and I'm not sure we ever communicated that the json API still had the old stuff. We could have written up a few words on how to put the like column back in no plugin, etc.
I know one thing I'm guilty a of is worrying more about issues that are technologically harder to revert; something like a column is so easy to change that I didn't concern myself much with the discussions around it, because I thought, hey, worst case I just put it back.
But sometimes little things in the code are huge to users and are worth more of my attention.
-
When I last tried I made it back to when I first posted and I have more in the "All" section. Tab nearly hit 600MB IIRC though.
I did identify a jQuery event leak plus a lot of extra processing on that page. It was fixed shortly before v1 so it should be harder to crash. It wasn't a proper fix though, if you load enough data the tab will bail at some point.
-
So what happened to the whole cloaking idea? You guys remove shit from the dom everywhere else.
-
Still waiting for instructions on how to use VBulletin to view these posts.
-
Nah, vBulletin sucks. Open source does it better than the last version of vB did - they pushed it out just before (like, 24 hours before) they settled the lawsuit with XenForo and it was their big 5.0 version missing a shit-ton of features.
-
Cloaking would probably help but there is a serious flaw in usage when there is no location saved via replaceState like in topics. It would buy us more memory but really it should be fixed properly.
A topic is a lot better than a user stream in discourse in many ways: it stores your location, tracks what you've read and even has a search feature and filtering.
User streams just dump in the dom forever.
-
Question: is a stream of 'everything that has ever happened to a user' actually useful? I get the streams of other stuff but 'everything' seems a touch unhelpful to have in the first place.
-
It sounds really badass if you picture navigating it in a flying DeLorean...
-
How about streaming in a large object, and doing a metered load with built in delays? That would prevent the browsers from crashing due to being 'unresponsive' when it's doing legitimate work.
The problem is 100% how you're fetching data. What are your database indexes, and your sql query to pull the all post data?
-
Why would I use a car to navigate the time streams? *bzzzzzzzzzzzzz* Sonic screwdriver says hello, and goodbye.
*groan* *groan*
-
As sexy as Sexy is, there's something about a revving motor that gets my motor going ;)
-
Yeah I think that's the real solution. Show a bunch of recent activity, let theM search beyond that.
-
Oh, in that case.
-
As sexy as Sexy is, there's something about a revving motor that gets my motor going ;)
Fortunately in my case, others would disagree.
-
Works for me. Going in search of problems will guarantee to find you some, especially with the people here who will break things because they can.
