Wedge
Public area => The Pub => Bug reports => Topic started by: Arantor on February 29th, 2012, 02:50 PM
-
It can be added easily enough to the new PM settings page :)
-
OK, question of the day.
SMF's post notifications has a user on/off for the body text - plus a master override. PMs on the other hand, have neither. You get it every time.
Now, adding a master override is easy, adding a user preference not quite so much. Do we want to allow the user preference on this or not? (It is actually a schema change if we do, but not a huge one, just an extra tinyint in the members table)
-
I say no for user preference, its just one more setting most people will not use, and it doesn't really add anything.
-
In that case, let's flip it back the other way. Do we need the ability for users to set a preference on posts, as they can currently do?
Does it add value to have that option? Do users take it?
-
I don't personally think it matters, as Admin on some sites I set it to have it for everyone and on some I set it for none.
-
So you don't ever leave it on by default but turn it off yourself? (This is what I'm wondering, because it would simplify the code to remove it for that too.)
-
Correct, sorry for not being more clear.
-
Anyone else who feels strongly about this one?
-
Yea I do.
Because of our recent pm discussion about editing pms after they're sent. Could be a user setting, either way is fine. Obviously if you want to edit or delete a sent pm, you need to ensure it wasn't sent by email already. Otherwise you can only fix typos...
-
That suggests then that we might want to remove the body text in every case from PM notifications and just be done with it? Not even making it optional, allows for editing after sending - until it has been read, of course.
Plus that then gains the benefit by default of not having messages sent by return email to the admin...
-
I suppose the benefits outweight the inconvenience. :-/
-
Well, they do, but if there's enough people that would prefer to have the option, we can leave the option in - but having the option does constrict what editing you can do of PMs that are as yet unread.
-
I have a feeling that either no one reads the 'SMF bug' topics, or no one cares about the option :P
-
They probably don't :/
-
If a quick read of what's above will suffice; make it a user opt-in to have the body in the notification, off per default (least information leakage that way...)
As for edit/delete, I personally see no conflict whether the body is included in the notification or not. If I send you a PM, then retract it (whether before or after you are notified), a message at the time of retraction (be it by editing or deleting) to say that the recipient has already been notified of the original should serve as sufficient warning to the sender. Stupid people will always be stupid, and no amount of helper code will stop that :)
-
That would certainly seem to cover it, but do we also need a master override to never have that option?
-
It all sounds like a good option. Its one of those settings that I have to wonder if anyone would notice if you just take the message out my default and only let it be an admin choose of whether to include it or not.
-
Which is precisely what I asked, and in fact why I asked it.
I'm not sure whether it's worth being a user preference, and just be an admin one.
-
As a user I know I would never change a feature like that. As an admin I would. Though as an Admin I would be mean and turn off body for posts and pm's in email. Save bandwidth and makes people more inclined to participate. Plus I don't have to worry about getting replies in the catch all lol