Actually, FLOSS is more precise, given the “L” coming from “libre” in castilian (spanish now a days) referring explicitly to freedom. But it so happen open source != free/libre software, therefore open source usually disregard the philosophic aspect of freedom, which might turn against the users interest, which is what GNU guys were trying to prevent all along, because focusing in the practical aspects, without any concern on the principals behind, actually do have implications on the software itself and its usage.

You’re aware Librewolf removes some stuff, and then provides an already applied though opinionated user script, based on the arkenfox, and an easy way to override settings, right? Meaning it’s basically Firefox with sane defaults which can be easily overwritten if needed.

+1 to rtorrent

rtorrent, you just need an ssh connection if wanting to know remotely what’s going on

IronFox is done by the phoenix developers I believe, and FrozenFennec, which hadn’t been released, it more actually based on Mull. If you care IronFox is not part of official f-droid, but offers its own f-droid repo, FrozenFennec is being developed as an extended/special Fennec and it’ll be released on official f-droid

FrozenFennec on the work, a fork closer to Mull in some settings I believe.

FLOSS used to include the ability to build software. Perhaps that’s not important anymore but now a days some developers don’t attend problems with their build recipes because they only consider what they release through binaries, whether on flatpak or whatever other binary repository they like. At least I dislike that, it’s ok to me some or most users would prefer to grab a bloated binary rather than building anything, but that doesn’t mean forgetting about those actually wanting to build from source, or wanting to use shared libraries and software from their distros, actually that’s a requirement for free/libre software repositories. Not sure if the tendency is to move the gnu+linux users into app stores like the ones on windows, now ubuntu snaps, android play store and the like. Sure there’s more security with sandboxing, but nothing one can’t get with firejail, and if wanting MAC as well then firejail + apparmor for example.

At any rate, just my little rant. And if you’re wondering, I use AUR on Artix, and I really hope I won’t have a need for a flatpak stuff.

Well @fishonthenet@lemmy.ml used to post in here, and he was an active Librewolf developer, see his first post on this very same community, and he still is one of the moderators, though I believe he’s no longer around, 🙁

https://librewolf.net/docs/faq/#can-i-use-firefox-sync-with-librewolf-is-it-safe-to-do-so

(things change quickly though, given Mozilla Corp decisions)

What’s the error you get? Perhaps someone has dealt with it before. What overrides have you tried?

There are several things that might affect some sites and are more troublesome than others, for example:

• security.OCSP.require
• webgl.disabled (if changed to false it’s recommended to use the CanvasBlocker extension)

ublockOrigin can give trouble to some sites, a quick test is to temporarily disable it and see if the site works. It can be investigated further what specific filter might be affecting the site.

Have you tried enabling webgl, which by default is disable on Librewolf? You can do that by overwriting the corresponding setting, as it can be done for any Librewolf setting, in particular the webgl override needed is:

defaultPref("webgl.disabled", false);

If you do, Librewolf recommend using the extension “CanvasBlocker” given the fingerprinting allowed by webgl. There’s a settings doc BTW…

Corps are for profit, and Mozilla is a Corp… Really sad times indeed.

If using wayland: wlsunset

Where did you get this idea?

I didn’t knew about Microsoft taking over the fsf either, and I am getting concerned about the real freedom behind my beloved Linux.

I think you are confusing FSF with the Linux Foundation, and you can see MS as part of the platinum LF members. Was that it, or you really meant FSF?

If you have installed wlroots, that’s why. Wlroots has a hard dependency on libseatd, which is provided by seatd. Labwc also directly depends on it. Sway as well can use seatd as both documented by sway itself, and its arch wiki, but for some reason it doesn’t directly depend on it, though it depends on wlroots, :). This is not a problem on arch since the seatd service can co-exist with logind/systemd, and on arch you can use the seatd service combined with libseatd for software build on top of libseatd, and users on arch can then choose between seatd or policy kit on that software. On other non systemd distros like artix, the seatd daemon is in conflict with logind (on artix it’s extracted from systemd), precisely because you can get away without logind as long as you use acpid to provide some of the functionality logind also provides besides session administration. Not sure if besides wlroots on archthere’s additional software depending on seatd. Several wayland compositors are based on wlroots, which attempts to somehow offer a standard for compositor and applications developers.

So it might be xdg-desktop-portal behaves differently for sandboxed apps such as flatpak ones than regular apps, hmm. So I’d still like to know how required d-bus is…

Thanks a lot !

Have you explore hyprland, niri (scrollable, not dynamic, but it’s sort of dynamic then) or sway (static tiling though, but offering tabbed layout and dynamic stacking/floating, plus hugely customizable)? Did you discard them because not close enough to bspwm? Just curious, not to judge your decision or anything like that.

Being an artix user, are you using logind (the official default), or just seatd, or the new logind alternative turnstile (not supported by all init systems, looks like only dinit which I use and openrc, tough void has it working with runit I believe)? I’m wondering what’s really required on wayland. I like the approach of just seatd, but I don’t know what one would lose and what are the wins, but if not seat alone then turnstile which actually require seatd. Also I would like to drop calling d-bus, but I’m not sure if that would prevent the compositor to work, but further if screen sharing with webrtc, electron apps like slack or teams-for-linux would stop working. I guess not using d-bus would not affect mako. But any ways, I’m curious of what would be you choice for your wayland experience if/when you get into it. The official and default way is just logind plus d-bus plus polkit. For such sharing xdg-desktop-portal is required, which fundamentally seems to be plumbing of d-bus, but I’m not sure…

BTW, from the blog post referenced, dudemanguy is also the mpv developer, so that requires quite a lot of effort (mpv specially on the support side of things, besides the developing effort, particularly to support wayland, and mpv does for some time now) together with artix effort. I’m glad he’s back writing, :)

Hey, sorry to take adantage of your answer, perhaps you can help me out though.

Is dbus actually necessary for xdg-desktop-portal? I understand from this flatpak post that xdg-desktop-portal is actually a bunch of d-bus interconnections, which of course make d-bus fundamental for xdg-desktop-portal, but wanted to confirm. xdg-desktop-portal is a must on wayland if one wants to share screen through webrtc, or electron apps like slack or teams-for-linux (probably zoom which is Qt as well). But I’ve read some people (this for example) start sway from console without d-bus, without logind/systemd, just seatd on the background (wlroots and sway support seatd). So perhaps those people are not interested on sharing screen, I don’t know. Or perhaps such d-bus plumbing is only required for flatpaks apps, which are sandboxed, thus requiring all that interconnection to access resources and such, and then I’m not sure about a thing…

Thanks !

BTW, just in case, not only the system configs are inmutable on Guix, the root/system directory is also read-only making it an inmutable distribution. So the argument that the Guix system is not inmutable is not correct. There are many places clearly stating that, but the itsfoss 12 inmutable linux distributions is one of them, and by its definition of inmutable:

An immutable distro ensures that the operating system’s core remains unchanged. The root file system for an immutable distro remains read-only, making it possible to stay the same across multiple instances.

So Guix is actually an unmutable distribution. But moreover, it’s much more than that.

Well, I think you already mentioned the key thing about encrypting disks. It’s not about protections when the block device is already decrypted and the filesystem already mount. At that point your disks are decrypted and anyone with or without physical access to your device, if gaining any access to it you’re toast. That’s true, but that’s not what disks encryption help you with, and you already mentioned. If you turn off your device, and someone steals it, or gains access to it, they can’t look at your contents, that’s it. That wouldn’t prevent malicious people, to instead plant something through UEFI for example, and you are right about that case. And if you never turn off your computer, and just do sleep to memory, then you depend on how strong your password is, or any other authentication mechanism you have…

Can you explain why if someone get access to your encrypted disk, they would have access to its contents?