:wtf: How can this be so wrong??? (AKA the Discopocalypse thread)
-
@Lorne-Kates Who is @alicef?
-
@aliceif said in How can this be so wrong??? (AKA the Discopocalypse thread):
@Lorne-Kates Who is @alicef?
It's you without I in you.
-
@bb36e said in How can this be so wrong??? (AKA the Discopocalypse thread):
@izzion said in How can this be so wrong??? (AKA the Discopocalypse thread):
/t/1000
I'd argue that discourse really shouldn't be used when discussing how things /should/ work :p
One thing I miss about discourse is the ability to read/goto replies from the post they reply to. Discourse did get a few things right.
-
@Dreikin said in How can this be so wrong??? (AKA the Discopocalypse thread):
One thing I miss about discourse is the ability to read/goto replies from the post they reply to. Discourse did get a few things right.
Yeah, it was also handy to be able to quickly see if a certain item in a post had been replied to yet.
-
@Dreikin I also miss being able to easily view the context of a quote.
-
@PleegWat
I wonder if that feature is something NodeBB has the underpinnings for. I was originally going to say "we could maybe write a plugin and submit it as a feature request back upstream" but then I realized I, personally, have no motivation to try to help with coding of such a thing. So... "could y'all ...?" :P
-
@izzion Beats me, all I know is nodebb is based on a non-relational database.
@TDWTF-NodeBB-Development, is a discourse-style "Replies to this post" popout feasible in nodebb?
-
@izzion said in How can this be so wrong??? (AKA the Discopocalypse thread):
I wonder if that feature is something NodeBB has the underpinnings for.
My 30 seconds of thought on this:
We could make a plugin so that when you replied to a post, we store the post id of the reply as part of the replied to post's data. Then the plugin could render some sort of expandable thing to show you what was there.
Obviously, this wouldn't do anything for replies made before the plugin.
It's certainly possible to scan the rest of the posts in the thread for replies to the post when it's being rendered. But it sounds prohibitive from a performance point of view. Of course, we could have some sort of upgrade process that goes through all the posts and updates that information.
-
@boomzilla That would be the way to do it.
-
@boomzilla why make it a plugin? Make it part of core and use https://github.com/NodeBB/NodeBB/blob/master/src/upgrade.js to build the initial index.
-
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
why make it a plugin?
If the NodeBB devs would allow it in, I agree.
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
Yes, if it's in core then that's how you'd do it.
-
@boomzilla said in How can this be so wrong??? (AKA the Discopocalypse thread):
If the NodeBB devs would allow it in, I agree.
-
@boomzilla said in How can this be so wrong??? (AKA the Discopocalypse thread):
We could make a plugin so that when you replied to a post, we store the post id of the reply as part of the replied to post's data.
I believe this part is already being done, but only under certain conditions, and only one post (sorry multi-quoters).
-
@Tsaukpaetra said in How can this be so wrong??? (AKA the Discopocalypse thread):
@boomzilla said in How can this be so wrong??? (AKA the Discopocalypse thread):
We could make a plugin so that when you replied to a post, we store the post id of the reply as part of the replied to post's data.
I believe this part is already being done, but only under certain conditions, and only one post (sorry multi-quoters).
It goes reply → parent, but I don't think there's a reverse index.
-
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
@Tsaukpaetra said in How can this be so wrong??? (AKA the Discopocalypse thread):
@boomzilla said in How can this be so wrong??? (AKA the Discopocalypse thread):
We could make a plugin so that when you replied to a post, we store the post id of the reply as part of the replied to post's data.
I believe this part is already being done, but only under certain conditions, and only one post (sorry multi-quoters).
It goes reply → parent, but I don't think there's a reverse index.
Oh, right. So you'd have to make an index for the in-reply-to...
I'll consider that a technical
-
Moar cakeday perfect functionality!
-
@izzion user cards being broken sure seems like a common occurrence, even now.
-
@izzion said in How can this be so wrong??? (AKA the Discopocalypse thread):
Moar cakeday perfect functionality!
/whisper @end Don't tell anyone but I think Cakeday is broken and was a bad idea implemented poorly
-
@izzion said in How can this be so wrong??? (AKA the Discopocalypse thread):
@PleegWat
I wonder if that feature is something NodeBB has the underpinnings for.From what I've been told, no.
Request:
Upstreamed like a Candiru:
This is a neat idea... we currently store the relationship one way (posts record their toPid value), but not the other way around...
In other words, because they don't use a sane database or a sane data model.
:|
-
@Lorne-Kates said in How can this be so wrong??? (AKA the Discopocalypse thread):
In other words, because they don't use a sane database or a sane data model.
Do they actually have a good reason for using Mongo, or is it purely based on “webscale is cool beans”?
-
@dkf said in How can this be so wrong??? (AKA the Discopocalypse thread):
@Lorne-Kates said in How can this be so wrong??? (AKA the Discopocalypse thread):
In other words, because they don't use a sane database or a sane data model.
Do they actually have a good reason for using Mongo, or is it purely based on “webscale is cool beans”?
Since there is literally no "good reason" for using Mongo, Imma going to just go ahead and say "no".
-
@dkf TDWTF criticize me for using JavaScript, then go to some shit that uses mongo. You guys are no wiser than the authors of the snippets you mock in your front page.
-
@Lorne-Kates said in How can this be so wrong??? (AKA the Discopocalypse thread):
there is literally no "good reason" for using Mongo
Well, I happen to agree with you in my own prejudiced way, but I was wondering if someone had a different perspective. Maybe someone has found a reason to have a massively denormalised non-reliable shit-pile for data storage that doesn't make me think they've gone insane…
-
@dkf said in How can this be so wrong??? (AKA the Discopocalypse thread):
@Lorne-Kates said in How can this be so wrong??? (AKA the Discopocalypse thread):
there is literally no "good reason" for using Mongo
Well, I happen to agree with you in my own prejudiced way, but I was wondering if someone had a different perspective. Maybe someone has found a reason to have a massively denormalised non-reliable shit-pile for data storage that doesn't make me think they've gone insane…
http://i.imgur.com/XuMj5SB.png
Note that that first article contains a bunch of bullshit and no facts, and boils down to "well, if you don't care about your data much and it isn't important, sure, go ahead."
Also one of the criteria for choosing MongoloidDB is, and I quote, "You Don't have a DBA"
-
@dkf said in How can this be so wrong??? (AKA the Discopocalypse thread):
Do they actually have a good reason for using Mongo, or is it purely based on “webscale is cool beans”?
IIRC it was initially on Redis, so everything is key / value. So, the "good" reason is that Mongo makes more sense than Redis and can be used basically the same way, as a key / value store.
-
@boomzilla said in How can this be so wrong??? (AKA the Discopocalypse thread):
Mongo makes more sense than Redis
But nobody thought “maybe we have some idea what our data model really is now”? :(
-
@izzion said in How can this be so wrong??? (AKA the Discopocalypse thread):
doesn't mean that IP banning bad actors is a bad method
Permanently banning IP is, because they're frequently temporary and you'll end banning legit users.
-
@dkf there are very rare circumstances where nosql make sense, If you're Twitter or Facebook, but then you use a decent nosql db like Cassandra.
Using mongodb is giving proof of your incompetence.
-
@groo what are the differences between Mongo and Cassandra?
-
@Jaloopa Cassandra performance was a lot better when I read about it, and mongo didn't even increase it linearly when you add more servers. If you can justify using a nosql database you need a decent one, don't you?
Mongo is mostly used as a fad by startups, people that don't wanna a schema and people that want everything JavaScript.
That means I may have exaggerated a little, not using a schema and using JavaScript are valid reasons in a toy project.
Cassandra is harder to use too.
-
Wait, you can't do something like this?
SELECT p.postid, COUNT(r.postid) FROM posts p LEFT JOIN posts r ON p.postid = r.replyto
-
@AlexMedia said in How can this be so wrong??? (AKA the Discopocalypse thread):
Wait, you can't do something like this?
SQL in a NoSQL DB?
-
-
Who in their right mind picks a NoSQL database for forums anyway? There's nothing NoSQL about it...
-
@AlexMedia YMBNH
-
@AlexMedia or nodejs as a programming language
-
@boomzilla I mean, not even the DiscoDevs made the choice to go with NoSQL. :D
-
@AlexMedia said in How can this be so wrong??? (AKA the Discopocalypse thread):
Who in their right mind picks a NoSQL database for forums anyway? There's nothing NoSQL about it...
What makes you think anyone involved was in their right mind?
-
@AlexMedia said in How can this be so wrong??? (AKA the Discopocalypse thread):
@boomzilla I mean, not even the DiscoDevs made the choice to go with NoSQL. :D
Yeah, they had to roll their own disfunction. But damned if they aren't naturals!
-
@AlexMedia said in How can this be so wrong??? (AKA the Discopocalypse thread):
@boomzilla I mean, not even the DiscoDevs made the choice to go with NoSQL. :D
You see, we were so burned out by the ugliness that is Discourse that we even departed from their one sensical design decision and refuse to touch relational DBs anymore. Like that Seinfeld episode where having a relationship with George made that woman become a lesbian instead.
-
Is there an existing plugin or a built-in way to add an "I read it" button to posts? Our team is in a dire need to have the ability to publicly mark posts as read, without sharing semantics with "liking" something.
For what purpose? What is the goal? What would this achieve? Discourse knows exactly what you have read and even how long it was visible on your screen...
When we do some kind of announcement on our forum and we want to make sure that all team members read it, we can either:- ask team members to "like" the post
- ask the team members to leave an answers saying "I read it"
Neither makes sense.
I disagree. Liking a post does mean you've read it, so the semantics are clear. In nearly four years of using Discourse, I have categeorically never pressed the like button on a post I have not read.
Yeah, but liking a post also means that you like it. So it enables a scenario when someone presses the like button on a post they don't like (just to show that they do acknowledge it's content). This is the semantic discrepancy that we're trying to solve here.
I don't get this big descrepancy.It's like you work for the company but you don't approve of the things the company is doing? Why would you work there, again?
Mildly amusing, but then I also found this:
Which sets strange limits on things you can do. Especially weird on a bug-tracker. "I can only accept 50 new bug/feature requests per day".
-
@Mikael_Svahnberg said in How can this be so wrong??? (AKA the Discopocalypse thread):
"I can only accept 50 new bug/feature requests per day".
I think you mean: You can only mark 50 announcements as read per day.
-
@Luhmann said in How can this be so wrong??? (AKA the Discopocalypse thread):
@Mikael_Svahnberg said in How can this be so wrong??? (AKA the Discopocalypse thread):
"I can only accept 50 new bug/feature requests per day".
I think you mean: You can only mark 50
announcementsreplies as read per day.FTFY
-
-
https://meta.discourse.org/t/being-a-heretic-aka-going-back-to-pagination/52070
Maybe I'm old fashioned or stuck in my ways or whatever...but I prefer the ways forums were designed for reading in the past and I find it easier to keep my bearings, find old and reference material, share specific posts within a thread, and so on in this older, more structured, paged atmosphere. Hoping for some friendly discussion.
: Pagination isn't coming. If you are waiting for that, look elsewhere.
: Over time I can see our timeline getting richer and smarter. Here is a list of things I'd like to do to the timeline, but we'll probably never get time to implement...
-
It would be interesting if you mentioned at least one thing about reading experience that can be done the old-fashioned way but cannot be done the new page-less way in Discourse.
Possible > Easy
-
@end said in How can this be so wrong??? (AKA the Discopocalypse thread):
if you mentioned at least one thing about reading experience that can be done the old-fashioned way but cannot be done the new page-less way in Discourse.
A button to retry fetching the next page when it gets stuck.
-
@Yamikuronue
It's not Discourse's bug that you're browsing with sub-Korean Internet. You should file a ticket with your ISP.
-
@izzion said in How can this be so wrong??? (AKA the Discopocalypse thread):
@Yamikuronue
It's not Discourse's bug that you're browsing with sub-Korean InternetiPhone mobile. You should file a ticket with your ISP.
-
@DoctorJones With all the discussion of Discourse alternatives, I expect this thread to be jeffed into oblivion.