Weechat for Android - remote client for the weechat IRC client. Best Android IRC experience I’ve found to date.
If you want even better Android IRC experience, you could try the new Quasseldroid beta https://quasseldroid.info/ (as soon as the new version is released it’ll also replace the current F-Droid entry) with the new quassel 0.13 (try it by compiling from git).
I would, but my quassel experience wasn’t that great ~1 year ago. Got really unstable and took several minutes to start the desktop client as I approached 400 buffers. Granted, this is a lot, and people have told me that using postgres for the backend can improve it, but I don’t really want to use postgres for my IRC bouncer and I’m accustomed to weechat and its own problems now :’)
That said, I used the old quasseldroid for a long time, and it was actually a life-saver when the desktop client kept crashing and I needed to read some old messages. Thanks for many years of IRC on the go!
Yeah that’s a real issue with SQLite, it really wasn’t designed for many separate threads writing and reading at the same time, causing timeouts. That said, with the recent versions, that issue should go away as now loading backlog is only really required for the buffers you actually open – which reduces the amount of data that has to be loaded on connection massively.
What’s the memory usage like with postgres? I might try it again at some point, seeing as weechat keeps eating all the RAM I can feed it (not much).
I’m still a bit unsure about the internals of quassel… for example recently I found out that it inexplicably sends NAMES for every channel it’s in quite regularly. When you’re in a few hundred that ends up being quite a lot of traffic, which is really unnecessary.
Edit: I just noticed that you edited your post to clarify about sqlite, all of this is sounding pretty good so far, maybe even good enough to tempt me back to the dark side — but certainly good enough to stop me warning people against using quassel nowadays :-)
A lot of people are using it successfully on systems as small as a raspberry pi. Personally I have been hosting a core for 5 people, some of which with 400+ channels (not buffers) on this: https://www.online.net/en/server-dedicated/start-2-s-sata
So performance is actually quite great, especially with more recent versions of the core.
for example recently I found out that it inexplicably sends NAMES for every channel it’s in quite regularly. When you’re in a few hundred that ends up being quite a lot of traffic, which is really unnecessary.
That’s done to update the away status, the modes, etc all correctly on servers that don’t yet support the IRCv3 extensions for doing this automatically. The 0.13 beta uses IRCv3 away-notify and IRCv3 account-notify for this, if available.
That’s done to update the away status, the modes, etc all correctly on servers that don’t yet support the IRCv3 extensions for doing this automatically. The 0.13 beta uses IRCv3 away-notify and IRCv3 account-notify for this, if available.
Oh fair enough then. Is there a way to turn this off?
Silence - (badly) encrypted SMS messages, I just use it because I like the UI
Afaik Silence is a fork of TextSecure and uses the Signal Protocol, just over SMS/MMS. So the encryption, authentication, and integrity properties it provides should be very good–not bad as you state. If you read the Signal blog post on why they stopped using SMS/MMS they list user experience, metadata leakage, and development overhead as the main problems.
Oh, I was under the impression they were using some different crypto because the messages produced by Signal would be too large, or something. I retract my statement :-)
If you want even better Android IRC experience, you could try the new Quasseldroid beta https://quasseldroid.info/ (as soon as the new version is released it’ll also replace the current F-Droid entry) with the new quassel 0.13 (try it by compiling from git).
The result looks something like https://i.k8r.eu/63U1pA and works quite nicely. The repo is at https://git.kuschku.de/justJanne/QuasselDroid-ng/ and beta builds are available on the Play Store or at https://s3.kuschku.de/releases/quasseldroid-ng/Quasseldroid-latest.apk (sadly I haven’t found a nice way to get beta builds onto F-Droid yet, but thanks to this thread I’m right now trying out a way to do so)
EDIT: An F-Droid binary repo of the latest beta releases is now available, its direct link (not usable in the browser) is https://repo.kuschku.de/repo?fingerprint=A0CBC2C29E38ED9542F86A1188412A60C5A756FC4D7A31C4C622242D7AD021F2
Disclaimer: I’m the dev.
I would, but my quassel experience wasn’t that great ~1 year ago. Got really unstable and took several minutes to start the desktop client as I approached 400 buffers. Granted, this is a lot, and people have told me that using postgres for the backend can improve it, but I don’t really want to use postgres for my IRC bouncer and I’m accustomed to weechat and its own problems now :’)
That said, I used the old quasseldroid for a long time, and it was actually a life-saver when the desktop client kept crashing and I needed to read some old messages. Thanks for many years of IRC on the go!
Yeah that’s a real issue with SQLite, it really wasn’t designed for many separate threads writing and reading at the same time, causing timeouts. That said, with the recent versions, that issue should go away as now loading backlog is only really required for the buffers you actually open – which reduces the amount of data that has to be loaded on connection massively.
Still great that you liked it :)
What’s the memory usage like with postgres? I might try it again at some point, seeing as weechat keeps eating all the RAM I can feed it (not much).
I’m still a bit unsure about the internals of quassel… for example recently I found out that it inexplicably sends NAMES for every channel it’s in quite regularly. When you’re in a few hundred that ends up being quite a lot of traffic, which is really unnecessary.
Edit: I just noticed that you edited your post to clarify about sqlite, all of this is sounding pretty good so far, maybe even good enough to tempt me back to the dark side — but certainly good enough to stop me warning people against using quassel nowadays :-)
A lot of people are using it successfully on systems as small as a raspberry pi. Personally I have been hosting a core for 5 people, some of which with 400+ channels (not buffers) on this: https://www.online.net/en/server-dedicated/start-2-s-sata
So performance is actually quite great, especially with more recent versions of the core.
That’s done to update the away status, the modes, etc all correctly on servers that don’t yet support the IRCv3 extensions for doing this automatically. The 0.13 beta uses IRCv3 away-notify and IRCv3 account-notify for this, if available.
Oh fair enough then. Is there a way to turn this off?
Of course! https://i.k8r.eu/57bw_A
Afaik Silence is a fork of TextSecure and uses the Signal Protocol, just over SMS/MMS. So the encryption, authentication, and integrity properties it provides should be very good–not bad as you state. If you read the Signal blog post on why they stopped using SMS/MMS they list user experience, metadata leakage, and development overhead as the main problems.
Oh, I was under the impression they were using some different crypto because the messages produced by Signal would be too large, or something. I retract my statement :-)