User Controls
notification when quoted
-
2019-12-07 at 9:47 AM UTCIt'd be cool to get a notification of some type when someone quotes one of your posts.
thhe thread subscription system is retarded btw. atleast on mobile. I wish subscribed threads bumps and quoted posts acted similar to the inbox notification system -
2019-12-07 at 1:30 PM UTCAgreed. A way to summon people would be cool too. Like, if I wanted to alert you to the thread be able to go @bigthink and have it notify you
-
2019-12-07 at 1:37 PM UTCdoes Larry even read these things?
@lenny -
2019-12-07 at 2:54 PM UTC
-
2019-12-07 at 2:56 PM UTC
-
2019-12-07 at 7:42 PM UTC
-
2019-12-07 at 7:58 PM UTCwell whatever you use its gay as fuckThe following users say it would be alright if the author of this post didn't die in a fire!
-
2019-12-08 at 2:43 AM UTCYeah, it's also almost 20 years in development, has a thriving community of modders, and has an entire forum dedicated to support. It's neat that Lanny wrote this software or w/e, but in the long run it's unlikely that it would withstand the load of a medium sized community.
-
2019-12-08 at 9:57 PM UTC
-
2019-12-08 at 10:04 PM UTC
Originally posted by AngryIVer Yeah, it's also almost 20 years in development, has a thriving community of modders, and has an entire forum dedicated to support. It's neat that Lanny wrote this software or w/e, but in the long run it's unlikely that it would withstand the load of a medium sized community.
its also for fat faggots like you -
2019-12-09 at 2:46 AM UTCThis has been suggested before. In terms of the concept I don't mind it as an option. The two issues as I see it are:
- It has to be opt-out to be useful. But that also makes it abusable-by-default. The two ways to do opt-out are mention target full opt-out which means people are going to be crying to me when someone tags them in every shitpost because they have a binary on/off toggle or user-to-user mentioner opt out kind of like "blocking" (e.g. I don't want speckles to be able to flood my notifications with mentions so I go add him to my block list) which in terms of implementation is significantly more work for the server, more effort to code, more effort to maintain and a less intuitive user experience no matter which way you look at it which is an issue because we live in a world where people still PM me because they don't know how to resize images for avatars.
- The implementation is inherently expensive and a pain in the neck. Right now when someone makes a post we basically just throw it in the database. That's nice. That's fast. That's one query. We don't even need a transaction for it. If we potentially need to send out notifications on every new post then it means to need to parse posts when we get them, we need to do a query for every user mentioned to determine if they exist or not, we need to do at least one more query per notification to be sent out. Then reasonably we need to open a transaction to do all this because there are race conditions like "mention target spawns/disappears/blocks/unblocks while this is happening". Then if we go the "@-mention" route we either need to do this process again during post rendering or create shitty heavy new JS to support mention-by-pk in a way that's half way usable. This is all a big performance hit and requires parse-time restrictions to keep it from being a DoS vector.
The whole thing is complicated and expensive and probably costs a lot more than it's worth. If someone really wants to do it I'd consider quote only notifications with mention-target binary opt-out to be the best option since there's no read penalty and the UI isn't a total nightmare. But as it stands it's not something I'm super excited about. -
2019-12-09 at 11:43 AM UTC
Originally posted by Lanny This has been suggested before. In terms of the concept I don't mind it as an option. The two issues as I see it are:
- It has to be opt-out to be useful. But that also makes it abusable-by-default. The two ways to do opt-out are mention target full opt-out which means people are going to be crying to me when someone tags them in every shitpost because they have a binary on/off toggle or user-to-user mentioner opt out kind of like "blocking" (e.g. I don't want speckles to be able to flood my notifications with mentions so I go add him to my block list) which in terms of implementation is significantly more work for the server, more effort to code, more effort to maintain and a less intuitive user experience no matter which way you look at it which is an issue because we live in a world where people still PM me because they don't know how to resize images for avatars.
- The implementation is inherently expensive and a pain in the neck. Right now when someone makes a post we basically just throw it in the database. That's nice. That's fast. That's one query. We don't even need a transaction for it. If we potentially need to send out notifications on every new post then it means to need to parse posts when we get them, we need to do a query for every user mentioned to determine if they exist or not, we need to do at least one more query per notification to be sent out. Then reasonably we need to open a transaction to do all this because there are race conditions like "mention target spawns/disappears/blocks/unblocks while this is happening". Then if we go the "@-mention" route we either need to do this process again during post rendering or create shitty heavy new JS to support mention-by-pk in a way that's half way usable. This is all a big performance hit and requires parse-time restrictions to keep it from being a DoS vector.
The whole thing is complicated and expensive and probably costs a lot more than it's worth. If someone really wants to do it I'd consider quote only notifications with mention-target binary opt-out to be the best option since there's no read penalty and the UI isn't a total nightmare. But as it stands it's not something I'm super excited about.
Okay, but let's be honest, how much server load can 12 people mentioning eachother back and forth really create? -
2019-12-09 at 3:31 PM UTC
Originally posted by AngryIVer Okay, but let's be honest, how much server load can 12 people mentioning eachother back and forth really create?
A post can have an unbounded number of mentions in it, and initiating a transaction has to lock things, so it can be significant. And ISS is designed to be run on low end hardware. Like sure, I'm not saying it's going to grind everything to a halt, the NiS servers could handle it pretty well, but it's going to take post creation from relatively very fast to kind of expensive and I'm just not convinced that what it does is worth it. I mean yes, probably a good move for increasing engagement (I'm sure people are more likely to read a thread where they get mentioned) but engagement has never really been a central design goal. -
2019-12-09 at 4:35 PM UTCoh yeah i could ruin that feature pretty quickly. Just make a thread in half baked and spam
@Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot @Lanny ur a faggot -
2019-12-09 at 4:37 PM UTCthat will overload the potato with the edge connection
-
2019-12-10 at 8:56 AM UTC
Originally posted by Lanny This has been suggested before. In terms of the concept I don't mind it as an option. The two issues as I see it are:
- It has to be opt-out to be useful. But that also makes it abusable-by-default. The two ways to do opt-out are mention target full opt-out which means people are going to be crying to me when someone tags them in every shitpost because they have a binary on/off toggle or user-to-user mentioner opt out kind of like "blocking" (e.g. I don't want speckles to be able to flood my notifications with mentions so I go add him to my block list) which in terms of implementation is significantly more work for the server, more effort to code, more effort to maintain and a less intuitive user experience no matter which way you look at it which is an issue because we live in a world where people still PM me because they don't know how to resize images for avatars.
- The implementation is inherently expensive and a pain in the neck. Right now when someone makes a post we basically just throw it in the database. That's nice. That's fast. That's one query. We don't even need a transaction for it. If we potentially need to send out notifications on every new post then it means to need to parse posts when we get them, we need to do a query for every user mentioned to determine if they exist or not, we need to do at least one more query per notification to be sent out. Then reasonably we need to open a transaction to do all this because there are race conditions like "mention target spawns/disappears/blocks/unblocks while this is happening". Then if we go the "@-mention" route we either need to do this process again during post rendering or create shitty heavy new JS to support mention-by-pk in a way that's half way usable. This is all a big performance hit and requires parse-time restrictions to keep it from being a DoS vector.
The whole thing is complicated and expensive and probably costs a lot more than it's worth. If someone really wants to do it I'd consider quote only notifications with mention-target binary opt-out to be the best option since there's no read penalty and the UI isn't a total nightmare. But as it stands it's not something I'm super excited about.
would an 'opt in' checkbox, visible* quote notification check (as opposed to a blind mailbox)*, blocking functionality, and a ping restriction solve all of these issues?
e* -
2019-12-10 at 9:05 AM UTCactually there's like 50 lannys, l idk how* the 'parsing' (I think) would know which lanny to notify without the randomly generated words.
(I know nothing about what I'm talking about btw)
and @lanny add me on DC nigger -
2019-12-10 at 11:14 AM UTC
Originally posted by Lanny A post can have an unbounded number of mentions in it, and initiating a transaction has to lock things, so it can be significant. And ISS is designed to be run on low end hardware. Like sure, I'm not saying it's going to grind everything to a halt, the NiS servers could handle it pretty well, but it's going to take post creation from relatively very fast to kind of expensive and I'm just not convinced that what it does is worth it. I mean yes, probably a good move for increasing engagement (I'm sure people are more likely to read a thread where they get mentioned) but engagement has never really been a central design goal.
I'm being flippant
Also, make like a 3 mention limit per post -
2019-12-26 at 6:30 AM UTCWhaiting for beeno reply
-
2019-12-26 at 11:27 AM UTCtheres nothing that says i am an attention whore more than this.
ever.
Originally posted by bigthink It'd be cool to get a notification of some type when someone quotes one of your posts.
thhe thread subscription system is retarded btw. atleast on mobile. I wish subscribed threads bumps and quoted posts acted similar to the inbox notification system
