:wtf: How can this be so wrong??? (AKA the Discopocalypse thread)
-
@loopback0 said in How can this be so wrong??? (AKA the Discopocalypse thread):
Also $100/month? Fuck.
Don't forget that you need at least an additional server for the likes and an avatar CDN, so maybe $100 isn't that much.
-
@loopback0 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):
in the meantime the post index referred to changed.
What?
Where "post index" means the post's ordinal number in the thread.
-
@boomzilla said in How can this be so wrong??? (AKA the Discopocalypse thread):
@loopback0 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):
in the meantime the post index referred to changed.
What?
Where "post index" means the post's ordinal number in the thread.
Originally stored as a byte, because who'd ever need more for civilized discourse, then got upgraded to
BigInteger
, just to be sure.
-
@boomzilla said in How can this be so wrong??? (AKA the Discopocalypse thread):
@loopback0 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):
in the meantime the post index referred to changed.
What?
Where "post index" means the post's ordinal number in the thread.
Yes but I've got no idea what that had to do with the First Share or the pieman's post about it.
-
@loopback0 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):
@loopback0 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):
in the meantime the post index referred to changed.
What?
Where "post index" means the post's ordinal number in the thread.
Yes but I've got no idea what that had to do with the First Share or the pieman's post about it.
The thing is that the "first share" badge doesn't seem to contain a proper permalink because moving from the to the supposedly originating post can make you land on a different post (which is disorienting).
Then we began to speculate that the likely contains a link pointing to an ordinal post number in a thread, and because it is a Disconumber affected by every
thingguid surrounding it you can then land on e.g. one of Jeff's posts instead ( the horror! ).
Filed under: This was a Public Service Announcement, Captain Obvious away!
-
@JBert said in How can this be so wrong??? (AKA the Discopocalypse thread):
The thing is that the "first share" badge doesn't seem to contain a proper permalink because moving from the to the supposedly originating post can make you land on a different post (which is disorienting).
I'm not sure how we've concluded it lands on a different post.
I get the same post as @pie_flavor.
-
https://i.imgur.com/4yxcmsf.png
https://i.imgur.com/LZr1GMV.png
@discobot say why are you booing me
-
-
@Zerosquare said in How can this be so wrong??? (AKA the Discopocalypse thread):
every member in the staff is 100% active, receptive and open to suggestions and even constructive critics
open to suggestions and even constructive critics
open to suggestions and even constructive critics
open to suggestions and even constructive critics
open to suggestions and even constructive critics
open to suggestions and even constructive critics
-
-
Oh lard, the "new" Nanowrimo community site is on .
I never really participated in all the yappery there (except for some drumming up in the home region), for warthog and other reasons (one: being here), but now I'm certainly very, very unlikely to ever do so.
It's been in devlopment for more than a year, it mangled data imports, it ran like a dog, after being unable to solve that it's now moved to one and only true official hosting and it's still fucking shite, because half of the functionality is in some bootstrap site (which also doesn't quite run correctly despite its technical complexity being above intern-level only because of the traffic it has to handle) and the other half is on fucking discourse, tied like a cannon to bootstrap's bootstraps, except SSO doesn't work half the time and even the data that is already there (such as years participated - a simple number) randomly gets mangled .
They've never been particularly hesitant about rattling the can all the time. I wonder what will be the site maintenance costs this year.
-
@Applied-Mediocrity said in How can this be so wrong??? (AKA the Discopocalypse thread):
It's been in devlopment for more than a year, it mangled data imports, it ran like a dog, after being unable to solve that it's now moved to one and only true official hosting and it's still fucking shite,
Sounds like Discourse.
@Applied-Mediocrity said in How can this be so wrong??? (AKA the Discopocalypse thread):
tied like a cannon to bootstrap's bootstraps, except SSO doesn't work half the time and even the data that is already there (such as years participated - a simple number) randomly gets mangled
Definitely Discourse.
-
Is there a similar topic to make fun of forum software that isn't Discourse (and isn't NodeBB either)?
-
@Zerosquare Pretty sure there are some old Community Server threads lying around somewhere, though they'll be a letdown without all the working Signature Guys and logout bombs.
-
@mott555 said in How can this be so wrong??? (AKA the Discopocalypse thread):
Signature Guys and logout bombs.
I miss those, they were great.
I also recall one or two signature guys that broke the entire page. Those were the days!
-
@DoctorJones
We had plenty of that on Discourse as well.
-
@Luhmann Discourse pages mostly broke on their own, though (except for the fa-spin stuff). CS at least required a bit of effort on our part.
-
@mott555 said in How can this be so wrong??? (AKA the Discopocalypse thread):
logout bombs.
Good old <img src="/Logout.aspx">
-
@error I guess that's the advantage to NodeBB's WebSocket architecture. As far as I know, there is no logout page, and you can't have an img tag reference a WebSocket connection (yet).
-
@mott555 said in How can this be so wrong??? (AKA the Discopocalypse thread):
@error I guess that's the advantage to NodeBB's WebSocket architecture. As far as I know, there is no logout page, and you can't have an img tag reference a WebSocket connection (yet).
It's still an HTTP endpoint, but not the GET verb, so an img can't spoof it.
Some weird hybrid of REST and WebSockets.
-
@mott555 Looking at the logout button in dev tools, it looks like logging out is accomplished by POSTing to /logout. So nothing that could be triggered by an img src (at least assuming the back-end implementation isn't brain-dead enough to accept a GET without the _csrf token), but nothing to do with websockets from what I can tell.
-
I found a forum with some interesting posts:
The behaviour now seems to be (almost?) entirely consistent:
If you select only part of a sentence, the quote will work;
If you select an entire sentence (or include the end of a sentence), the quote will fail.in the above quote, the text has fallen outside the quote box!
Although the forum allows names with spaces - eg, "Einar Thorsrud" - the automatic lookup when you type the '@' to mention someone does not work with spaces!
It's worse than that!
The forum allows two different users to have the same name - and the @ mention feature can't cope with that!
Just found another one!
User "NYP NB-IOT" has a "display" name with a space - so that can't be @ Mentioned.
But the "hidden" name is "nyp-nb_2d00_iot" - which also cannot be @ Mentioned because it has a hyphen in !!
You'd say "sounds like Discourse", right?
But it's not. It's Telligent Community.
-
INB4: this wouldnāt have happened on discourse.
:smug:
-
@topspin It would've been deleted intentionally, to foster civilized discourse
-
Didn't Discohorse at least have (mostly) working backups?
-
@loopback0 said in How can this be so wrong??? (AKA the Discopocalypse thread):
Didn't Discohorse at least have (mostly) working backups?
This surprises me too. Apparently NodeBB's current strategy is "you're on your own LOL. Maybe stop the database and back it up manually and start it again? "
-
@Tsaukpaetra said in How can this be so wrong??? (AKA the Discopocalypse thread):
@loopback0 said in How can this be so wrong??? (AKA the Discopocalypse thread):
Didn't Discohorse at least have (mostly) working backups?
This surprises me too. Apparently NodeBB's current strategy is "you're on your own LOL. Maybe stop the database and back it up manually and start it again? "
I guess it's possible that us using PostgreSQL not MongDB might have complicated something.
-
@loopback0 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):
@loopback0 said in How can this be so wrong??? (AKA the Discopocalypse thread):
Didn't Discohorse at least have (mostly) working backups?
This surprises me too. Apparently NodeBB's current strategy is "you're on your own LOL. Maybe stop the database and back it up manually and start it again? "
I guess it's possible that us using PostgreSQL not MongDB might have complicated something.
It should have made it easier!
Half of the needed backup strategy is built into the engine and enabled by default (apparently)!
-
@Tsaukpaetra said in How can this be so wrong??? (AKA the Discopocalypse thread):
@loopback0 said in How can this be so wrong??? (AKA the Discopocalypse thread):
I guess it's possible that us using PostgreSQL not MongDB might have complicated something.
It should have made it easier!
Half of the needed backup strategy is built into the engine and enabled by default (apparently)!
I'm not saying that "we" couldn't have done something more easily, just that software expecting to be running on MongDB might not have a backup method for PostgreSQL (if it has one at all).
-
@loopback0 said in How can this be so wrong??? (AKA the Discopocalypse thread):
(if it has one at all).
@Tsaukpaetra said in How can this be so wrong??? (AKA the Discopocalypse thread):
NodeBB's current strategy is "you're on your own LOL. Maybe stop the database and back it up manually and start it again? "
But I repeat myself.
-
@HardwareGeek said in How can this be so wrong??? (AKA the Discopocalypse thread):
Um, CDCK is, what, 5 guys working out of their own homes and some unpaid community contributors? If they're paying themselves millions in salary, I think I need to learn RoR, post haste.
They are making silly valley money with something that could be done anywhere in the world. That makes them orders of magnitude more successful than me at least.
-
@sockpuppet7 said in How can this be so wrong??? (AKA the Discopocalypse thread):
They are making silly valley money with something that could be done anywhere in the world. That makes them orders of magnitude more successful than me at least.
They realised one key thing: they don't need to put all their staff in California; they can pay a pittance at Silly Valley rates and have lots of dev satisfaction. This makes them a lot more able to use their money (mostly) effectively than their peers in the SF VC feeding trough.
-
@dkf said in How can this be so wrong??? (AKA the Discopocalypse thread):
They weawised onye key thing: they don't nyeed to put aww theiw staff in Cawifownyia; they can pay a pittance at Siwwy Vawwey wates and have wots of dev satisfaction. This makes them a wot mowe abwe to use theiw monyey (mostwy) effectivewy than theiw peews in the SF VC feeding twough.
I want money...
-
@Tsaukpaetra said in How can this be so wrong??? (AKA the Discopocalypse thread):
I want money...
I don't.
But having it is better than not having it.
-
@loopback0 said in How can this be so wrong??? (AKA the Discopocalypse thread):
Didn't Discohorse at least have (mostly) working backups?
Did we even have backups for the Discourse forum?
Say what you will about Discourse, but it wasn't a bunch of tables emulating Redis. Instead, it was an actual database schema including a table with a billion rows that logged how many milliseconds each user looked at each post and also like 5 other things in the same table
-
@ben_lubar said in How can this be so wrong??? (AKA the Discopocalypse thread):
@loopback0 said in How can this be so wrong??? (AKA the Discopocalypse thread):
Didn't Discohorse at least have (mostly) working backups?
Did we even have backups for the Discourse forum?
Say what you will about Discourse, but it wasn't a bunch of tables emulating Redis. Instead, it was an actual database schema including a table with a billion rows that logged how many milliseconds each user looked at each post and also like 5 other things in the same table
I almost thought this would be saying something positive about
-
@Tsaukpaetra said in How can this be so wrong??? (AKA the Discopocalypse thread):
I want money...
I thought you wanted sex? You can usually trade one for the other, but if you've got neither, well...
-
@Zerosquare 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):
I want money...
I thought you wanted sex? You can usually trade one for the other, but if you've got neither, well...
You can also earn money by having sex.
-
@topspin said in How can this be so wrong??? (AKA the Discopocalypse thread):
You can also earn money by having sex.
you can?!
doe it pay well?
I might be in the wrong business.......
-
-
The "don't jump to your reply" option got removed because reasons.
Cue classic Jeff who can't even be consistent with his own vision of civilised Discourseā¢.
Now retaining your place in the topic after replying is an advanced feature.
I am just struggling really really really hard to think of a use case where āfast forwardingā 10+ posts you never read is the right thing ā¢ to do.
Itās designed to be ā¦ instructive ā¦ because youāre supposed to read the topic before replying. Not doing so means you are either being kind of rude and talking without fully listening, or you really know what you are doing because You Are An ExpertĀ®You didn't read the whole topic so now we skipped you to the end. YOU'RE AN EXPERT, HARRY!
Hostile, much?If we really want to be instructive isnāt the right thing to do to pop up a bootbox here?
Sunk cost fallacy means itāll be ignored every time. Humans are amazing at this.Those other toasters though? Totes useful.
[cue more silly discussion, more Sam trying to be not entirely stupid and Jeff being Jeff]
Itās clearly a per topic decision that users want to make.
Clearly.
I worry though that the actual implementation here is significantly more work than just bringing back the killed feature.
Hah. Welcome to Discourseā¢.
Prefs are poison. Drink enough of the poison over time and you die.
Fuck off is giving back people choice a bad thing.
Itās an expert mode
At any rate, thereās no rush here, if it takes 6 months for us to get to itā¦ so be it.
Sure, don't worry about the users who want the functionality back. The users who got used to doing things their way.
[ENTER A USER]
I canāt think of any scenario where I would reply to post 440 of a 500 post long thread and want to end up at the bottom, losing my place. I would suggest making Samās implementation the default and implement Jeffās as the optional āthis is what I really want, Iām an expertā choice.
That will never happen as long as Iām working on this project. Just to set your expectations in line. If thatās a problem for you, I suggest moving off Discourse at your earliest possible opportunity.HAHAHAHAHA.
My deepest apologies for participating in the discussion.
Just setting your expectations in line with reality. If you need any help migrating away from Discourse donāt hesitate to ask, I can have Jay assist you at no cost (to you). Just say the word.[More of the same, enter more users]
We have one big topic
Then thatās the problem you should address. Megatopics are not a good idea.Yeah yeah, big topics bad, Discourse good. Whatevs.
This is fundamentally an attempt to sneak in threading, and we have zero plans to ever tackle a threaded view for our forum it would be fiendishly complex and completely against our core project mission statement.
Oh he's caught the Jeff disease again.
TL;DR - use Discourse Jeff's way or not at all. Clear winner.
-
Good to know that all forums are instantly accessible and all user interaction features are instantly recognizeable as user interactable. Even if the result of the interaction cannot be easily guessed at least the fact that they can be interacted is obvious.
hah hah no.
I suppose i should be fair here..... that's a problem with ALL minimalist user interfaces. Sure a great big button in your face is less pretty.... but at least it's more discoverable....
so you know..... that applies to.... Apple, Microsoft, Google, Samsung, Hauwei, Cisco, Ubiquity, Dell, HP,.... actually.... if I keep listing companies we're going to be here a while......
-
@loopback0 said in How can this be so wrong??? (AKA the Discopocalypse thread):
I canāt think of any scenario where I would reply to post 440 of a 500 post long thread and want to end up at the bottom, losing my place. I would suggest making Samās implementation the default and implement Jeffās as the optional āthis is what I really want, Iām an expertā choice.
Thanks NodeBB for keeping that option!
Now if only I could steal enough time to implement my intra-topic position tracking and alleviate the likes-storm people know me by...
-
@loopback0 said in How can this be so wrong??? (AKA the Discopocalypse thread):
I canāt think of any scenario where I would reply to post 440 of a 500 post long thread and want to end up at the bottom, losing my place. I would suggest making Samās implementation the default and implement Jeffās as the optional āthis is what I really want, Iām an expertā choice.
That will never happen as long as Iām working on this project. Just to set your expectations in line. If thatās a problem for you, I suggest moving off Discourse at your earliest possible opportunity.HAHAHAHAHA.
I'd have thought that the approach here would be to implement a site-wide policy option for a maximum length of topic (after which the topic auto-closes) with a range of 1ā20, have no way for admins to disable it (and using a slider as the input control), and then sit back in the sure knowledge that no discussion can ever get so long as to become Uncivilized.
-
@dkf said in How can this be so wrong??? (AKA the Discopocalypse thread):
I'd have thought that the approach here would be to implement a site-wide policy option for a maximum length of topic (after which the topic auto-closes) with a range of 1ā20, have no way for admins to disable it
It's configurable and defaults to 10k but...
A few years ago we ran into a technical limitation where we send down a list of all the post IDs in the topic when you enter the topic. This starts to cause problems on the client ā particularly older smartphones with less memory and CPU power ā at around ~10,000 replies, so we created a site setting that automatically closes topics at 10,000 replies and defaulted it to on.
-
@loopback0 "ran into technical limitations ... 10,000 replies" It's nice to be remembered!
-
@dkf said in How can this be so wrong??? (AKA the Discopocalypse thread):
@loopback0 "ran into technical limitations ... 10,000 replies" It's nice to be remembered!
I like being remembered...
-
@loopback0 said in How can this be so wrong??? (AKA the Discopocalypse thread):
My deepest apologies for participating in the discussion.
Just setting your expectations in line with reality. If you need any help migrating away from Discourse donāt hesitate to ask, I can have Jay assist you at no cost (to you). Just say the word.Huh, where have I heard that one before...
-
@Tsaukpaetra said in How can this be so wrong??? (AKA the Discopocalypse thread):
the likes-storm people know me by...
Likes are worthless if they aren't rate limited anyway. A vote from that guy that never upvote, that would be real internetpointzzz.
-
@Vixen said in How can this be so wrong??? (AKA the Discopocalypse thread):
Even if the result of the interaction cannot be easily guessed at least the fact that they can be interacted is obvious.
This is a design principle known as "affordance."