I’ll never understand why we don’t just use s-expressions.

I think I said something a bit stronger than what I meant. I'm not averse to sharing my thoughts on posts, I've just never held it against a post if the OP happens to not provide some comment containing their thoughts on it.

I do see what you're saying about not knowing what something is, and not wanting to spend ~1 hour on it to find out. Though I still don't think that's what downvoting is for (unless you have positive evidence that it's spam).

Mainly I disagree with "I'll downvote it to make room for the posts that are definitely good". That's just very much not my philosophy and not one I ever took to be a majority view. Downvoting for me means the content is not good/appropriate/whatever. It's a sign of negativity, and being not definitely good != being bad.

I don’t care about XMPP as a protocol versus some other messaging protocol much, but I care a fair bit about the wdespread adoption of federated XMPP

I don't quite understand what this means, could you elaborate?

if this service using this protocol becomes very popular, will the service seek to eliminate the open role of the protocol

That is a valid concern, though the point of the article is to try and convince people why it won't happen like it did with Google or might with Meta for structural reasons (rather than "oh but we're different" reasons).

The main difference I see with Snikket vs Google Talk is that Snikket is not only libre client software, but libre server software as well. The point of Snikket is that individual people host it themselves, not that the Snikket devs run a bunch of Snikket servers which require their Snikket client for connection and just so happen to use xmpp to power it. Really all Snikket is (right now) is a prosody server with some pre-configurations and easy install, as well as an android/ios app which are general xmpp clients that are designed to work well when connected with Snikket servers.

Now it could still go south in a similar way to Google Talk, in that maybe a bunch of people start running Snikket servers and using Snikket clients, and then the Snikket devs start wall gardening the implementation. That would be bad, but the users (both server runners and client users) would be in a much stronger position to pivot away from those decisions.

I think it's at least an interesting idea (hence why I posted it) for the reasons the author mentions: striking a balance between trustless freedom and interface stability/agility.

Yep! I used it as a daily driver for ~a year, switched off to try something new, and have recently switched back indefinitely.

Only distro I’ve ever switched back to after leaving, and that’s because it’s where I plan to stay. It really lives in such a sweet spot of up to date, stable, and simple/hackable.

With a nice handbook, friendly community, runit, xbps-src, and multi lib/arch support, Void is truly great.

guix pull && guix upgrade is still a bit slow, but I never thought excessively slow (definitely slower than xbps, pacman, and probably apt too).

I guess I never thought much about it because of rollbacks, so it’s safe enough to just cron.

I've never used Arch or Nix, but I switched from Void -> Guix and have been very happy with it. It's such a huge peace of mind to be able to have your whole system declaratively configured, package changes being atomic and generational (rollbacks so no worries about breakage), Guix shell for messing about, and being able to make your system do anything you can write in Scheme.

That's my daily driver. On servers so far I've gone with Debian Stable + Guix.

Also Void is still a fantastic distro, and is what I would use if not for Guix/Nix.

lol glad to see you here on lemmy too, keep up the good and enthusiastic work :)

I have never used nix or nixos. I liked their shared idea (functional, atomic, reproducible systems), and so when I looked at their differences they seemed to all be pros for guix:

1. Clearer, more robust, more centralized documentation
2. GNU Project
3. Guile Scheme (Lisp) as opposed to Nix DSL
4. Unparalleled emacs integration

The only bittersweet aspect of guix compared to nix was the foss only stuff, as I do need some proprietary drivers, but nonguix is so easy it hasn't been a practical issue. And of course I am big advocate of free software so I like that guix is pushing that forward.

There's also a theoretical issue that guix has less packages, but the standard channel + nonguix has had everyhing I use.

Memmy has been working very well for me. Lots of updates very quickly and feeling good.

Been really enjoying Memmy. Has been getting updates at a super fast pace and already feels pretty good and featureful. More to go but the dev work has impressed me.

I quite enjoy it!

Being able to rollback any change I make to the system, either package changes or system configuration, makes it completely unbreakable and provides great peace of mind. It means I can fully enjoy its rolling-release nature without worrying.

Having my entire system configuration declared in a single, robust programming language (Guile) across a small number of files makes it very easy to understand and just stick into source control to reproduce.

Being able to hack on it in a lisp (scheme) is the cherry on top, along with the great emacs integration. I would highly recommend it to any lisp/emacs/gnu enthusiasts.

Thanks for pointing that out! The more math in the federation the better I say.