kixik

which one is it? The replies were erased, :(

Jami with unifiedPush notifications is a pretty good option

Wofi is still working fine with wayfire. It's actually still offered on Arch as part of the "extra" repository:

% pacman -Ss wofi
extra/wofi 1.3-2 [installed]
    launcher for wlroots-based wayland compositors

To be honest, I found it more straight forward than rofi, but I could still use rofi if it worked well on wayland. I've never used tofi, and it doesn't seem like a drop-in replacement for wofi. But I guess it's worth trying. It's seems less graphical than wofi though...

These two posts are really enlightening:

How I Built My New Linux Gaming Desktop In 2021 With Amd Cpugpu And Gnu Guix

I Love Arch But Gnu Guix Is My New Distro

From the last, there is a non guix project including packages for guix, which are not officially supported given hey are not free software. I recommend taking a look at the last post at least, since it comes from someone who used Arch, and made the move to Guix, not just opinions from people like me, who haven't ever used Guix.

That said, Guix is in my TODO list. The thing is that I want to learn a bit more than minimal Guile, so I can write packages myself (there are always missing packages, even on Arch/Artix + AUR, I always have the need to whether tweak something at some point, or create a package still not in there), and also deal with my own services to run with shepherd. So I don't want to blindly try things out...

It shares with Nix the reproducible build of everything, but the language it uses is Guile, which has some history. Nix has its own language. To me that's a plus on Guix. But the most important part, is that the official repos are all for free software, and then on the non guix project one can look for non free software pieces, which to me this is also a plus. I guest most might differ.

But again, if you want to try it, even if it's just because of curiosity, why not doing it so? I hope those prior posts from someone who migrated there might be helpful.

Why not looking for distributed mechanism, which don't depend on trusting central servers or particular instances on decentralized mechanisms, like jami, or similar?

Pff, I just got logged out on a refresh, hehe. So what I said is not true, I'm getting logged out, somehow randomly (can't say I know under which conditions that happens). Not sure if there was a release candidate upgrade, since I can't remember the version before this new logout. Currently:

UI: 0.19.0-rc.11
BE: 0.19.0-rc.10

Nope, I only have a lemmy.ml account, and I only use librewolf on the desktop...

I had that issue of having to re-login, and then every now and then when I do reload, it posts not on my subscribed communities as if I were not logged in, although I'm logged in, but on a subsequent reload, then only my subscribed communities posts show up. I haven't had to re-login again, just after the upgrade, and then the other minor annoyance is that, but a subsequent reload is enough...

Thanks !

Is it normal that on an upgrade, users are forced to re-login?

I don't think so. Dhcpcd + wpa_supplicant is really light, suitable for light installers, and live USB stick images.

I've been using dhcpcd + wpa_supplicant for so long... I do understand currently users prefer NM, but I hope there's no push for it to be the unique way to manage network connectivity, and on light installers, I hope I'm not force to use NM either.

very few, and one has to try so many times... I gave up. I guess RSS feeds whenever possible. though that consumes disk if local, so I'm really reluctant...

That has never been true, not at the point of the discussions on Debian (on Arch there was never a public discussion that I remember), and of of course not true now.

s6, dinit, runit, openrc and shephered are good options, currently in use by different distros. At the time of the public debian descussions, at least runit and openrc were available, but they were dismissed, and I don't remember the arguments, but not so convincing at the time, thus the whole discussion about the topic.

I'm not a systemd opponent, but claims of not having compelling alternatives doesn't feel right. I used Arch with systemd for a while, and I moved later to Artix with s6, and I'm thinking on testing dinit, and I have no issue. I guess if some major distros had made the move to runit or openrc, they would be more used as of now. BTW, at work, for containers and VMs I actually need to use systemd, and I see no problem with that.

It's totally true sysVinit was way hard to keep maintaining on distros, and something else was required. Probably given the influence from major distros changed the game over systemd, and now that's considered standardization now a days, but something else could also have become the standard. What's for sure is that there are success stories of using something else, Guix with shepherd, Artix with several inits (dinit, s6, runit, openrc), Gentoo with openrc (one can choose others, like systemd), void with runit, chimera with dinit, and the list goes on. Variety is not necessarily a luxury, in this case it means one can choose whatever aligns better to one's needs, believes (perhaps simplicity, perhaps minimalism, perhaps free/libre considerations, etc), and so on.

What's also true is that for work purposes, one can't be negligent learning about systemd, most probably one will need to deal with it sooner or later, because major distros, and in particular commercial ones, already embraced systemd, and that's not changing any time soon.

The sad effect of wide adoption of systemd, whether one opposes it or not, is that now services/daemons developers focus on providing systemd ready daemons, and for anything else the distro developers need to port to non systemd alternatives, and even build applications without systemd if that's possible at all. And if one is looking for a daemon not packaged by the non systemd distro of choice, ones is on our own creating the proper service/daemon, but not something impossible.