idea--persistent-chat-client 1.1 KB

1234567891011121314151617181920212223242526
  1. id: 'idea--persistent-chat-client'
  2. content: |
  3. One could (to easily work with existing chat services) write a
  4. secondary, personal server. This would act as a meta-client,
  5. actually being responsible for talking to other chat services,
  6. keeping secondary logs of that content and maybe scraping it
  7. for image links &c.
  8. It would then open a (protected) connection to some other kind
  9. of chat client, either over an existing chat protocol or using a
  10. new secured protocol. If no connections are currently active, then
  11. it would set the relevant presence to 'offline', whereas if one
  12. or more clients are connected, it will transparently allow any
  13. or all of them to communicate.
  14. (This is in sharp contrast to typical Jabber implementations,
  15. which always designate a particular connection as 'active'.)
  16. It could also send the last dozen (or so) messages send and
  17. received to the client, so that switching client in
  18. mid-conversation will still keep the user in the loop.
  19. (Needs a name: ĝi eble povas esti nomita en esperanto?)
  20. related:
  21. - name: idea--persistent-chat-client-diagram
  22. why: a more visual explanation