I don’t agree with what is written in that blog BTW, 1st I like that there’s a repo that at least tries as best as it can to protect the free software aspect of the apps, which many disregard but are pretty important to me, that’s one of the main values from f-droid for me. Proprietary binary components can include many invasive “features” one is not aware of. As requirement the source code and building from it is required. If you build from source, removing proprietary dependencies for example you’ll get a different binary, and that requires a new signature on the final package. F-droid has improved a lot on reproducible builds. And I’ve read in several places magnifying the issue of apks from official f-droid being moths later compared to original developer release, my own experience is different, and when I’ve written, I immediately get a reaction from someone which doesn’t agree with me (I never reply back). I’ve read about the single entity signature, but that alone should not be an issue, otherwise we would be distrusting packages from debian, arch, and so on, which use a set of signatures to sign all of their packages, particularly when the build and signing process is automated, in some distros most packages come signed by the same bot. The issue about using a VM with a LTS distro about to expire or already expired is a valid one, but can you blame them when migrating breaks their flows and they don’t have enough hands, and that got overcome any ways. Now a days things are working fine AFAIK. That the clients support multiple repos violate an android policy, oh well, I don’t care much about android policies, and google for that matter, which collects a ton of data from users and people forgets about what that means, but what a bad practice not to follow those policies.

I believe some people really dislike free software, which is not the same as open source, one really need to value the four basic freedoms it procures, and if one doesn’t give a dumb for whatever reason then one doesn’t really appreciate free software, perhaps all one wants is not paid software, which is not the same. Free has two meanings and people often gets confused, and f-droid is about free software. It’s true they can’t guarantee every single bit of their content, but they trying through their policies and a few scripts has value to me, and taking a look at what free software meaning and the basic freedoms it looks to preserve is important to be understood before complaining about an organization trying to offer free software. It would be more appropriate if the terminology changes to use the spanish “libre” word instead, but it is what it is, that why sometimes FOSS is instead referred as FLOS (free/libre or free and libre). And true, as a result developers who want to provide apks through f-droid and also through non free software app stores or repos (whatever makes more sense) need to have in place something to account for the differences, and that’s not optimal, but there’s a good reason for it, but some developers just don’t want to do it and even less not depending on android proprietary stuff or other proprietary stuff for that matter, which is their prerogative any ways.

A little rant of mine, not we all have to agree over the same arguments I guess.

Well, it is available on the IzzyOnDroid separate f-droid repo, so if using the f-droid client, you can still grab freetubeAndroid with it.

Never tried it though, and not sure how bloated for a phone, but it’s easy to install/update with any f-droid client.

ohh, as I set sponsorblock for it some time back, I thought it also did it, but it does not.

Tubular and Libretube (both available on f-droid btw)

Well, to me xmpp is the way to go, but I guess it’s not a matter of opinion, but rather understanding the motivation.

Why is your dad looking for telegram? What caused your dad to look into it? Perhaps digging into those, one can make a case with alternative more private options. For sure one can always argue in general the already mentioned alternatives, and the ones to come are better privacy wide, but it boils down to why is him looking to use telegram. If it’s about having friends or co-workers, or a high school set of friends there, I would think there’s no way to change his mind, :( But more technology arguments like stickers, better voice/video conferences, whatever, then that’s more something that can be argued I would think, the same way if he’s just looking for something more private of course.

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 !

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 !