Feature request: notifications for downvotes
-
@Tsaukpaetra said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
@Tsaukpaetra Yeah, the naming of stuff totally matters.
I seriously don't understand how NodeBB could fuck that up. I could write the logic in my sleep. I'd have PRed it a long time ago if I knew JS.You know Java right? It's like that, but not nearly as verbose.
High claims but you show no proof of your mighty abilities.
You're funny. I've seen enough JS to know that I have no idea what I'm doing.
I would say I could prove it by doing it withb
, but that's going to have zero client side code so that might be difficult.
... I should really go back to working on that.
-
@pie_flavor said in Feature request: notifications for downvotes:
I have no idea what I'm doing
I don't really know anything about it either. I know enough Visual Basic to have hacked together a SPA serving as the front end for Master Server. All I hear are weasel excuses.
-
@Tsaukpaetra And I don't. See?
-
@pie_flavor said in Feature request: notifications for downvotes:
@Tsaukpaetra And I don't. See?
No. Elaborate, if you will?
-
@Tsaukpaetra I do not know JS. At all. I don't know the language and I don't know the standard library and I don't know Node's library. I also know enough about it to know that there are roadblocks in the way of learning by doing, especially when the 'doing' would be screwing with NodeBB.
-
@Tsaukpaetra said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
@JBert Yeah, and it's not like it's much different when @Tsaukpaetra arrives. So?
Once jellypotato is resolved satisfactorily I'll no longer need to track my read position. Until then, have a nice bodge!
But then I will no longer feel special and appreciated.
-
@pie_flavor said in Feature request: notifications for downvotes:
@Tsaukpaetra I do not know JS. At all. I don't know the language and I don't know the standard library and I don't know Node's library. I also know enough about it to know that there are roadblocks in the way of learning by doing, especially when the 'doing' would be screwing with NodeBB.
Didn't stop Discourse. I mean....
-
@topspin said in Feature request: notifications for downvotes:
@Tsaukpaetra said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
@JBert Yeah, and it's not like it's much different when @Tsaukpaetra arrives. So?
Once jellypotato is resolved satisfactorily I'll no longer need to track my read position. Until then, have a nice bodge!
But then I will no longer feel special and appreciated.
I'll just have to people more!
-
@pie_flavor said in Feature request: notifications for downvotes:
I do not know JS. At all.
Oh, and don't worry about that, I'll give you a primer!
This is how you make a function:
function myAwesomeFunction() { //Code goes here }
This is how you variable:
var itsAVar = 9
This variable is an object with properties!
var objectWithProperties = { 'aGoodProperty': 'Nothing to see here', 'noGoodDead': 9 }
There, practically all you really need to know about javascript!
Now, go do a Jeff Atwood and start hacking!
-
@pie_flavor said in Feature request: notifications for downvotes:
@Tsaukpaetra Yeah, the naming of stuff totally matters.
I seriously don't understand how NodeBB could fuck that up. I could write the logic in my sleep. I'd have PRed it a long time ago if I knew JS.I mean, what possible reason could there be for a forum not having a database record for each (user id, post id) pair that get written to while you scroll?
-
@Tsaukpaetra said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
@JBert Yeah, and it's not like it's much different when @Tsaukpaetra arrives. So?
Once jellypotato is resolved satisfactorily I'll no longer need to track my read position. Until then, have a nice bodge!
I have yet to see an infinite scrolling application that doesn't have it in one form or another, so don't hold your breath.
-
@pie_flavor said in Feature request: notifications for downvotes:
@Tsaukpaetra said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
@JBert Yeah, and it's not like it's much different when @Tsaukpaetra arrives. So?
Once jellypotato is resolved satisfactorily I'll no longer need to track my read position. Until then, have a nice bodge!
Wouldn't that be nice. As it is, Discourse is kicking NodeBB's ass.
lolol
-
@Groaner said in Feature request: notifications for downvotes:
don't hold your breath.
Would that help me sleep at night?
Filed under: Stupid sleep apnea
-
@Tsaukpaetra said in Feature request: notifications for downvotes:
You know Java right? It's like that, but not nearly as verbose.
There's something I keep hearing about promises and futures and coroutines, which as far as I can tell, mean something along the lines of "threads." Additionally, the
$
symbol seems to be very important. Is that because Javascript developers make a lot of money?Of course, it's hard to be able to learn Javascript, as every time someone posts a question about it on SO, the default answer is, "Have you tried jQuery?" I think you're also supposed to know something about AngularJS and be able to pick yourself up by your bootstraps to learn new frameworks. While about 95% of the Javascript I write is to invoke methods from the DevExpress client API (or to check/uncheck a range of checkboxes without having to postback to the server), apparently the market is changing.
Nowadays, instead of using filthy ASP.NET WebForms, we're supposed to use this fancy new ASP.NET Marvel vs. Capcom framework, which seems to be a hundred times more complicated than WebForms and looks reminiscent of classic ASP. With all this change in the marketplace, I fear that my employment prospects are dim in 2018, given that I haven't been keeping up with these Anglequery Marvel vs. Capcoms. :(
-
@Tsaukpaetra said in Feature request: notifications for downvotes:
@Groaner said in Feature request: notifications for downvotes:
don't hold your breath.
Would that help me sleep at night?
Filed under: Stupid sleep apnea
See pap. See pap run.
-
@Groaner said in Feature request: notifications for downvotes:
@Tsaukpaetra said in Feature request: notifications for downvotes:
@Groaner said in Feature request: notifications for downvotes:
don't hold your breath.
Would that help me sleep at night?
Filed under: Stupid sleep apnea
See pap. See pap run.
See Pappy choke you in your sleep, chanting, "why aren't you breathing! Breathe in motherfucker!"
-
@Groaner said in Feature request: notifications for downvotes:
fear that my employment prospects are dim in 2018
Likewise, for I program in c++ like it's 1989.
-
@ben_lubar said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
@Tsaukpaetra Yeah, the naming of stuff totally matters.
I seriously don't understand how NodeBB could fuck that up. I could write the logic in my sleep. I'd have PRed it a long time ago if I knew JS.I mean, what possible reason could there be for a forum not having a database record for each (user id, post id) pair that get written to while you scroll?
Please point out where in my post I said 'database'. The implementation details aren't important, the feature is. You've got a row for 'upvoted', don't you? Is @Tsaukpaetra taking up a lot of space in the database?
-
@Groaner said in Feature request: notifications for downvotes:
@Tsaukpaetra said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
@JBert Yeah, and it's not like it's much different when @Tsaukpaetra arrives. So?
Once jellypotato is resolved satisfactorily I'll no longer need to track my read position. Until then, have a nice bodge!
I have yet to see an infinite scrolling application that doesn't have it in one form or another, so don't hold your breath.
I have; it's called Discourse.
-
@Groaner said in Feature request: notifications for downvotes:
@Tsaukpaetra said in Feature request: notifications for downvotes:
You know Java right? It's like that, but not nearly as verbose.
There's something I keep hearing about promises and futures and coroutines, which as far as I can tell, mean something along the lines of "threads." Additionally, the
$
symbol seems to be very important. Is that because Javascript developers make a lot of money?Of course, it's hard to be able to learn Javascript, as every time someone posts a question about it on SO, the default answer is, "Have you tried jQuery?" I think you're also supposed to know something about AngularJS and be able to pick yourself up by your bootstraps to learn new frameworks. While about 95% of the Javascript I write is to invoke methods from the DevExpress client API (or to check/uncheck a range of checkboxes without having to postback to the server), apparently the market is changing.
Nowadays, instead of using filthy ASP.NET WebForms, we're supposed to use this fancy new ASP.NET Marvel vs. Capcom framework, which seems to be a hundred times more complicated than WebForms and looks reminiscent of classic ASP. With all this change in the marketplace, I fear that my employment prospects are dim in 2018, given that I haven't been keeping up with these Anglequery Marvel vs. Capcoms. :(
That's about it, plus all the hackiness that they use to pretend they're object oriented, like whatever the fuck a prototype is.
-
@Tsaukpaetra said in Feature request: notifications for downvotes:
@Groaner said in Feature request: notifications for downvotes:
@Tsaukpaetra said in Feature request: notifications for downvotes:
@Groaner said in Feature request: notifications for downvotes:
don't hold your breath.
Would that help me sleep at night?
Filed under: Stupid sleep apnea
See pap. See pap run.
See Pappy choke you in your sleep, chanting, "why aren't you breathing! Breathe in motherfucker!"
Two family members express similar sentiments about their respective devices.
-
@Tsaukpaetra said in Feature request: notifications for downvotes:
@Groaner said in Feature request: notifications for downvotes:
fear that my employment prospects are dim in 2018
Likewise, for I program in c++ like it's 1989.
I dunno, some of the C++11 stuff is pretty cool. It's nice being able to type
for(auto i = mymap.begin(); i != mymap.end(); i++)
instead of
for(std::map<std::string, MyReallyLongAndAnnoyingClassName>::const_iterator i = mymap.begin(); i != mymap.end(); i++)
-
@pie_flavor said in Feature request: notifications for downvotes:
Is @Tsaukpaetra taking up a lot of space in the database?
I am pretty fat...
-
@pie_flavor said in Feature request: notifications for downvotes:
@ben_lubar said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
@Tsaukpaetra Yeah, the naming of stuff totally matters.
I seriously don't understand how NodeBB could fuck that up. I could write the logic in my sleep. I'd have PRed it a long time ago if I knew JS.I mean, what possible reason could there be for a forum not having a database record for each (user id, post id) pair that get written to while you scroll?
Please point out where in my post I said 'database'. The implementation details aren't important, the feature is. You've got a row for 'upvoted', don't you? Is @Tsaukpaetra taking up a lot of space in the database?
@Tsaukpaetra is spending time based on a button he intentionally pressed. Imagine the horror that would be thousands of requests per second just from scrolling down a page.
The reason Meta.D works fine and WTDWTF ran like shit is that Meta.D uses the Discourse definition of "big forum" which is "100+ members" and WTDWTF has 10000+ members.
-
@Groaner said in Feature request: notifications for downvotes:
@Tsaukpaetra said in Feature request: notifications for downvotes:
@Groaner said in Feature request: notifications for downvotes:
fear that my employment prospects are dim in 2018
Likewise, for I program in c++ like it's 1989.
I dunno, some of the C++11 stuff is pretty cool. It's nice being able to type
for(auto i = mymap.begin(); i != mymap.end(); i++)
instead of
for(std::map<std::string, MyReallyLongAndAnnoyingClassName>::const_iterator i = mymap.begin(); i != mymap.end(); i++)
WHAT IS THIS MAGIC??!?!?
-
@ben_lubar said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
@ben_lubar said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
@Tsaukpaetra Yeah, the naming of stuff totally matters.
I seriously don't understand how NodeBB could fuck that up. I could write the logic in my sleep. I'd have PRed it a long time ago if I knew JS.I mean, what possible reason could there be for a forum not having a database record for each (user id, post id) pair that get written to while you scroll?
Please point out where in my post I said 'database'. The implementation details aren't important, the feature is. You've got a row for 'upvoted', don't you? Is @Tsaukpaetra taking up a lot of space in the database?
@Tsaukpaetra is spending time based on a button he intentionally pressed. Imagine the horror that would be thousands of requests per second just from scrolling down a page.
The reason Meta.D works fine and WTDWTF ran like shit is that Meta.D uses the Discourse definition of "big forum" which is "100+ members" and WTDWTF has 10000+ members.
Oh! And don't forget the regular deletion of content. It's easier to be performant with less data in the system...
-
@ben_lubar said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
@ben_lubar said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
@Tsaukpaetra Yeah, the naming of stuff totally matters.
I seriously don't understand how NodeBB could fuck that up. I could write the logic in my sleep. I'd have PRed it a long time ago if I knew JS.I mean, what possible reason could there be for a forum not having a database record for each (user id, post id) pair that get written to while you scroll?
Please point out where in my post I said 'database'. The implementation details aren't important, the feature is. You've got a row for 'upvoted', don't you? Is @Tsaukpaetra taking up a lot of space in the database?
@Tsaukpaetra is spending time based on a button he intentionally pressed. Imagine the horror that would be thousands of requests per second just from scrolling down a page.
The reason Meta.D works fine and WTDWTF ran like shit is that Meta.D uses the Discourse definition of "big forum" which is "100+ members" and WTDWTF has 10000+ members.
And like fifty active users. Also, there's no reason to set a read flag on a read post, and you don't scroll through thousands of posts a second.
-
@Tsaukpaetra said in Feature request: notifications for downvotes:
@Groaner said in Feature request: notifications for downvotes:
@Tsaukpaetra said in Feature request: notifications for downvotes:
@Groaner said in Feature request: notifications for downvotes:
fear that my employment prospects are dim in 2018
Likewise, for I program in c++ like it's 1989.
I dunno, some of the C++11 stuff is pretty cool. It's nice being able to type
for(auto i = mymap.begin(); i != mymap.end(); i++)
instead of
for(std::map<std::string, MyReallyLongAndAnnoyingClassName>::const_iterator i = mymap.begin(); i != mymap.end(); i++)
WHAT IS THIS MAGIC??!?!?
I'm still stuck with Visual C++ 2010 until I recompile all my dependencies, and it even works in that old version.
-
@ben_lubar said in Feature request: notifications for downvotes:
@blakeyrat said in Feature request: notifications for downvotes:
@ben_lubar You should do the thing Kuro does where he types "kappa" without actually including the kappa emote, thus confusing everything everywhere.
No, @ben_lubar, that's a Doom Koopa.
-
@Lorne-Kates said in Feature request: notifications for downvotes:
@ben_lubar said in Feature request: notifications for downvotes:
I'd like to get rid of the voting system
Wait until one of my post is the highest rated post in the forum.
Then shut down the voting.
Because I'm the best.
-
@pie_flavor said in Feature request: notifications for downvotes:
Is @Tsaukpaetra taking up a lot of space
Dude ... fat shaming is
-
@pie_flavor said in Feature request: notifications for downvotes:
Unread status is preserved per post (with a little notifier visible on the post itself), which only gets flipped if the post is actually on your screen (and not, say, if you view a post several posts down).
And I can't manually reset it for when I want to see if it's short enough I can just quickly read and respond or if it's long enough that I will need to take some time (later!) to respond on a point-by-point basis.
Additionally you get notifications for all your likes, mentions, and tracked threads, and they don't interfere with one another or cause anything to get set to read when it shouldn't.
But I don't want notifications for all the upvotes I receive.
And a tracked thread can have only one "last read" position, so if I'm away from a thread for a while and other people post in it, and then someone mentions me and I click the notification to see what they said... Oh, whoops! Now my "last read" position has suddenly skipped a dozen or hundred posts.
They also take up a tiny amount of space each, so the notifications box generally accommodates all of them at once.
"Generally"? And what happens when it doesn't? Do you have to scroll the box, or do you have to go to another page to view them all?
And as a bonus, not only do they only get cleared when you view the relevant post, they always get cleared when you view the relevant post -
As noted above, I may not always want to have them always cleared.
no clicking every single like notification to make it go away from posts you've already seen.
NodeBB does that, too. You just have to perform a hard refresh action in the forum. (Ok, so it's not perfect, but neither is Discourse's.)
Imagine that, basic functionality.
:horse-whinny.mp3:
-
@djls45 said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
Unread status is preserved per post (with a little notifier visible on the post itself), which only gets flipped if the post is actually on your screen (and not, say, if you view a post several posts down).
And I can't manually reset it for when I want to see if it's short enough I can just quickly read and respond or if it's long enough that I will need to take some time (later!) to respond on a point-by-point basis.
That's what bookmarks are for.
Additionally you get notifications for all your likes, mentions, and tracked threads, and they don't interfere with one another or cause anything to get set to read when it shouldn't.
But I don't want notifications for all the upvotes I receive.
Then you can disable that. What I was contrasting that with was the bell's obsession with showing you the least relevant notifications, and not all the upvotes, and 'x and y replied' when a b c d e and f also did, and so on and so forth.
And a tracked thread can have only one "last read" position, so if I'm away from a thread for a while and other people post in it, and then someone mentions me and I click the notification to see what they said... Oh, whoops! Now my "last read" position has suddenly skipped a dozen or hundred posts.
Except if each post has its own read status, even if your last read position jumps down a ton of posts, you can still find your spot again with relative ease, especially since scrolling quickly over a post will not mark it as read.
They also take up a tiny amount of space each, so the notifications box generally accommodates all of them at once.
"Generally"? And what happens when it doesn't? Do you have to scroll the box, or do you have to go to another page to view them all?
You go to another page, which has a very nice compressed format, prioritizes read over unread, and not only is it infiniscroll but it still loads a ton at a time for maximum convenience. Also, unlike NodeBB, there's an option for viewing upboat notifications once a day instead of fixed increments, which is my preferred browsing mode.
no clicking every single like notification to make it go away from posts you've already seen.
NodeBB does that, too. You just have to perform a hard refresh action in the forum. (Ok, so it's not perfect, but neither is Discourse's.)
I've never seen that work. Ever. Discourse's, on the other hand, is perfect.
-
@pie_flavor said in Feature request: notifications for downvotes:
And like fifty active users.
Try "ten thousand unique readers this week".
-
@ben_lubar And are all those people registered? Because last read location doesn't save if you don't have an account.
-
@pie_flavor said in Feature request: notifications for downvotes:
@ben_lubar And are all those people registered? Because last read location doesn't save if you don't have an account.
That's true here, but not on Discourse.
-
@ben_lubar said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
And like fifty active users.
Try "ten thousand unique readers this week".
90/9/1 rule in action, motherfuckers!
-
@ben_lubar said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
@ben_lubar And are all those people registered? Because last read location doesn't save if you don't have an account.
That's true here, but not on Discourse.
I wasn't aware of that. Are you sure that's server-side?
-
@Groaner said in Feature request: notifications for downvotes:
@Tsaukpaetra said in Feature request: notifications for downvotes:
@Groaner said in Feature request: notifications for downvotes:
fear that my employment prospects are dim in 2018
Likewise, for I program in c++ like it's 1989.
I dunno, some of the C++11 stuff is pretty cool. It's nice being able to type
for(auto i = mymap.begin(); i != mymap.end(); i++)
instead of
for(std::map<std::string, MyReallyLongAndAnnoyingClassName>::const_iterator i = mymap.begin(); i != mymap.end(); i++)
You have overlooked the even shorter:
for (auto& kv : mymap)
-
@pie_flavor said in Feature request: notifications for downvotes:
@Tsaukpaetra said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
@Tsaukpaetra said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
@JBert Yeah, and it's not like it's much different when @Tsaukpaetra arrives. So?
Once jellypotato is resolved satisfactorily I'll no longer need to track my read position. Until then, have a nice bodge!
Wouldn't that be nice. As it is, Discourse is kicking NodeBB's ass.
Is it?
Yup! Unread status is preserved per post (with a little notifier visible on the post itself), which only gets flipped if the post is actually on your screen (and not, say, if you view a post several posts down). Additionally you get notifications for all your likes, mentions, and tracked threads, and they don't interfere with one another or cause anything to get set to read when it shouldn't. They also take up a tiny amount of space each, so the notifications box generally accommodates all of them at once. And as a bonus, not only do they only get cleared when you view the relevant post, they always get cleared when you view the relevant post - no clicking every single like notification to make it go away from posts you've already seen.
Imagine that, basic functionality.
There are some things does better than ; I've never denied that. But there are many it does much, much worse. Not least of which is the attitude of the developers. Overall, is the winner by a big margin.
-
@HardwareGeek Oh, I'm sure the back end does some really strange stuff, like that avatar CDN thing. And here's the fun part: I don't care. Front end usability comes before everything else, and NodeBB sucks balls in that department.
-
@pie_flavor said in Feature request: notifications for downvotes:
Unread status is preserved per post (with a little notifier visible on the post itself), which only gets flipped if the post is actually on your screen
When it works.
(Probably 'd)
-
@pie_flavor said in Feature request: notifications for downvotes:
@Groaner said in Feature request: notifications for downvotes:
@Tsaukpaetra said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
@JBert Yeah, and it's not like it's much different when @Tsaukpaetra arrives. So?
Once jellypotato is resolved satisfactorily I'll no longer need to track my read position. Until then, have a nice bodge!
I have yet to see an infinite scrolling application that doesn't have it in one form or another, so don't hold your breath.
I have; it's called Discourse.
LOL
-
@pie_flavor said in Feature request: notifications for downvotes:
Oh, I'm sure the back end does some really strange stuff, like that avatar CDN thing. And here's the fun part: I don't care. Front end usability comes before everything else, and NodeBB sucks balls in that department.
Discourse sucks so many balls in that department it should implement a BDN.
-
-
@loopback0 said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
Oh, I'm sure the back end does some really strange stuff, like that avatar CDN thing. And here's the fun part: I don't care. Front end usability comes before everything else, and NodeBB sucks balls in that department.
Discourse sucks so many balls in that department it should implement a BDN.
-
@loopback0 said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
Oh, I'm sure the back end does some really strange stuff, like that avatar CDN thing. And here's the fun part: I don't care. Front end usability comes before everything else, and NodeBB sucks balls in that department.
Discourse sucks so many balls in that department it should implement a BDN.
I haven't seen any deficiency in the UX. Care to elaborate?
-
@pie_flavor said in Feature request: notifications for downvotes:
@djls45 said in Feature request: notifications for downvotes:
@pie_flavor said in Feature request: notifications for downvotes:
Unread status is preserved per post (with a little notifier visible on the post itself), which only gets flipped if the post is actually on your screen (and not, say, if you view a post several posts down).
And I can't manually reset it for when I want to see if it's short enough I can just quickly read and respond or if it's long enough that I will need to take some time (later!) to respond on a point-by-point basis.
That's what bookmarks are for.
Additionally you get notifications for all your likes, mentions, and tracked threads, and they don't interfere with one another or cause anything to get set to read when it shouldn't.
But I don't want notifications for all the upvotes I receive.
Then you can disable that. What I was contrasting that with was the bell's obsession with showing you the least relevant notifications, and not all the upvotes, and 'x and y replied' when a b c d e and f also did, and so on and so forth.
And a tracked thread can have only one "last read" position, so if I'm away from a thread for a while and other people post in it, and then someone mentions me and I click the notification to see what they said... Oh, whoops! Now my "last read" position has suddenly skipped a dozen or hundred posts.
Except if each post has its own read status, even if your last read position jumps down a ton of posts, you can still find your spot again with relative ease, especially since scrolling quickly over a post will not mark it as read.
They also take up a tiny amount of space each, so the notifications box generally accommodates all of them at once.
"Generally"? And what happens when it doesn't? Do you have to scroll the box, or do you have to go to another page to view them all?
You go to another page, which has a very nice compressed format, prioritizes read over unread, and not only is it infiniscroll but it still loads a ton at a time for maximum convenience. Also, unlike NodeBB, there's an option for viewing upboat notifications once a day instead of fixed increments, which is my preferred browsing mode.
no clicking every single like notification to make it go away from posts you've already seen.
NodeBB does that, too. You just have to perform a hard refresh action in the forum. (Ok, so it's not perfect, but neither is Discourse's.)
I've never seen that work. Ever. Discourse's, on the other hand, is perfect.
So, basically, I'm doing everything wrong and I should change my preferences to match the way the website works.
-
@topspin said in Feature request: notifications for downvotes:
@Groaner said in Feature request: notifications for downvotes:
@Tsaukpaetra said in Feature request: notifications for downvotes:
@Groaner said in Feature request: notifications for downvotes:
fear that my employment prospects are dim in 2018
Likewise, for I program in c++ like it's 1989.
I dunno, some of the C++11 stuff is pretty cool. It's nice being able to type
for(auto i = mymap.begin(); i != mymap.end(); i++)
instead of
for(std::map<std::string, MyReallyLongAndAnnoyingClassName>::const_iterator i = mymap.begin(); i != mymap.end(); i++)
You have overlooked the even shorter:
for (auto& kv : mymap)
+1
But does that allow adding items to or removing items frommymap
within the loop?
-
@djls45 In response to the first one, maybe. But not to the rest.