It will use more, but not exponentially more if de-duplication works as well as is claimed. The problem with AppImages is that they don’t include all of the dependencies, making them less reliable. At the expense of storage space, Flatpak bundles everything for reliability.
De-duplication works better the more Flatpak applications you have installed. e.g. de-duplication saves TheEvilSkeleton over 50GB of storage space here: tesk.page/…/response-to-developers-are-lazy-thus-…
The total size 27 GIB for 173 apps works out at an average of 155 MiB per application.
The average appimage is also that size. Like besides very big applications like libreoffice which is 300 MiB and kdenlive which is 200 MiB. The rest of apps are usually 150 MiB or less.
And most appimages are “lazy” appimages made with linuxdeploy, if you do finer control on the build you can get the size of the appimage way way down.
One example is qbittorrent, the official appimage is 100 MiB, while there is a fork called qbittorrent-enhanced edition, and they got the size of the appimage down to 26 MiB
making them less reliable
Hard disagree that they are less reliable, that might be less reliable on weird distros or very minimal installations, but usually the issue is that you are missing a lib and not that the app itself is less reliable, but stability wise, they have been the most reliable, case in point was yuzu, the flatpak was such as nightware that even the devs would talk againts it due to issues with mesa.
And the support channel of yuzu in their discord was full of people having issues with the flatpak that were magically fixed the moment they tried the appimage, due to that issue with mesa being outdated in the flatpak.
But anyway, I will install my applications as flatpak and compare the storage used.
if this counts as spam sorry not sorry. I created a tumblr clone two years ago. And then I conected it to the fedi like a year ago. its been hard, its buggy and its fun. Did a big redesign during christmas
Hello, A few months ago, the French government proposed a new law, putting the free internet in peril. But the global Mozilla community showed its power and stepped up to stop it. In a moment, we’ll share good news on our fight against this dangerous censorship, as well as next steps you can take to help. But first, here’s some context about what’s happening.
Part of the SREN bill (Projet de loi visant à sécuriser et réguler I’espace numérique’) as proposed originally would have given the government the power to censor what you can and cannot see online.
Immediately, the Mozilla community and our allies fought back. More than 80,000 supporters signed our petition and thousands of you donated to power this campaign.
And we have good news: a revised version was adopted in the French National Assembly, removing the browser-level blocking that was part of the original draft.
The amended bill is a huge improvement. And we can proudly say: This success can be credited to the Mozilla community and our allies fighting back, and the tireless advocacy work we have done for the last months.
While the National Assembly listened to the voices of the Mozilla community (Mozilla’s work was even mentioned several times during the debate!), there are several more formal steps in the legislative process.
Next up is discussion in a commission mixte paritaire (CMP): the text will be negotiated by a mix of lawmakers from the government, the National Assembly, and the Senate, in order to find a compromise.
And even if this text survives the CMP, it still won’t be quite over. The technical details will be laid out in an implementing decree.
##We need to make sure this version makes it through this next stage unchanged.
We must keep up the pressure now to make sure no lawmakers bargain and sneak browser-level blocking back into the bill - it would have disastrous implications for browsers like Firefox, not just in France, by handing over censorship tools to less democratic countries.
What you can do now: Thank you for being part of this fight. If you can afford it, please consider making a donation today to bring this campaign over the finish line. We’re at a crucial point and your contribution could tip the scale by allowing us to:
continue to connect lawmakers with tech and policy experts to show what browser-level blocking would mean for the future of the internet; and
prepare for a potential last minute public advertising campaign in order to mobilise more people and apply pressure on decision-makers in the Senate and government in key moments.
I know that they allegedly use the Signal proctol, but I find it hard to trust since not even the client is open source, even if their protocol is what they say it is, the keys could be harvested without issue, which is probably what happens when you use the reporting feature that allows them to read a piece of the message history, and they could still log your text input while typing. Of course, no way to verify neither their claims nor our theories.
what are the pros and cons of apt vs flatpak?
target OS is debian or linux mint
Wafrn is a tumblr clone that connects to the fediverse (app.wafrn.net)
if this counts as spam sorry not sorry. I created a tumblr clone two years ago. And then I conected it to the fedi like a year ago. its been hard, its buggy and its fun. Did a big redesign during christmas
[NEWS] Important update about the campaign against browser-levelcensorship in France (SREN bill) (imgur.com)
This was sent out by Mozilla today via email, fighting the recent SREN bill proposed by France ✊...
its even more outdated (lemmy.dbzer0.com)