Is anyone interested in starting a new adaptive GTK Rust client for Signal for Linux smartphones and desktops? I wrote a post on the @PINE64 forum about my reasoning for this technical approach:
*Do not respond to this with criticism of Signal*. If you're annoying about that, I'll block you.
@fla @r3pek @PINE64 @chiraag For push notifications, I think the best approach would be implementing a Linux daemon for receiving Firebase Cloud Messaging with a dbus API to communicate with applications. This would not require the Signal Foundation to do any extra work on their end. Plus it could be used for other applications like WhatsApp, Facebook Messenger, Slack, Zulip, and other Android applications.
FYI @be, there already exists a RPG engine named #Flare (Free/Libre Action Roleplaying Engine), whose executable is flare (in Debian there's a metapackage named flare as well but that's something solvable): https://flarerpg.org
Flare is the first and only RPG I've ever finished (four times, counting one for the alpha campaign) and its gameplay is my absolute favorite, even compared to that of AAA games. Written on SDL2, it works just fine on the #PinePhone and touch input is WIP.
@mcsinyx I don't know if there's any common English word that isn't already used for *some* application...
Unfortunately no, @be, sorry. I don't use Signal to understand it and think of a pun for it to keep our tradition, and I suspect all related names are already taken.
@mcsinyx By the way, "Flare" was not my idea. It was suggested on Reddit and got a ton of upvotes so I went with it. https://www.reddit.com/r/linux/comments/mp2j0j/starting_a_native_adaptive_linux_client_for_signal/gu7cze6/?context=3
The Reddit thread reminds me of Giara, @be. If you're into recursive ancronyms, any four-letter word ending with either -isc (is a Signal client) or -isa (is a Signal app) might be a good idea.
@fla @r3pek @PINE64 @chiraag @kde Update: After reaching out to the Whisperfish developers, I've decided the best path forward for a native mobile Linux Signal client is to help Whisperfish decouple from Sailfish OS and implement a new Plasma Mobile GUI with Kirigami: https://gitlab.com/rubdos/whisperfish/-/issues/318
@fla @r3pek @PINE64 @chiraag @kde @marcozehe I see you commented on an old issue about accessibility with the Electron Signal client. If you're interested in helping us make the new Kirigami GUI accessible, that would be much appreciated! There's quite a bit of preliminary work to do before we'd be ready to test that.
@r3pek @be @fla @PINE64 @chiraag @kde Aha. What toolkit do you wanna use? KDE has mixed accessibility, only slowly getting there on Linux, QT seems to work somewhat OK on Windows, I think, and I don't even know the Mac story of QT a11y, e.g. their support of the NSAccessibility protocol of AppKit, which is an absolute requirement for Mac. If you plan to use GTK, Linux will be the only platform this will be accessible AFAIK.
@marcozehe @r3pek @fla @PINE64 @chiraag @kde The plan is to adapt Whisperfish to use KDE's Qt libraries. Currently it only runs on Sailfish with Jolla's proprietary Qt libraries. Once we have it working on Linux, I think it wouldn't be too hard to build it on Windows and macOS too, but our priority is getting it working on Linux.
@be @fla @r3pek @PINE64 @chiraag @kde Besides, with tthat recent stance by Signal with that UK Bitcoin thing, I am actually not sure I could get behind anything supporting Signal any more. Also with regards to the fact that their server code seems to no longer be open source in its current form, only in a very outdated version.
@gamey @be The question is: do they want to do it? In most cases alternative clients/fronts provide enhanced experience for use cases that aren't interesting enough for an original service to support. Thus, that could decrease churn rate for the service. However, in case they decide an alternative is unwanted they basically are in charge of their service and free to pursue blocking an alternative in any way including a legal one.
@lig To add a big example case to the mix Oracle just lost the about a decate old fight against Google. I assume you know the case but in short Oracle claimed ownership of the Java API Google implemented to Android and asked for money because of that. There even is the Java trademark in that code but that currently doesn't seem to be enough to claim ownership (At least in the US)
@gamey That's different. No one can stop you from using the same APIs as Signal uses. However, that doesn't mean you can use their service in whatever way you like.
@lig Yea exactly but that means they would have to proof API abuse by the client to go against it legally.
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.