As suggested by a user, [lariza] defaults to using HTTPS since the
release v21.12. So, when you enter an address into the bar, say,
`www.vim.org`, then the browser will request `https://www.vim.org`.

It works surprisingly well. I wonder when/if the big browsers will do
the same.

Honestly, it's only a problem when requesting local URLs, like
`http://localhost:8080`, because you now have to explicitly add that
`http://`. I trip over that quite often. (It would be easy to filter the
string `localhost`, but I also often use my system's host name instead,
because some daemons I use don't bind to 127.0.0.1 but my NICs IP.)

That said, I'm not sure about the future of lariza. It needs to be
ported to GTK4. I don't have the motivation or energy to do that at the
moment. (The same problem applies to my terminal, [xiate].) The program
needs to be restructured quite a bit (with GtkApplication and all).

To be completely honest: I often thought about discontinuing my GTK
programs. It's not a lot of fun to keep up with GNOME's shenanigans.
Reading through their [migration guide] makes me just want to go to bed
instead. It's going to be a lot of work.

We'll see. It would make me sad to abandon these projects, so maybe I'll
just do it. Who knows.

[lariza]: https://uninformativ.de/git/lariza
[xiate]: https://uninformativ.de/git/xiate
[migration guide]: https://docs.gtk.org/gtk4/migrating-3to4.html

You are viewing proxied material from uninformativ.de. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.