Try Orgzly with Emacs Orgmode

emacs org-mode publish

https://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.html

Have you heard something recent? I feel Signal has been saying that for years now.

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.

That sounds roughly correct, though I don’t see the connection with the article? Unless you’re saying that “products” (like Signal) will always exist, which is probably true but is orthogonal to whether or not other models will succeed.

As for email, I think posteo does a pretty good job, but you’re right options are few and far between. But self hosting email is just as viable as ever? Perhaps less so since e.g. gmail will instantly flag your incoming mail as spam if you’re sending it from randomsite.tld, but honestly that issue hasn’t gotten that bad (yet). Yes, whenever there’s a protocol like email or xmpp, companies will create gmails and signals and turn them into walled gardens, but that doesn’t spoil the protocol for everyone else. It just causes frustration that companies build closed products on top of open technologies, but not much to be done about that.

Interesting, what made you switch? I’ve never used nix but they are very similar.

Care to point me towards these lemmy guix posts?

Thanks! I’ve changed quite a few things in my setup over the years, but gruvbox is one of the very few mainstays (that and mpv).

Yep! If you’re applying and need a non-trivial number of locations checked/maps generated, you can check out the prgoram here.

Note that it says you can install it with guix, but it hasn’t actually been merged into master yet, so for now you do need sbcl and the dependencies (etiher via quicklisp or however else you snag them).

Very nice and quite similar to my Void + River + Everforest setup

what would you be stealing?

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.

Alternatively if price is an issue (NEVER use a “free” VPN) you could torrent over I2P, which is free and very safe (at least as safe as tor, if not moreso).

Also the next release of qbittorrent is about to have built in I2P support (but also standard I2P comes with its own torrenting software).

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.