Dec 31, 2018, 5:37 pm
Last edit by: tcook052
This new annual thread has been carved out of the previous thread in an effort to reduce the number of megathreads on the AC forum. For those interested previous versions are the original 2004 - 2014 thread , 2015 edition, 2016 edition , 2017 edition and 2018 edition.
The original thread started by accident but quickly became a popular place to come and discuss off topic things such as hockey, new movies, or almost anything that wouldn't fit into existing AC forum threads. Air Canada or Aeroplan topics such as flight feedback, in-flight services issues, status or mileage earning/redemption are all topics that should go into existing AC forum threads so others can benefit from this information. Topics about hotels or airlines and/or their loyalty programs, destinations, in-flight travel tech. or anything best discussed elsewhere on FT may be relocated to that forum as this thread isn't meant to import travel topics to this forum that are better discussed on other forums. FT is an amazingly diverse and large community so members are encouraged to seek out all of its resources.
While the conversation is more relaxed as it would be in a lounge that doesn't mean however that the FT rules don't apply here as they definitely do so please refrain from controversial topics such as politics or religion, avoid profanities and treat other lounge patrons with the same respect you expect.
tcook052
Air Canada forum moderator
The original thread started by accident but quickly became a popular place to come and discuss off topic things such as hockey, new movies, or almost anything that wouldn't fit into existing AC forum threads. Air Canada or Aeroplan topics such as flight feedback, in-flight services issues, status or mileage earning/redemption are all topics that should go into existing AC forum threads so others can benefit from this information. Topics about hotels or airlines and/or their loyalty programs, destinations, in-flight travel tech. or anything best discussed elsewhere on FT may be relocated to that forum as this thread isn't meant to import travel topics to this forum that are better discussed on other forums. FT is an amazingly diverse and large community so members are encouraged to seek out all of its resources.
While the conversation is more relaxed as it would be in a lounge that doesn't mean however that the FT rules don't apply here as they definitely do so please refrain from controversial topics such as politics or religion, avoid profanities and treat other lounge patrons with the same respect you expect.
tcook052
Air Canada forum moderator
The Forum Lounge Thread (2019)
Nov 1, 2019, 5:01 am
#1997
Join Date: Apr 2016
Location: YHZ/YQM
Programs: Aeroplan
Posts: 1,618
A sad (for me) statement from my son just now about Halloween.
"I used to just give all of my KitKats to Dad, but now I trade them with my friends."
"I used to just give all of my KitKats to Dad, but now I trade them with my friends."
Nov 1, 2019, 10:07 am
#1999
Join Date: Apr 2016
Location: YYZ
Programs: TK *G
Posts: 3,099
This may be a long shot, but I will still give it a try, as they are many smart people on FT 
We currently have a messaging feature in our app. Users can join different channels to view messages, users can also get push notifications by muting/unmuting a channel. We use a channel_participant table to store these settings, and mark the last read message. One record in the table stores a user's status and settings in a specific channel.
We now want to introduce a thread feature. A user can start a thread on an existing message. An easy solution is to treat every thread as a channel, copy the entries in the channel_participant table, and change the channel_id from the parent channel to the new thread. This works, but now we have one record for each user in each channel and each thread in channel_participant table. My gut is telling me I don't need to create these many records. I can derive the user's subscription to threads based on user's subscription to the parent channel, but it won't work for recording the last read message in a thread, or if a user want to mute a thread but not the whole channel.
So, am I missing something?
We currently have a messaging feature in our app. Users can join different channels to view messages, users can also get push notifications by muting/unmuting a channel. We use a channel_participant table to store these settings, and mark the last read message. One record in the table stores a user's status and settings in a specific channel.
We now want to introduce a thread feature. A user can start a thread on an existing message. An easy solution is to treat every thread as a channel, copy the entries in the channel_participant table, and change the channel_id from the parent channel to the new thread. This works, but now we have one record for each user in each channel and each thread in channel_participant table. My gut is telling me I don't need to create these many records. I can derive the user's subscription to threads based on user's subscription to the parent channel, but it won't work for recording the last read message in a thread, or if a user want to mute a thread but not the whole channel.
So, am I missing something?
Nov 1, 2019, 10:17 am
#2000
Join Date: Sep 2011
Location: Ideally YOW, but probably not
Programs: AC SE*MM
Posts: 1,828
Nov 1, 2019, 10:25 am
#2001
Join Date: Apr 2016
Location: YYZ
Programs: TK *G
Posts: 3,099
so thanks.I don't recall how many times I wanted to write the entire code base from scratch lol
Nov 1, 2019, 10:29 am
#2002
Join Date: Aug 2013
Location: YVR - MILLS Waypoint (It's the third house on the left)
Programs: AC*SE100K, wood level status in various other programs
Posts: 6,238
Of course I'm mostly evil. Although I was careful last night not to hand out the cups of mulled wine to anyone under 18.
Nov 1, 2019, 12:28 pm
#2005
Suspended
Join Date: Sep 2014
Programs: AC SE100K-1MM, NH, DL, AA, BA, Global Entry/Nexus, APEC..
Posts: 18,877
Nov 1, 2019, 3:41 pm
#2006
Join Date: Jan 2017
Location: Halifax
Programs: AC SE100K, Marriott Lifetime Platinum Elite. NEXUS
Posts: 4,574
This may be a long shot, but I will still give it a try, as they are many smart people on FT
We currently have a messaging feature in our app. Users can join different channels to view messages, users can also get push notifications by muting/unmuting a channel. We use a channel_participant table to store these settings, and mark the last read message. One record in the table stores a user's status and settings in a specific channel.
We now want to introduce a thread feature. A user can start a thread on an existing message. An easy solution is to treat every thread as a channel, copy the entries in the channel_participant table, and change the channel_id from the parent channel to the new thread. This works, but now we have one record for each user in each channel and each thread in channel_participant table. My gut is telling me I don't need to create these many records. I can derive the user's subscription to threads based on user's subscription to the parent channel, but it won't work for recording the last read message in a thread, or if a user want to mute a thread but not the whole channel.
So, am I missing something?
We currently have a messaging feature in our app. Users can join different channels to view messages, users can also get push notifications by muting/unmuting a channel. We use a channel_participant table to store these settings, and mark the last read message. One record in the table stores a user's status and settings in a specific channel.
We now want to introduce a thread feature. A user can start a thread on an existing message. An easy solution is to treat every thread as a channel, copy the entries in the channel_participant table, and change the channel_id from the parent channel to the new thread. This works, but now we have one record for each user in each channel and each thread in channel_participant table. My gut is telling me I don't need to create these many records. I can derive the user's subscription to threads based on user's subscription to the parent channel, but it won't work for recording the last read message in a thread, or if a user want to mute a thread but not the whole channel.
So, am I missing something?
Syncing channels (chat channels and threads) between login sessions still needs to be done, but you've either already done that or don't care.
Nov 1, 2019, 4:32 pm
#2007
Join Date: Nov 2018
Programs: AC 50K
Posts: 199
On a related note, very happy to show up to work last night and the boss had a giant box of mini kit kats...which were then piled on my desk. Sometimes working Halloween has it's benefits!!
Nov 4, 2019, 6:59 pm
#2008
Join Date: Jun 2018
Location: YVR
Programs: AC SE100K, Bonvoy Platinum Elite, IHG Gold, Hertz 5*
Posts: 2,132
If you haven't watched Succession you're doing television all wrong.
Nov 4, 2019, 8:17 pm
#2009
Join Date: Jan 2016
Location: YYZ
Programs: Only J via Peasant Points, 777HDPeasant or The Unexpected Virtue of Ignorance and Narcissism.
Posts: 5,961
Nov 5, 2019, 12:51 am
#2010
FlyerTalk Evangelist
Join Date: Feb 2004
Location: YVR
Programs: AC SE 2MM; UA MP Premier Silver; Marriott Bonvoy LT Titanium Elite; Radisson; Avis PC
Posts: 35,255
IMHO, Marchand is even more annoying than Barnaby ever was.