axolotl
gccrs
axolotl | gccrs | |
---|---|---|
21 | 102 | |
319 | 2,289 | |
- | 1.1% | |
8.9 | 10.0 | |
12 days ago | 5 days ago | |
Rust | C++ | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
axolotl
-
Is anyone really using this?
While searching around a bit more I found another unofficial Signal client for arm64 Linux optimized for mobile called Axolotl. The github page makes it look promising, but once installed I couldn't log in successfully. I intend to put more effort in there. Axolotl appears to be the most promising looking option for Signal on mobile Linux - assuming it works..
- Axolotl.chat - First cross-platform Signal client
-
Axolotl: First cross-plattform Signal client
> Only a small thing, but due to Signals strict phone-desktop pairing mechanism, when registering Axolotl, both phone and regular Desktop wont work anymore.
> Also, you cant use Axolotl on Desktop together with Signal mobile.
> After deleting the Axolotl registration I had to wait a while to be able to register on Signal again, I didnt loose any backups and my codes didnt change.
> Nonetheless a warning should be displayed at the beginning, that users wanting to use regular mobile (iOS, Android) and Desktop (Windows, macOS, Flatpak or Snap), they should use a second phone number for testing.
https://github.com/nanu-c/axolotl/issues/811
-
Why Not Signal?
>Signal also notably isn't self-hostable: there's no way to run your own signal server, and control your data. Marlinspike ruthlessly shuts down anyone attempting to build alternate clients or servers that could communicate with the main one.
That is perfectly wrong. As a maintainer of https://axolotl.chat, a third-party signal client initially built for Ubuntu Touch but which runs on almost everything now, I can tell you that our client is speaking without any problems to the official Signal servers, and also that the code of the server is available and is running fine, we used it to test our code.
-
Stories Are Coming to Signal
Wouldn't Signal Desktop be a way to make backups?
I moved my home directory to a new computer and Signal Desktop started like if something changed. Sure you lose your messages on your phone, but you can still access them on your computer if needed.
On a rooted Android phone, you could use oandbackup to backup Signal. If you care about these things, maybe consider using a rooted Android phone?
I agree with you on the centralized platform aspect and the use of phone number (which is both a blessing (this makes it easy for new users to join) and a curse). I also agree with you on Element's UX, but it's getting better and most people can use it fine. I have a few groups on both apps.
I personally prefer Element, which seems more open than Signal and which I can actually use correctly on the PinePhone. Axolotl [1] still needs some work.
[1] https://github.com/nanu-c/axolotl
- Signal experiences on any of the Linux-based phones
-
PureOS - a pure Linux phone experience
I think the best option to communicate through Signal will be Axolotl. Because the original desktop client of Signal might work as well but it's not optimized for touch input.
-
I just bought a PinePhone
If you go to the git repo for Axolotl (https://github.com/nanu-c/axolotl), you will see links to the deb among other formats.
-
starting a native adaptive Linux client for Signal
Ah well then I applaud you. :) Perhaps some ideas could come from past efforts like Axolotl, which I've had working in a basic way in the past.
gccrs
-
FreeBSD evaluating Rust's adoption into base system
There is a Rust front-end for GCC that is under active development [1]. If the chip vendors are not willing to develop and upstream a LLVM back-end then they can feel free to start contributing to it.
[1] https://rust-gcc.github.io/
-
Why do lifetimes need to be leaky?
That's why gccrs doesn't even consider lifetime checking a part of the language (they plan to use Polonius, too).
- Rust-GCC: GCC Front-End for Rust
-
How hard would it be to port the Rust toolchain to a new non-POSIX OS written in Rust and get it to host its own development? What would that process entail?
There's ongoing work on a Rust front-end for GCC (https://github.com/Rust-GCC/gccrs). Bit barebones right now -- ie, even core doesn't compile -- but there's funding, demand, and regular progress, so it'll only get better from there. Once gccrs can compile core, it should be ready to compile most of Rust, and thus if you've taught the calling conventions for C to GCC, you're golden.
-
How hard is it to write a front end for a more complex language like Rust or Kotlin?
I recommend checking out the GCC Rust frontend project.
-
Rust contributions for Linux 6.4 are finally merged upstream!
That is what theyre refering to, yes. The GitHub is named https://github.com/Rust-GCC/gccrs
-
GCC 13 and the State of Gccrs
- But this misses so much extra context information
3. Macro invocations there are really subtle rules on how you treat macro invocations such as this which is not documented at all https://github.com/Rust-GCC/gccrs/blob/master/gcc/rust/expan...
Some day I personally want to write a blog post about how complicated and under spec'd Rust is, then write one about the stuff i do like it such as iterators being part of libcore so i don't need reactive extensions.
- Break rust Easter Egg Merged Into gccrs
-
Any alternate Rust compilers?
(Speaking of which, Rust-GCC (or gcc-rs or gccrs or whichever other of their names they decide is the primary one) isn't even going to be a complete C++ implementation. Their plan is to implement enough to compile Polonius (the NLL 2.0 borrow checker being developed in Rust for rustc) and then share that since borrow-checking isn't necessary for codegen... only to identify and reject invalid programs... making the C++ portion of it not that different in scope from mrustc.)
-
Which programming languages, if all legacy code written in them was ported to a more modern language, would become extinct?
That bridge will be crossed with gccrs (compiling Rust with gcc directly, coming next month with GCC 13) and rust_codegen_gcc (rustc frontend, GCC backend, works now but just doesn’t yet have an “easy” setup)
What are some alternatives?
Signal-Desktop - A private messenger for Windows, macOS, and Linux.
gcc-rust - a (WIP) Rust frontend for gcc / a gcc backend for rustc
signal-cli - signal-cli provides an unofficial commandline, JSON-RPC and dbus interface for the Signal messenger.
rustc_codegen_gcc - libgccjit AOT codegen for rustc
libsignal - Home to the Signal Protocol as well as other cryptographic primitives which make Signal possible.
rustc_codegen_gcc - libgccjit AOT codegen for rustc
GrapheneOS-Knowledge - This is a short description of some of the knowledge I've collected on GrapheneOS and some common questions I've been asked and my answers to them.
mold - Mold: A Modern Linker 🦠
signald
rust - Empowering everyone to build reliable and efficient software.
nheko - Desktop client for Matrix using Qt and C++20.
Rust-for-Linux - Adding support for the Rust language to the Linux kernel.