Well, wait for motorola's graphene compatible phones to pop up ig.
Molly basically is a fork of the signal client that switches out some notification based things (such as your notifications going through fcm and such) and instead lets you use unifiedpush and/or a molly websocket. Apart from this they're both the same. Molly uses signal's codebase.
The clients for XMPP are really bad. Also, matrix sells itself in a variety of ways, discord alternative, corporate usability, e2ee signal replacement, all that. Although matrix client implementations aren't that great, the publicity does work. And IRC has historic relevance.
Thank you!
Agreed, and the dev is an amazing guy! Yalter makes sure that every feature is well thought out and laid best according to the specs.
My daily driver for home and college, where I write most of my code
Lockscreen is swaylock, which I haven’t posted here. Everything is catpuccin-macchiato
EDIT: Forgot to add, that hexdump like thingy is my WIP website
My daily driver for home and college, where I write most of my code
Lockscreen is swaylock, which I haven't posted here. Everything is catpuccin themed :)
EDIT: Forgot to add, that hexdump like thingy is my WIP website
Right now, you can do it in two ways:
I'd mostly go with 1 unless you're sharing your non-arch config with an arch config on two separate machines.
Haha, fair enough. The reason I even created this in the first place was because of how painful nix/nixOS is to use in general. Nushell is far simpler, and much more ergonomic to deal with. Especially with how much it supports structured data.
Dcli looks interesting! The long term goal of supac is to support many different relevant package managers as backends, so that all sorts of packages and language toolchains can be managed. Besides, nushell being a scripting AND shell language massively helps with that.
From what I understand (I've never used mise), mise is meant for programming environments and tools. Supac works with your distribution's package manager to manage all your system packages and also language toolchains like rustup and uvx (uvx backend doesn't manage toolchains yet, it's being developed though).
What it doesn't manage are programming environments, basically, you cannot use it to spawn something like a nix devshell. Hope it makes sense. This is more meant to be along the lines of something like nix, but friendlier and easier.
I'd be surprised if the majority of folks on arch aren't using tiling WMs.