It does neither atm, it simply serves you the streams as-is. The plan, however, is to eventually proxy all requests so that the services aren’t able to see it was you who made the request but only get the proxy’s IP

Leaving my project Tubo in case someone finds it useful. Support for it just got merged on Libredirect

Leaving my project Tubo in case someone finds it useful. Support for it just got merged on Libredirect

fsdaufsad8f97sa08f97a

Yes, you can use a “puppetting” bridge like mautrix-whatsapp to talk with people from WhatsApp.

vi support is built into the browser, you only need to enable vi-mode in your default-modes. There is no concept of tree tabs, you manipulate tabs as “buffers” that you can switch to via fuzzy search, which IMO is far more efficient. You can take a look at one of the core maintainers’ config. Alternatively, I’ve recently added a Guix home service and feature into rde for those that want a more batteries-included config, which you can check how I use in my dotfiles

Matrix with mautrix-whatsapp, mautrix-instagram, and mautrix-telegram. I strongly think that protocols should be interoperable for them to succeed, otherwise we’ll create a multitude of silos like Signal, Threema, etc that further separate communication.

More people should be aware of Nyxt as I believe it’s one of the greatest efforts towards a customizable browser out there. It aims at being renderer-agnostic, but it currently only supports Webkit and there are plans to support Blink via Electron. I built some extensions for it in Common Lisp and I can say the ecosystem is much more fun and open than standard browsers.

432432$@$#@23

I’m an EXWM user too, but I’d like to migrate to Wayland some time soon. This looks promising, but if nothing comes out of it I’ll probably move to dwl-guile

GNU Guix. It’s a joy to manage your systems with a Lisp