Discussion of NodeBB Updates
-
@accalia said in Discussion of NodeBB Updates:
That one was not acceptable, not even after the tweak IMO.
Hey, I for one liked it. ;) But the version where every element was slightly rotated from its parent was just funny.
-
Do all the icons change every update?
-
@anotherusername yeah, I ended up needing to change
.querySelector('[component="post/favourite"]');
to
.querySelector('[component="post/bookmark"]');
-
@coldandtired said in Discussion of NodeBB Updates:
Do all the icons change every update?
UI familiarity wats that lol SHINY NEW FA-FUCKERY!
-
@Lorne-Kates said in Discussion of NodeBB Updates:
@coldandtired said in Discussion of NodeBB Updates:
Do all the icons change every update?
UI familiarity wats that lol SHINY NEW FA-FUCK
ERYTOY!FTFG
-
@accalia :fa_purple_dildo:
-
@Jaloopa said in Discussion of NodeBB Updates:
@accalia :fa_purple_dildo:
they totally should add that.
actually......
@ben_lubar, for lack of a better emoji can we have :fa_purple_dildo: as an alias for (or if you really want an actual emoji of the sex toy in question)?
-
@anotherusername said in Discussion of NodeBB Updates:
@anotherusername yeah, I ended up needing to change
.querySelector('[component="post/favourite"]');
to
.querySelector('[component="post/bookmark"]');
:infinity:
Dear system developers: Renaming something just for the fuck of it? Think it's a good idea? You're wrong. Don't do it. No, not even for that reason that you're going to try to counter-argument me with.
Is a variable misspellet? Oh well, live with it. People rely on the name of that variable.
Do you have a cooler name for an endpoint? Too bad. People have bookmarks pointing to it. People have code targeting that endpoint.
Especially when you're developing an extensible website. You created that house of cards, and other people have built support pillars and add-ons that RELY on you not fucking up the way they interface with it.
Don't like how it was originally designed? Too bad. You have dependents now. It's called "living with your bad decisions".
Need to actually change things? Then follow these rules:
- Can you keep it backwards compatible so the old way will still work? If yes, then do that. I don't care if it takes extra effort.
- It can't be backwards compatible? Chances are you are completely full of shit, and/or functionally brain damaged. Go back to #1 for a bit.
- Hey, you're here. So it actually can't be backwards compatible. I doubt that. Stop ass-sniffing your own teammates. They are just as stupid as you. Put it out to the development community as to how to keep this backwards compatible. It's their plug-ins, css and js that will break because your idiocy.
- Wow, okay, you came across the 0.0001% chance that a change you need to make actually has no backwards compatibility path. This doesn't mean you aren't an idiot. You are, because you created this scenario. You are a horrible developer for painting yourself into this corner. And by paint, I mean smearing shit all over everything. Idiot. Okay, fine, you'll have to break backwards compatibility. First, put out a public warning that this will happen within X versions-- were X is a very large number. Then after sufficient time with the warning, DEPRICATE the feature. Have your system throw warnings (NOT ERRORS) reminding developers that this change is coming. Then, finally, after a good long while of people knowing this change is coming, and being given a fair chance to fix their stuff-- and only across a major release-- then and only then do you break the API.
- If you, instead, rolled out the breaking change in a minor release and/or an unrelated update and didn't even tell anyone, go fuck a cheese-grater until you're unable to breed you fucktard.
-
Seriously, even the fucking CSS selectors!
body.page-user-favourites .posts-list .posts-list-item .topic-title {
becomes
body.page-user-bookmarks .posts-list .posts-list-item .topic-title {
-
@Lorne-Kates said in Discussion of NodeBB Updates:
If you, instead, rolled out the breaking change in a minor release and/or an unrelated update and didn't even tell anyone, go fuck a cheese-grater until you're unable to breed you fucktard.
Teeeeechnically they haven't rolled out the release yet. But, yeah, I don't understand putting out a breaking change in a minor release. Interestingly, I found this:
...but I don't see one for 1.2 (the current minor version). So, here we go:
-
@boomzilla said in Discussion of NodeBB Updates:
But, yeah, I don't understand putting out a breaking change in a minor release
I got the response that they aren't strictly following semver and basically consider a semver minor release to be a major release at this point in NodeBB's lifecycle.
-
@boomzilla said in Discussion of NodeBB Updates:
@boomzilla said in Discussion of NodeBB Updates:
But, yeah, I don't understand putting out a breaking change in a minor release
I got the response that they aren't strictly following semver and basically consider a semver minor release to be a major release at this point in NodeBB's lifecycle.
Then announce the breaking change. Several versions before you make it. And every version in between.
-
@Fox That was pretty much what I said.
-
How do you recommend this be done? If you want a changelog, you can look at the milestone on GitHub.
How about announcing it somewhere customers rather than programmers will see it?
-
@Jaloopa said in Discussion of NodeBB Updates:
How about announcing it somewhere customers rather than programmers will see it?
They literally don't understand the difference.
Also, your versioning is your fucking choice, you're not locked in here. Use semver.
Also, they worry that if they bumped the major version every time they had a breaking change, they'd be on version 32. To which I say, good! Fucking plan your releases so you do multiple breaking changes at once in a major release, or accept that your numbers will go up like chrome does and be okay with that.
-
@Lorne-Kates said in Discussion of NodeBB Updates:
@ben_lubar said in Discussion of NodeBB Updates:
Ok, I fucked up one of the "secret" changes in the update, so there will be an extra restart at 21:30 UTC."
Is this another one of those "if user==fbmac then FUKKIN_BAN!!!!()"
This community is so nice. We get secret changes, and even have secret police!
-
@Yamikuronue said in Discussion of NodeBB Updates:
Fucking plan your releases
What an advanced idea ... I must relay this around here.
-
@Luhmann it will never catch on
-
@Jaloopa said in Discussion of NodeBB Updates:
t will never catch on
maybe if I bump the release number a few times ...
-
@error said in Discussion of NodeBB Updates:
@Lorne-Kates said in Discussion of NodeBB Updates:
@ben_lubar said in Discussion of NodeBB Updates:
Ok, I fucked up one of the "secret" changes in the update, so there will be an extra restart at 21:30 UTC."
Is this another one of those "if user==fbmac then FUKKIN_BAN!!!!()"
This community is so nice. We get secret changes, and even have secret police!
Are any feds in here?
-
-
@Maciejasjmj said in Discussion of NodeBB Updates:
@aliceif said in Discussion of NodeBB Updates:
Are any feds in here?
I was thinking Stasi...
KGB?
-
@aliceif said in Discussion of NodeBB Updates:
Are any feds in here?
There are no little girls around here!
-
???
-
@Yamikuronue said in Discussion of NodeBB Updates:
@Jaloopa said in Discussion of NodeBB Updates:
How about announcing it somewhere customers rather than programmers will see it?
They literally don't understand the difference.
Also, your versioning is your fucking choice, you're not locked in here. Use semver.
Also, they worry that if they bumped the major version every time they had a breaking change, they'd be on version 32. To which I say, good! Fucking plan your releases so you do multiple breaking changes at once in a major release, or accept that your numbers will go up like chrome does and be okay with that.
QFFT
-
Anyone else notice the nodes dying a bit more often than usual?
-
@Tsaukpaetra said in Discussion of NodeBB Updates:
Anyone else notice the nodes dying a bit more often than usual?
22% of nodes have died, with some areas of nodes having upwards of 50% mortality. RIP NodeBB, there's nothing we can do to save it now.
29 February 2016 - 18 October 2016
-
Did the latest updates include a Molasses plugin?
{click thread link}
........................................................................................................................................................................ {shows thread}
-
:cooties: !!!
-
So. Much. Steal.
We're basically being throttled to 1/3 of maximum.
-
So. Much. Steal.
We're basically being throttled to 1/3 of maximum.
-
Saw this today:
-
-
@boomzilla said in Discussion of NodeBB Updates:
So. Much. Steal.
We're basically being throttled to 1/3 of maximum.
http://i.imgur.com/QBCRI6C.png
So. Much. Steal.
-
Looks like the site is back to working somewhat now?
-
@boomzilla said in Discussion of NodeBB Updates:
We're basically being throttled to 1/3 of maximum.
We've finally been idle enough to earn 5 credits then? ;)
-
@Tsaukpaetra said in Discussion of NodeBB Updates:
@boomzilla said in Discussion of NodeBB Updates:
We're basically being throttled to 1/3 of maximum.
We've finally been idle enough to earn 5 credits then? ;)
1 cpu credit is 1 cpu core running at 100% utilization for 1 minute.
We get 24 cpu credits per hour and can save up to 576 of them.
We have 2 cpu cores.
-
@ben_lubar So, what are all the new unique visitors doing? Seems like there should be twice+ as many as before. Did they get stuck reading the -thread or something?
-
@ben_lubar So we're running this horribly slow forum on half a potato?
-
@ben_lubar can we afford to upgrade to a t2.large or even an m4.large?
-
@ben_lubar said in Discussion of NodeBB Updates:
@Tsaukpaetra said in Discussion of NodeBB Updates:
@boomzilla said in Discussion of NodeBB Updates:
We're basically being throttled to 1/3 of maximum.
We've finally been idle enough to earn 5 credits then? ;)
1 cpu credit is 1 cpu core running at 100% utilization for 1 minute.
We get 24 cpu credits per hour and can save up to 576 of them.
We have 2 cpu cores.
So you're saying we need to turn the forum off for 24 hours so we can get our credits saved up again.
-
@Lorne-Kates said in Discussion of NodeBB Updates:
@boomzilla said in Discussion of NodeBB Updates:
So. Much. Steal.
We're basically being throttled to 1/3 of maximum.
http://i.imgur.com/QBCRI6C.png
So. Much. Steal.
Yep. I tried to post that 6 times.
-
@boomzilla said in Discussion of NodeBB Updates:
Yep. I tried to post that 6 times.
And it only posted twice.
Not. Enough. Steal.
-
Welcome back, after, what, 5 hours of downtime?
-
-
@aliceif said in Discussion of NodeBB Updates:
Welcome back, after, what, 5 hours of downtime?
Yeah, it's terrible. I actually had to work this morning.
-
-
@Yamikuronue Hover over the avatars, it gets "better":
Looks like it's messed up on the main avatar, because this is what it is supposed to be (on other avatars):
-
@Yamikuronue said in Discussion of NodeBB Updates:
@ben_lubar said in NodeBB Updates:
Some kind of chat menu UI update
Ew.
At least you can read your chats.
-