Well, wait for motorola's graphene compatible phones to pop up ig.
innocentz3r0
joined 8 months ago
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.
Thanks for the kind words! For dotfiles, I used org-babel for a long time, keeping a literate config. Now I use a git repo to hold everything with a script to pull in whatever I think is necessary. That said, one of the long term plans for supac is to add dotfile management as well, something like nix-wrapper does it. Although it will certainly take some time before we get there.
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
- Laptop: thinkpad E14
- OS: Btw
- WM: Niri
- Bar+notification daemon+launcher: ironbar + mako + vicinae
- editor+note taking: nvim + zk-cli
- terminal+shell+prompt: kitty + nushell + starship
Lockscreen is swaylock, which I haven't posted here. Everything is catpuccin themed :)
Ah yes, I came across this when someone else pointed it out as well. The project looks neat, ngl. supac also shares some goals along these lines, but dcli looks more mature. I still prefer supac (it's my project duh) because supac allows you to script in nushell, which lets you do interactive development (if you use nushell as your shell, which you absolutely should!). I also don't prefer something like YAML for config, but since it's extensible with lua, I guess it makes sense to go with a config language as well. I do think the end goals are different, I try to orient supac to be a nix alternative but with integrated package management across different package managers. Also, supac is simpler in principle because a lot of the complexity is shifted to accompanying libs in nushell (such as systemd unit integration).
Not to mention, with a couple of lines of nushell code you can probably import all your yaml configs from dcli into supac :)
I'd rather just use nix 🙃
Right now, you can do it in two ways:
- Don't have the Arch key at all. supac will silently skip it.
- You can write a small wrapper in package.nu that checks the presence of your preferred arch package manager in $env.PATH, if it's there then it'll insert the key and value, and not otherwise.
I'd mostly go with 1 unless you're sharing your non-arch config with an arch config on two separate machines.
Yep, it should cover you alright! I use all the 5 package managers mentioned here (hence the order :p). Scriptability and post hooks in particular make it even better (cloning/copying dots, activating systemd units, other stuff, etc).
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.
view more: next ›
It's custom ascii art. I got it from archwiki. You can change the image/text used in fastfetch config