PM Read Notification

[Pebble]

Hi Everyone!

I was reading this thread : support.proboards.com/thread/508050/indication-received and got a few ideas running around in my head.....
I was thinking (this is still in my head) that this could be done with a super user key, for a certain amount of pms sent. The problem is that Keys should only be set on user action. 
Would clicking the PM to open it count as user action and the key be set on the page that opens? This seems to contradict the rule of not setting a key on page load, but PM's seem to be a different thing to just reading a post on the forum itself.
I also haven't done the logistics of the key and how much data you could get in there but a PM number from the route and a Boolean set on the PM being read and again on reply seems to be the way to go.

A PM sent to multiple people would still just have a 'Read' indication, even if only one person had read it. ( just thinking aloud  and beginning to ramble! )

I don't have much time at the moment to have a go at writing this , if it is within the rules, so I'm willing to throw some ideas out here, or work on it with someone if they are interested. And if no-one is interested, I'll have a bash at a later date!
Any views/ideas welcome, 

Pebble

EDIT: Maybe add a tool tip to the PM page saying opening it will notify the sender? It could actually be done from the PM list page as well, so the need of doing it on page load wouldn't be an issue, I guess?
Just wondering if this against TOS, or has privacy issues etc.

[Todge]

This could feasibly be done using a Conversation Key, and yes, you could set the key when the member clicks on the thread to open it.

The only problem there is that you will need to add a delay into when the link was clicked on and when the page is actually changed to allow time for the key to be set, otherwise it will fail.

[Forever Sunshine]

Wasn't there a plugin done some time ago showing when a PM was read but it was pulled from the line up due to a violation of privacy concerns? I could be wrong but I thought I'd read that somewhere here.

[Former Member]

It was pulled due to ajax problems, not privacy.

[Forever Sunshine]

Oh, I stand corrected! But isn't privacy the reason they're giving on the support thread for not being able to have it? Maybe I misunderstood.

[Former Member]

For not having it as a permanent, proboards-standard feature. A lot of things that they will not have as a permanent feature have been made into plugins for those who want it, such as a dislike system. Though I'm sure staff will post here if they want any idea of this terminated, the one who made it before was staff himself.

[Forever Sunshine]

You're right, he is staff and I remember reading why it was pulled.

[Former Member]

I could be 100% wrong, trust me xD I'm hoping an admin will post to verify the true fact, since I'm going off previous examples I've witnessed and guesses.

[Wormopolis]

a decoy link could be substituted. set the conversation key on the decoy, and make the success function actually change the URL. make the conversation key an array type. on clicking the decoy, check the array for userid. if not in there, push userid, and on success change the URL. if already there, just change URL.

then when you want to check if PM has been read, simply check its key for userids. or, since you cant resolve user info from just an id, you could push objects onto the array that contain {id, name, username} so you can list them on a hover or something.

[Pebble]

Apr 17, 2014 16:41:52 GMT -8 Todge said:

This could feasibly be done using a Conversation Key, and yes, you could set the key when the member clicks on the thread to open it.

The only problem there is that you will need to add a delay into when the link was clicked on and when the page is actually changed to allow time for the key to be set, otherwise it will fail.

Apr 18, 2014 0:12:09 GMT -8 Wormopolis said:

a decoy link could be substituted. set the conversation key on the decoy, and make the success function actually change the URL. make the conversation key an array type. on clicking the decoy, check the array for userid. if not in there, push userid, and on success change the URL. if already there, just change URL.

then when you want to check if PM has been read, simply check its key for userids. or, since you cant resolve user info from just an id, you could push objects onto the array that contain {id, name, username} so you can list them on a hover or something.

This sounded very straight forward in my head! Thanks for the info guys.
A 'Coversation Key' ? I didn't know one even existed    I guess this will be a chance to check it out I was thinking of using a super user key....

Making a decoy button/link, delay's etc.....  Mmmm, it'll be something I haven't tried before so should be interesting. 
When I've made a start on this I'll post an editable version on here for others to get working/improve!  

Cheers,
Pebble.

[Todge]

Good luck.

[Pebble]

Well.... I eventually sat down to do this and waited for it to break so I could add delays and decoy keys etc.... and it didn't happen!
Now I've got this nagging doubt that I've missed something obvious! Is this to do with a specific browser and version?

Anyway, here's the plugin as I have it so far which seems to be working : www.dropbox.com/s/66lwjw5cuqtme2y/PM%20Read%282%29.pbp
Obviously not ready for general release ( no options for anything etc and the code needs a tidy up ). If I've missed something , could you let me know, or add some suggestions.
Cheers,
Pebble.

EDIT: Thought I'd add an image to show where it's showing, on the inbox/outbox pages.

[Pebble]

Now I've hit a problem....
It's all working and I have the key setting from the reply page (and everywhere else that it should be working), but the set_on doesn't seem to work when replying to a conversation from the quick reply.

From the notes about this:

thread_new - When a thread is created
post_new - When a post is made
post_quick_reply - When a post is made using the quick reply
conversation_new - When a conversation is created
message_new - When a reply to a conversation is made

It seems that we don't have a 'message_quick_reply' or 'conversation_quick_reply'.   Maybe this is what you were talking about earlier in the thread?

This is what I'm using , that works, from the reply page ( to a conversation ) but not from the quick reply.
pb.plugin.key('pmread').set_on('message_new', route.params.conversation_id,  newcurrentval );
 I also tried :
pb.plugin.key('pmread').set_on('post_quick_reply', route.params.conversation_id,  newcurrentval )
But no luck there.

I'll give Tim Camara a tag, in case he has any info as well.

Cheers,
Pebble.

Editable plugin here if it's any help : www.dropbox.com/s/66lwjw5cuqtme2y/PM%20Read%282%29.pbp

[Todge]

pb.plugin.key('pmread').set_on('post_quick_reply', route.params.conversation_id, newcurrentval ) will work, but you do not need to specify the conversation ID as it will be picked up automatically.

So..

pb.plugin.key('pmread').set_on('post_quick_reply', newcurrentval)

Should work.

[Pebble]

Apr 26, 2014 8:28:10 GMT -8 Todge said:

pb.plugin.key('pmread').set_on('post_quick_reply', route.params.conversation_id, newcurrentval ) will work, but you do not need to specify the conversation ID as it will be picked up automatically.

So..

pb.plugin.key('pmread').set_on('post_quick_reply', newcurrentval)

Should work.

Yep, I had it like that before I realised that it wasn't working from the quick reply. I just added in the id to make sure......
It works from the QR on a normal thread, but when in a conversation.... nothing

EDIT: I'll take another crack at it tomorrow with a clear head.