-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improvement: recipient_id #87
Comments
parent_id is perhaps not a good field name as it would be misleading as if it was a channel ID. Perhaps to_message_id? |
Well, here are some thoughts/issues
Edit: Taking back that I am doing the @'s wrong. It appears that this isn't the case. Manually typing |
Another interesting detail, it appears that the displayed name in the comment does change when someone changes their name though it can take a few minutes for it to update for all @ references. I saw one reply as the new name and the others as the previous name until a few minutes went by. Then rename the account to Foo Bar |
I have submitted an issue feature request about this to Google to see if they can add the channel reference to the |
Thanks for posting the link to the Google request. |
Some background. There is a need to at least identify replies to replies. That need arises from the difference between notification of listeners in a comment thread. Because such a reply does not notify the original poster of the common parent message. Currently I use this SQL criterion as a hack: |
It's quite amazing what can be done with the database. Now I am looking at comments where the recipient is not the parent, the original poster, but another user in the same thread. Perhaps the YouTube API does not reveal that case except one has to take that from the @user Name prefix of the text. The best place to do this IMHO would be when importing into the database, especially in light of the fact that a user can change name while the ID remains the same.
To resolve this, the comments table would need an additional field, like recipient_id which would be the same as parent_id in case the comment is directed at the parent.
The text was updated successfully, but these errors were encountered: