General MSB announcements
-
The problem is that nodeBB, to my knowledge, isn't portable. At all. We've been up for a long time, and we may lose a lot of information if we try to 'port over, if that's even possible.
As for my problem, I need someone who knows nodeBB, period, for good or ill.
-
I mean - would it REALLY be a bad thing if some parts of the forum lose all their data and we never recover them?
-
@silverfox I'm still put out that WORA is gone and not even as archives.
There was some true gold in there.
-
@silverfox said in General MSB announcements:
I mean - would it REALLY be a bad thing if some parts of the forum lose all their data and we never recover them?
Yes, since we'd be losing continuity. And it wouldn't be selective.
-
Yeah, there were quite a few threads in the MU development sections that had some great ideas.
-
I upgraded us to the latest and greatest NodeBB v1.16.2 last night. There were... some issues. I think they have been resolved, but please let me and Gany know if anything new pops up.
-
@arkandel said in General MSB announcements:
I upgraded nodeBB to v1.18.5.
Please report any issues to your local cat-authorities.
THERE'S A NEW LINE ON THE LEFT AND I DON'T LIKE NEW THINGS RAR.
(Kidding obvi)
-
@derp I had that exact same reflex. HOW DARE CHANGE HAPPEN!
-
I don't like it either. CHANGE IS HARD.
-
This post is deleted! -
-
@silverfox said in General MSB announcements:
I don't like it either. CHANGE IS HARD.
I don't mind change, generally, but that line is absurdly distracting for some reason.
-
@faraday said in General MSB announcements:
@silverfox said in General MSB announcements:
I don't like it either. CHANGE IS HARD.
I don't mind change, generally, but that line is absurdly distracting for some reason.
Also not a fan. At a quick prod, if people use something like Stylebot they should be able to remove it with:
.topic .posts.timeline .timeline-event, .topic .posts.timeline>[component=post] { border-left: 0; } .topic .posts.timeline [component=post]:last-child:after { width: 0; }
If they want a little clearer division between posts they might also add something like
.topic .posts.timeline .timeline-event:not(:first-child), .topic .posts.timeline>[component=post]:not(:first-child) { border-top: 1px solid #375a7f; }
...might want a different colour if they use a different skin than I do, though.
-
I like the line. It brings structure. Boundaries.
Respect the line.
-
@ninjakitten said in General MSB announcements:
@faraday said in General MSB announcements:
@silverfox said in General MSB announcements:
I don't like it either. CHANGE IS HARD.
I don't mind change, generally, but that line is absurdly distracting for some reason.
Also not a fan. At a quick prod, if people use something like Stylebot they should be able to remove it with:
.topic .posts.timeline .timeline-event, .topic .posts.timeline>[component=post] { border-left: 0; } .topic .posts.timeline [component=post]:last-child:after { width: 0; }
If they want a little clearer division between posts they might also add something like
.topic .posts.timeline .timeline-event:not(:first-child), .topic .posts.timeline>[component=post]:not(:first-child) { border-top: 1px solid #375a7f; }
...might want a different colour if they use a different skin than I do, though.
Bless you.
-
Well, the line decides it. Let's migrate to new software. Without a line.
-
@tnp said in General MSB announcements:
Well, the line decides it. Let's migrate to new software. Without a line.
-
The line is a little irritating, but it could be useful. Since it's different colours for posts you haven't read yet... so you know where you're up to later.
-
The little line is ESPECIALLY irritating on my phone though. Namely because it doesn't fully... work.
-
I have no idea what line y'all are even talking about and now I keep second-guessing myself as to whether the lines I am looking at have been there the whole time or not.