I have no idea, the documentation didn’t even warn there would be any.

I’ll keep you updated if I end up having any performance issues.

Hi,

Did you end up doing it ?

some asshole could extract/crack it and give her a massive bill […] it will be trivial for some asshole to make a revanced patch to bypass the subscription

Hi,

I stumbled on your post looking for a ReVanced patch for Infinity, not for bypassing the subscription though : until now, I was using a fork that implements login using Reddit’s official app’s API, but it stopped being updated while I was getting tired of some bugs, so I was hoping for a ReVanced patch which would accomplish the same thing. There isn’t, but I found one that allows you to bring your own API key, so I went with that.

Before using that fork though, I was bypassing the subscription, with Lucky Patcher : it worked fine, which, as you pointed out, means I was making the maintainer pay for me. I didn’t really feel bad about that because they made the choice not to support any of the abovementioned alternatives, even though when I discovered those, I switched because I still didn’t like Reddit getting that money.

Willing to give this a go.

Alright, don’t hesitate to ask questions if you have any and request help if you need any

My go-to for getting non-repo debs automatically has been deb-get

Yes, I mentioned it in the Differences with deb-get & AM section of my tutorial.

it seems to go long periods of time between PR merges and releases (which includes adding new software)

Yeah, I could reiterate in that section that my app allows the user to add apps themselves.

I didn’t say it was more secure, I said it’s about the same.

You said automation breeds laziness (by design, to an extent) and lazy end users tend to shoot themselves in the foot.

So, my question is : what part of automating download of DEBs from a specific source can be shooting oneself in the foot compared to doing the same thing manually every time ?

you should legally protect yourself

The MIT license will take care of that.

Also, to force the user to accept and acknowledge that the software they are installing using this tool is not verified to be safe is inducing fear and/or guilt, therefore is bad UX, I’m not doing that.

It’s more functional than object-oriented and I read the former better than the latter. 😅

You understand perfectly.

How is the manual step more secure though ?

What does the user do before downloading a DEB that makes that gap between manual and automated ?

I’d be willing to try and reproduce that, but I don’t see anything.

It doesn’t, that’s provided by Cortile.

My point is that I’m working a solution for end users.

The solutions you’re offering are not user-friendly.

I don’t care.

I’m and end user working for end users.

My main use case is end user desktops.

Which isn’t user-friendly.

Well, I’m just automating what people currently have to do manually : visit GitHub and download DEB and install DEB.

If the automated process would be dangerous then the manual process also would be, and that would be on the maintainer for not providing an APT repository or a Flatpak, not on the user for just downloading from GitHub.

Why the OOP structure and syntax ? Sorry but it makes it difficult to read for me even in my own language 😅

I didn’t know there was one, that’s interesting, thanks.

Updates must still be delayed because of being third-party though.

I’d be willing to implement additional features for people who are extra careful about security.

Could you please explain what does this consist in ?

Thanks

What’s a FIFO ?

I’ve also looked into VFS but found nothing I’d have the skills to implement. 😅

I’ll look into it, thanks !