Proposed Channel changes and #recent
Posted 18 September 2017 - 11:58 AM
* Enhance #JC so that it implies #recent for channels that are supported by #recent
* Enhance the @@3 & @@guild type syntax ([email protected]@<channel> ) to imply a #jc <channel> if you aren't already in that channel and you have a free channel available (which may also imply a #recent)
* Do NOT imply a #recent when you login to prevent login lag.
Currently #recent works for server messages and channels bellow 1000 and may be extended to guild channels as changes for PremiumGuilds are added. When you aren't in a channel, that channel information isn't sent to the client to reduce the client chatter/data (which can be important to people with slow or laggy connections).
This enhancement gives you control and can help you get caught up when you going a channel but still leaves the option of using #recent on demand for existing channel. #recent would only work in limited channels and expanding it into the guild channel would be discussed when enhancing guilds. A benefit to #recent when you join or on demand later, is that burst of traffic can be compressed in OL to make it smaller, and you have control of when it happen since it only happens when you join a channel or request it.
There is no attempt to automatically remove you from a channel. If all your channels are in use already and you aren't in 3, @@3 would fail.
These thoughts are attempts to improve how channels work without major revamps, avoiding client changes, and attempting to reducing lag all combined into a 'simple' step.
Posted 18 September 2017 - 12:05 PM
Posted 18 September 2017 - 12:30 PM
Posted 18 September 2017 - 12:40 PM
Posted 18 September 2017 - 12:45 PM
Posted 19 September 2017 - 12:01 PM
Posted 20 September 2017 - 10:45 AM
Posted 29 September 2017 - 08:43 AM
Posted 29 September 2017 - 08:47 AM
Sorry, don't do novels when answering posts
Posted Yesterday, 08:33 AM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users