Revision history [back]

I have been brooding over this idea for quite a while now and I'm still not sure if it's just me that thinks having a

Multi Protocol Chat Client

supplementing the existing chat applications on Saifish would be a good idea.

After all, the very essence of any of these chat applications is to exchange chat messages, send/receive photos, arbitrary files and sometimes also voice messages or real-time voice/video streams.

I don't really see anything that would require every single protocol to have a dedicate app on SFOS. This could furthermore even free developers from having to reinvent the (UI) wheel over and over again every time a new protocol comes around.

e.g. I already have a few protocol daemons here which I mostly use from the command line:

• Telegram
• Threema
• IMAP/SMTP
• Matrix
• XMPP

All it would take to make them work on SFOS would be to create a common meta-protocol to tie together the actual protocol bits and the UI part (e.g. simple JSON sent back and forth over stdin) and to wrap a nice GUI around all of this.

But before I start wasting my time developing something no one really ever asked for I would like to make sure there is some actual demand for such an extravagance.

I have been brooding over this idea for quite a while now and I'm still not sure if it's just me that thinks having a

Multi Protocol Chat Client

supplementing the existing chat applications on Saifish would be a good idea.

After all, the very essence of any of these chat applications is to exchange chat messages, send/receive photos, arbitrary files and sometimes also voice messages or real-time voice/video streams.

I don't really see anything that would require every single protocol to have a dedicate dedicated app on SFOS. This could furthermore even free developers from having to reinvent the (UI) wheel over and over again every time a new protocol comes around.

e.g. I already have a few protocol daemons here which I mostly use from the command line:

• Telegram
• Threema
• IMAP/SMTP
• Matrix
• XMPP

All it would take to make them work on SFOS would be to create a common meta-protocol to tie together the actual protocol bits and the UI part (e.g. simple JSON sent back and forth over stdin) and to wrap a nice GUI around all of this.

But before I start wasting my time developing something no one really ever asked for I would like to make sure there is some actual demand for such an extravagance.

I have been brooding over this idea for quite a while now and I'm still not sure if it's just me that thinks having a

Multi Protocol Chat Client

supplementing the existing chat applications on Saifish would be a good idea.

After all, the very essence of any of these chat applications is to exchange chat messages, send/receive photos, arbitrary files and sometimes also voice messages or real-time voice/video streams.

I don't really see anything that would require every single protocol to have a dedicated app on SFOS. This could furthermore even free developers from having to reinvent the (UI) wheel over and over again every time a new protocol comes around.

e.g. I already have a few protocol daemons here which I mostly use from the command line:

• Telegram
• Threema
• IMAP/SMTP
• Matrix
• XMPP

All it would take to make them work on SFOS would be to create a common meta-protocol to tie together the actual protocol bits and the UI part (e.g. simple JSON sent back and forth over stdin) and to wrap a nice GUI around all of this.

But before I start wasting my time developing something no one really ever asked for I would like to make sure there is some actual demand for such an extravagance.

I have been brooding over this idea for quite a while now and I'm still not sure if it's just me that thinks having a

Multi Protocol Chat Client

supplementing the existing chat applications on Saifish would be a good idea.

After all, the very essence of any of these chat applications is to exchange chat messages, send/receive photos, arbitrary files and sometimes also voice messages or real-time voice/video streams.

I don't really see anything that would require every single protocol to have a dedicated app on SFOS. This could furthermore even free developers from having to reinvent the (UI) wheel over and over again every time a new protocol comes around.

e.g. I already have a few protocol daemons here which I mostly use from the command line:

• Telegram
• Threema
• IMAP/SMTP
• Matrix
• XMPP

All it would take to make them work on SFOS would be to create a common meta-protocol to tie together the actual protocol bits and the UI part (e.g. simple JSON sent back and forth over stdin) and to wrap a nice GUI around all of this.

But before I start wasting my time developing something no one really ever asked for I would like to make sure there is some actual demand for such an extravagance.

Please leave a vote should you be interested in a Multi Protocol Chat app for SFOS.

PS: And yes, I know it's basically what Jolla have tried with Telepathy but I don't mean trying to revive a dead horse.

I have been brooding over this idea for quite a while now and I'm still not sure if it's just me that thinks having a

Multi Protocol Chat Client

supplementing the existing chat applications on Saifish would be a good idea.

After all, the very essence of any of these chat applications is to exchange chat messages, send/receive photos, arbitrary files and sometimes also voice messages or real-time voice/video streams.

I don't really see anything that would require every single protocol to have a dedicated app on SFOS. This could furthermore even free developers from having to reinvent the (UI) wheel over and over again every time a new protocol comes around.

e.g. I already have a few protocol daemons here which I mostly use from the command line:

• Telegram
• Threema
• IMAP/SMTP
• Matrix
• XMPP

All it would take to make them work on SFOS would be to create a common meta-protocol to tie together the actual protocol bits and the UI part (e.g. simple JSON sent back and forth over stdin) and to wrap a nice GUI around all of this.

But before I start wasting my time developing something no one really ever asked for I would like to make sure there is some actual demand for such an extravagance.

Please leave a vote should you be interested in a Multi Protocol Chat app for SFOS.

PS: And yes, I know it's basically what Jolla have tried with Telepathy but I don't mean trying to revive a dead horse.years ago.

I have been brooding over this idea for quite a while now and I'm still not sure if it's just me that thinks having a

Multi Protocol Chat Client

supplementing the existing chat applications on Saifish would be a good idea.

After all, the very essence of any of these chat applications is to exchange chat messages, send/receive photos, arbitrary files and sometimes also voice messages or real-time voice/video streams.

I don't really see anything that would require every single protocol to have a dedicated app on SFOS. This could furthermore even free developers from having to reinvent the (UI) wheel over and over again every time a new protocol comes around.

e.g. I already have a few protocol daemons here which I mostly use from the command line:

• Telegram
• Threema
• IMAP/SMTP
• Matrix
• XMPP

All it would take to make them work on SFOS would be to create a common meta-protocol to tie together the actual protocol bits and the UI part (e.g. simple JSON sent back and forth over stdin) and to wrap a nice GUI around all of this.

But before I start wasting my time developing something no one really ever asked for I would like to make sure there is some actual demand for such an extravagance.

Please leave a vote should you be interested in a Multi Protocol Chat app for SFOS.

PS: And yes, I know it's basically what Jolla have tried with Telepathy years ago.ago but, in contrast to this, this project is meant to be a stand alone app.