3 ms·

> UX is entirely dependent on the client. Not entirely. Some features cannot be implemented without help from the protocol, like this extension to fetch histor

> UX is entirely dependent on the client. Not entirely. Some features cannot be implemented without help from the protocol, like this extension to fetch history: https://ircv3.net/specs/extensions/chathistory https://ircv3.net/specs/extensions/chathistory

BeefWellington 5y ago
IRC just operates differently than discord or slack do. In the olden days, people just had large log files for their IRC clients stored locally, understanding that disconnected time = time you weren't logging. A lot of existing IRC users would probably view the ability to fetch complete channel chat history as an anti-feature.
u801e 5y ago
Typically this was something that was handled locally by the client by logging messages sent to channels you were in. The concept of having all messages on a central server to pull down actually makes certain actions more difficult. For instance, pressing PgUp several times or just scrolling up to see what was said some time ago in Slack takes quite a bit of time because it has to pull down data from the server rather than relying on local storage. Same thing with using something like ctrl-f to find a certain phrase you saw in the channel some time ago. Slack, for example, requires you to go through several dialogs to formulate your search terms, and by default, returns results in channels you never were in, and won't filter them out until you select just the channels you want.
- progval 5y ago
  Yes of course. I meant this protocol extension is needed to get the history while disconnected from the network. And it can be fast enough to work smoothly with scroll/PgUp, I successfully did this with Gamja + https://github.com/progval/matrix2051 https://github.com/progval/matrix2051 + Synapse, it almost felt like the history was stored locally.

3 ms·

> UX is entirely dependent on the client. Not entirely. Some features cannot be implemented without help from the protocol, like this extension to fetch histor

by progval 5y ago

BeefWellington 5y ago
IRC just operates differently than discord or slack do. In the olden days, people just had large log files for their IRC clients stored locally, understanding that disconnected time = time you weren't logging. A lot of existing IRC users would probably view the ability to fetch complete channel chat history as an anti-feature.
u801e 5y ago
Typically this was something that was handled locally by the client by logging messages sent to channels you were in. The concept of having all messages on a central server to pull down actually makes certain actions more difficult. For instance, pressing PgUp several times or just scrolling up to see what was said some time ago in Slack takes quite a bit of time because it has to pull down data from the server rather than relying on local storage. Same thing with using something like ctrl-f to find a certain phrase you saw in the channel some time ago. Slack, for example, requires you to go through several dialogs to formulate your search terms, and by default, returns results in channels you never were in, and won't filter them out until you select just the channels you want.
- progval 5y ago
  Yes of course. I meant this protocol extension is needed to get the history while disconnected from the network. And it can be fast enough to work smoothly with scroll/PgUp, I successfully did this with Gamja + https://github.com/progval/matrix2051 https://github.com/progval/matrix2051 + Synapse, it almost felt like the history was stored locally.