Ripcord Development: View Ticket

Ticket UUID:	157bb8fbf16c79b0d18d937d5a8082af9bc61a95
Title:	Mentions panel will cause Ripcord to request the wrong "earliest post seen" from Discord
Status:	Closed	Type:	Bug
Severity:	Minor	Priority:	Low
Subsystem:	Discord	Resolution:	Fixed
Last Modified:	2020-12-25 14:10:26
Version Found In:	0.4.26
silverbacknet — 2020-10-29 17:04:50 My Ripcord.log goes like this: `.... 2020-10-29 09:39:47.793 Debug Networking: GET to Discord API at https://discord.com/api/v6/users/@me/mentions?limit=100&roles=true&everyone=true .... 2020-10-29 09:39:53.683 Debug Networking: GET to Discord API at https://discord.com/api/v6/channels/766475228498624533/messages?limit=100 .... 2020-10-29 09:39:56.200 Debug Networking: GET to Discord API at https://discord.com/api/v6/channels/766475228498624533/messages?limit=100&before=770409645352419348 ....` The problem is that the snowflake is the last one returned in that channel for the mentions request, 770409645352419348 (timestamp 1603750372971), not the channels request. The snowflake for the last message ID of the 100 messages returned is 771390092324896778 (timestamp 1603984129745), which results in several days of missing messages in the channel, since I'm mentioned regularly. Since it's cached for the remainder of the sessions, I have to close and reopen Ripcord with the mentions panel closed to avoid that.
cancel — 2020-10-30 13:57:10 Yup. Needs to be fixed. This only affects Discord, not Slack. Related: 75d72ad7b8
cancel — 2020-12-20 14:16:32 Fixed in next release