:fa_bullhorn: The sound of AN ANNOUNCEMENT BEING MADE (or: Request for Comments: Comments)
-
Wow, NodeBB feels so snappy when compared to Discourse. And then to think that it's hosted on a home connection!
One minor gripe: When someone uses an abbr tag, Discourse prints the description after the abbreviation when on a mobile device. NodeBB doesn't seem to do that, which is an inconvenience.
-
One minor gripe: When someone uses an abbr tag, Discourse prints the description after the abbreviation when on a mobile device. NodeBB doesn't seem to do that, which is an inconvenience.
That's actually a custom CSS rule here.
Paging @PJH.
-
That's actually a custom CSS rule here.
Oh, really? I didn't know.
It's a very useable rule though!
-
That's actually a custom CSS rule here.
And it works because the CCS for mobile is different to desktop; not sure if that's possible under NodeBB - I'll have a poke around.
-
Worst case scenario: use an
@media
query? The tablet limit might be tricky but...
-
Looking good so far. And I agree with everyone else's assertions that nodebb running on your 2Mhz 386 still feels far more responsive than discosauce.
One query - is it possible to search in a thread? I'm on the 38k post thread but both magnifying glasses only seem to do full-forum search, and CTRL-F is limited (or is that "not hijacked") to the loaded DOM.
-
That said, everything is snappy except the title searches;
https://discourse.local.lubar.me/search/stuff?in=titlesposts
...takes ~30 seconds or more. If I repeat it then it's faster (missing index compensated for by cached results?)
-
is it possible to search in a thread?
By default, it just searches the text in the browser. You can change a setting to enable searching all posts in the thread.
-
Huh... should that not be enabled by default, do we think?
Otherwise we've got two mag glasses doing (what I think are) the same thing and CTRL F doing nothing massively useful (in fact, that would be a dicksource regression, if my memory serves me right?)
-
it works because the CCS for mobile is different to desktop; not sure if that's possible under NodeBB
Maybe NodeBB applies a class to the
<html>
or<body>
tag to indicate that it's mobile? I can't access a DOM inspector right now, because mobile.
-
And then to think that it's hosted on a home connection!
Not just any home connection...
-
@PJH said:
it works because the CCS for mobile is different to desktop; not sure if that's possible under NodeBB
Maybe NodeBB applies a class to the
<html>
or<body>
tag to indicate that it's mobile? I can't access a DOM inspector right now, because mobile.Nothing immediately apparent.
/* Show abbr and a title contents on mobile */ @media screen and (max-width: 800px) { abbr[title]:after{ content: " [" attr(title) "]"; } }
seems to be OK, though the
max-width
will probably need tweaking.
-
max-width
should probably be768px
-
While you're there adding CSS, you might want to add
html,body { height:100%; }
That fixes the slide-out menu animation clipping (easiest to see on a page with not a lot of content on mobile like unread topics or a very small topic/category)
-
Something you could watch, the media queries level 4 draft will add support for
@media (pointer: [none|coarse|fine])
It's not supported yet on most browsers, but it'd take the guesswork out of this.
-
I posted a screenshot of this happening on nodebb...
I'd post it here but DiscoUpload took more than 5 minutes and I gave up...
https://discourse.local.lubar.me/topic/18906/this-is-an-example-topic
-
I'd post it here but DiscoUpload took more than 5 minutes and I gave up...https://discourse.local.lubar.me/topic/18906/this-is-an-example-topic
Hard-refresh and try again?
-
All good, thanks!
-
Hmm.
-
That's a
<big>
issue...
-
Looks a bit small to me...
-
.. and obviously..
-
Everyone can now access https://discourse.local.lubar.me/
You'll have to reset your password before you log in as passwords are not part of the import.
Um… What about people who used a one-time email address to sign up? Can you notify me before the actual migration so I can change my email to a temporary email address I actually have access to?
-
Uh... About that...
PM me the email address you want.
-
Can I do that when the actual migration happens? Because the email address would be invalid in a few days anyway.
-
Not sure abut this color scheme..
-
Ok, any edits to anything that was created before today's downtime will not be kept. You may continue to post and upload stuff, but any topic title or post content that was part of today's backup is effectively locked until we're on NodeBB.
-
Worst case scenario: use an
@media
query? The tablet limit might be tricky but...That's one of the easiest media queries to do.
.after-abbr { display: none; }
@media (width <= 768px) { .after-abbr {display: inline; } }
MOTHERFUCKING CSS
-
dashit?
I went there to log in. Couldn't remember my username and password, so I figured "I'll look at my Saved Passwords".
I press alt-T to bring up "Tools", and it redirects to https://discourse.local.lubar.me/tags
NO! Bad NodeBB. Do NOT fucking start intercepting command keys. {rubs NodeBB's nose in Discourse's mistakes} Don't do that. We took Discourse outback and fucked it with a shotgun. Learn!
-
Minor gripe: I put in my email address to reset the password. Waiting on that to arrive. But then for the hell of it, I put in a bad email address. And I got an error message.
Maaaaaaaaaaybe we shouldn't information-leak the existence of email addresses?
-
That may be something that should be announced globally......
-
@Lorne_Kates said:
NO! Bad NodeBB. Do NOT fucking start intercepting command keys. {rubs NodeBB's nose in Discourse's mistakes} Don't do that. We took Discourse outback and fucked it with a shotgun. Learn!
Yeaaaahhh.... that's actually a plugin that was installed at peoples' request........
-
I'll let the @boomzilla, @PJH, @abarker, @Yamikuronue, @aliceif do that.
Ok, any edits to anything that was created before today's downtime will not be kept. You may continue to post and upload stuff, but any topic title or post content that was part of today's backup is effectively locked until we're on NodeBB.
-
Does this look ok to you?
-
You need to specify what day "today" is. If that notice is going to be there longer than another, uh, one hour 10 minutes for my time zone.
EDIT: Actually by "today" I just assumed Ben L meant 3/7/2016, but considering when he posted it maybe he meant 3/8/2016. So without specifying what day "today" is, it's really kind of just entirely meaningless. Good job. I can see this server migration is on-track to go just as well as the one Alex botched last time.
-
You need to specify what day "today" is. If that notice is going to be there longer than another, uh, one hour 10 minutes for my time zone.
Ok, looked the approximate time up and added that.
-
I can see this server migration is on-track to go just as well as the one Alex botched last time.
Yeah, it's a mess. And I didn't know that it would happen so soon.
-
-
You need to specify what day "today" is. If that notice is going to be there longer than another, uh, one hour 10 minutes for my time zone.
July and August are so far away. Do we really have to stay here that long? :(EDIT: Actually by "today" I just assumed Ben L meant 3/7/2016, but considering when he posted it maybe he meant 3/8/2016. So without specifying what day "today" is, it's really kind of just entirely meaningless. Good job. I can see this server migration is on-track to go just as well as the one Alex botched last time.
-
You all know I just had to post this...
-
So when are we really going to move off of Dischorse on WTDWTF?
-
Apparently so, but I would really like a clear summary of the status and when we're moving and so on. It might be obvious to Ben and the mods, but it's not obvious to me.
-
-
You hardly count! You do too much of a job here!
-
It might be obvious to Ben and the mods, but it's not obvious to me
It's not entirely clear to some of the admins...
-
So in summary, there's a migration happening, but no-one knows when except @ben_lubar
-
If this fails I'm putting in a serious proposal to change his username to ben_fubar.
-
Or whereto, although I suspect we're all stuck on MilwaulkeePC for eternity (or until Ben's 9 hour Dwarf Fortress movie uploads).
-
Aw come on. It's a simple translation from one database to another. The only way this can go wrong is if either end is poorly structured and undocumented, with no obvious way of converting the homegrown terminology to a standardised set of terms.
-
Ok, any edits to anything that was created before today's downtime will not be kept. You may continue to post and upload stuff, but any topic title or post content that was part of today's backup is effectively locked until we're on NodeBB.
So...that bit of the import is done, and you'll be doing a further incremental import for stuff posted since then? At some point in the future to be determined?