For those using tbsync with TB, and any companion extension, like its provided for exchange (office 365 and the like), TB broke tbsync and its companion extensions.. That said, there's an issue, and apparently some developer releases for those wanting to try....
It's been several times TB breaks extensions with such changes. TB devs don't have to care, but that means for the users, to be extra careful, and to avoid upgrading until finding out required extensions have caught up...
The env var works fine on Xorg though. And yeap, several applications need to catch up. That's what I meant when I said it's not wayland fault itself. However it's been years things have been trying to catch up. Every now and then I try, but a couple of months back I couldn't routinely use wayland, given all missing functionality plus additional nuances... The hard part is that if not using gnome, or plasma for that matter, getting things working take a lot of time, just to find out some things, I depend on for work, don't work yet. At any rate, I still pay attention as well, to forums like this, to see if there's some news that might trigger another retrial...
What I'm missing from wayland, it's not really something from wayland itself. Examples are several needed electron based applications, which some will refuse to properly work (for meetings, desktop sharing, etc), wine, gtk4 applications not respecting GDK_DPI_SCALE (not sure if already addressed) when not using gnome (wayfire being used as compositor), no proper support for conky (or eventually equivalent wayland functionality) yet, and several nuances with waybar, and some other tools. Major issue is my work dependency over some non floss electron binary blobs, like teams, slack, and so on, which particularly for desktop sharing and meetings don't yet work properly, no matter the electron options one can use for them, and some floss I use like signal, freetube, jitsi. Wine has a horrible hack, which I might live with, but it's horrible...
So I'll have to wait further for non wayland stuff to truly support wayland, and it has taken ages for that to happen, :(
I haven't tried labwc, andit sounds interesting, though I don't like openbox configs, and I really love fluxbox ways, which are also text files, but I never got used to openbox configs, perhaps just because I got way too familiar with fluxbox, which is what I use with Xorg (fluxbox + picom + tint2 + conky).
AFAIK, most indexes ddg uses come from bing. So it's not really a search engine with its own indexes on its own. I'd suggest using SearX, and if one is willing to sacrifice a bit of privacy over some data and stats gathering, then SearxNG.
searx and searxng are not search engines, and searx is more private (searxng collects info from users, which searx never wanted to). AFAIK duckduckgo is neither a search engine on its own, it uses blink...
are there archive pages for cgtn or other such domains? I'm not sure if because behind the office firewall, but I can't read the contents, just the titles, :( Perhaps both URLs, the original one, plus sort of an archive one...
ohh, so I can use any torrent client (rtorrent for example), as long as I only use i2p sort of trackers, or so I understand from your post, and also from the wiki, perhaps specifying the binding address and port, or something like that...
Sorry if way too OT, :( What torrent i2p client are you using? I don't like the idea of vuze with a plugin, neither biglybt. I'm more inclined to something like rtorrent (ncurses, and if used with detached screen, then on any ssh session you can remotely monitor, without needing additional remote accesses or web publishing)...
Thx, will do more in depth later. Already gave a 1st glance. It's clear that guy really pushes for a VPN, and better yet, according to him/her, with port forwarding.
Well, I would extend FF to all derivative browsers, particularly those oriented to privacy, like Librewolf on the desktop and Mull on Android. Their in essence their FF counterparts with privacy settings applied, and removing binary blobs (yes FF still include some)... But I guess those are even less known than FF itself, :(, though overall, they depend on FF being maintained and progressing, since those projects don't develop a browser one their own...
For those using tbsync with TB, and any companion extension, like its provided for exchange (office 365 and the like), TB broke tbsync and its companion extensions.. That said, there's an issue, and apparently some developer releases for those wanting to try....
It's been several times TB breaks extensions with such changes. TB devs don't have to care, but that means for the users, to be extra careful, and to avoid upgrading until finding out required extensions have caught up...