Blakeyrat pointing out NodeBB problems
-
@RaceProUK said in Blakeyrat pointing out NodeBB problems:
@Lorne-Kates Short of getting Ben to set up private categories, not yet. And yes, I want proper PMs as much as anyone else.
Short of the NodeBB devs realizing they already had a communication system in place on day one and not implementing a half-baked "chat"----
-
@Lorne-Kates Dancing Bear Ware.
"Hey we have real-time communication via. WebSockets, how can we show that off? It doesn't matter if the feature's useful, we need to show-off the WebSockets stuff."
-
@blakeyrat *)
just testing
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
@Lorne-Kates Dancing Bear Ware.
"Hey we have real-time communication via. WebSockets, how can we show that off? It doesn't matter if the feature's useful, we need to show-off the WebSockets stuff."
"Hey, Bob, I like how you implemented WebSockets for the chat. Could we re-engineer the base forum to use WebSockets, too? First, we'll implement websockets, then worry about features. Also, any chance we can work in 're-implementing standard browser/html functions-- except in Angular.js and with half the funtionality' in this release?"
"We'll only have time for that if we skip QA"
"SHIP IT!"
-
@Lorne-Kates I sent a report to g.co/reportbadreflow about community.nodebb.org, so hopefully scroll anchoring will work with NodeBB eventually.
-
@Lorne-Kates said in Blakeyrat pointing out NodeBB problems:
"We'll only have time for that if we skip QA"
Filed under: [Déjà vu](#)
-
You can edit the content of deleted posts. Not sure it's a "bug" per-se, but probably a bad policy to have.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
probably a bad policy to have
[citation needed]
-
Oh and a huge problem:
These bugs:
Are all closed, but none are fixed.
Don't ask me to submit bugs if you're just going to jerk me around.
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
[citation needed]
"Hey Ted, why did you close this thread?"
"It's full of Nazi worship, look." (quickly edits-in Nazi worship)
"Oh, ok."
-
@blakeyrat "Hey Ted, why did you edit all these posts that have Nazi worship in them?"
-
@ben_lubar Look, what the fuck ever.
How about you re-open the bugs you fraudulently closed today? Instead of being a snarky asshole?
-
@blakeyrat those issues were moved to the bug trackers for the respective software, which is linked from each bug report right above where you complained about them being moved.
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
those issues were moved to the bug trackers for the respective software, which is linked from each bug report right above where you complained about them being moved.
But they aren't fixed, so they're still open.
So why did you close them?
-
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
[citation needed]
Right; and there was navigation to that which, IIRC, appeared for a couple hours then disappeared again forever. So it's still not fixed.
You fucking asked me to put in these bugs. Now I find out you never had any intention of taking them seriously at all? Why the fuck did I bother? Are you just wasting all our time to be a jackass?
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
navigation to that
-
@ben_lubar So when it appeared in the tabs at the top of the window, that was never how it was intended to appear or... what?
Why is it buried in that menu I'll never fucking look at in a million years?
Look, what the fuck ever.
Re-open the bugs that are still open. Fine; whatever. I concede your stupid little game. One of the three issues is "fixed". The other two are not.
-
When you go to the Unread page, and select show "new" topics only, then hit "Mark As Read -> All", all the topics are marked as read, not only the new ones.
BUT BEN L SAYS IT'S ALL FIXED!!!
-
Bug:
Go to /unread
Select "New only"
Click into a thread
Go to /unread
Showing "all"
=(
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
Instead of being a snarky asshole?
That's rich.
-
@Lorne-Kates said in Blakeyrat pointing out NodeBB problems:
Select "New only"
This moves you to
/unread/new
, which is a different page than/unread
. Just like clicking the categories button and then selecting a category doesn't change what the categories button does.
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
@Lorne-Kates said in Blakeyrat pointing out NodeBB problems:
Select "New only"
This moves you to
/unread/new
, which is a different page than/unread
. Just like clicking the categories button and then selecting a category doesn't change what the categories button does.That is not good at all. It's less that useful. It isn't discoverable, and it isn't sticky, and users won't even notice when it defaults back. Here:
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
This moves you to /unread/new, which is a different page than /unread.
Who'd you run this UI by before implementing it? Because I'm with Lorne, it's a shitty UI.
-
@ben_lubar said in Blakeyrat pointing out NodeBB problems:
This moves you to /unread/new, which is a different page than /unread.
Can we have an un-broken button that goes to
/unread/new
?
-
Yeah, the new top button made sense (but was borken). The select button is .
-
@ben_lubar oh, and at work if I tried closing a bug 'refiled upstream' it'd get reopened with prejudice.
EDIT: Though our status model is a mess and the fact 'waiting for base bug fix' is not a closed status may be considered weird.
-
post for testing edit of deleted comment
result: it really happens
-
None of the spoiler tags in this topic work, so it's now a spoiler-fest when it wasn't originally.
-
The Unread -> New page shows threads that I've read before.
Heck, I've not just read but POSTED to the Lorne Kates one.
-
@blakeyrat I got the yellow, "a new post was made, click here to refresh" thing and I clicked it and now:
It's closer to showing only new threads, but I've read the bottom two before.
-
@blakeyrat Now I've read all my "new" threads, and I get this:
Nope, try again. There's like 50 unread topics, lying message which is a liar whose pants are currently on fire.
So glad Ben L told me this feature existed. Good thing it's not buggy as shit or anything.
-
I had like 7 notifications left, and ... something happened? and now they're all marked as read, even though I had 7 left and never hit the "mark as read" button.
-
@blakeyrat I accidentally double-clicked on a notification yesterday and it marked them all as read.
-
@FrostCat Unless their double-click timer is a hell of a lot longer than the OS one, I certainly didn't double-click anything.
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
double-click
E_WEB_BROWSER_UX_CONCEPT_NOT_FOUND
The moment your website implements double or right click, you've failed and should be shut down.
(Minor exceptions for shit like Google Spreadsheet which is less a website and more a web-implementation of an application with expected right-and-double-click behavior)
-
@fbmac said in Blakeyrat pointing out NodeBB problems:
post for testing edit of deleted comment
result: it really happens
If you want to stylish that...
-
@blakeyrat said in Blakeyrat pointing out NodeBB problems:
I had like 7 notifications left, and ... something happened? and now they're all marked as read, even though I had 7 left and never hit the "mark as read" button.
Visiting a thread where you had
@mentions
automatically marks the mention notifications as read. (But it doesn't mark upvote notifications as read.)
-
@anotherusername Yes which is retarded. (Also leaving a browser open on a computer 60 miles away with that thread open will ensure notifications about that thread never occur on the computer you're actually using. Which is mega-retarded.) But this wasn't that.
-
Post submitted; NodeBB seems to think it didn't-- the composer never went away.
-
@blakeyrat I was seeing timeout cooties about then.
-
@flabdablet yeah, that was right about when the whole entire site went down for a while.
-
Also in the bloody hell category...
I think it's been bitched about before, but man, the InfiniScroll(tm) implementation to stream in posts toward the end is really bad when you get into a topic you're posting in and other replies are coming in around your replies.
Also, I'd be posting more on the forums in general, but the "Reply" buttons (either to post or to topic) seem to be extremely Discoursistant for me when in IE (IE 11 on Win 10 or IE on WP 8.1). And I'm way too lazy to install a different browser on my phone just to talk to you guys.
-
There's like a million links in this post:
https://what.thedailywtf.com/topic/19171/what-mobile-games-do-you-guys-play-enjoy/29
Literally every one is broken right now.
-
@blakeyrat This isn't a NodeBB problem this is a "Nobody enabled a plugin that supports BBCode syntax on NodeBB" problem.
-
@izzion said in Blakeyrat pointing out NodeBB problems:
the "Reply" buttons (either to post or to topic) seem to be extremely Discoursistant for me when in IE
Me too. I usually have to reload the page to make the reply button work. Firefox 46.0.1.
-
-
@Lorne-Kates How do I make size "fuggin-big" text on NodeBB?
-
@Lorne-Kates said in Blakeyrat pointing out NodeBB problems:
@izzion said in Blakeyrat pointing out NodeBB problems:
InfiniScroll
TURN
OFF
INFINISCROLL!
Like this?
I think that's the largest though, after abusing Markdown and HTML.
-
@Tsaukpaetra Yes, like that. Hows? Because there is no View Raw button anymore.