because they require more access to the system
afaik, you can allow more system access to flatpaks
Ubuntu runs a virtual filesystem in order to allow its Snap Firefox to access the Dictionary that lives "outside" its sandboxing
i believe flatpak also does that, you can specify some paths from the host to be available to the flatpak
my helping you
okay, this is a personal thing, but i need the source/citation for the 3rd quote. that grammar rule has beeg bugging me for like a month, i need to know where and when this is from, and who wrote this
and some native japanese words get katakana-ised too!
e.g. バカ, most animal names, etc.
where do you live where stuff's so expensive? genuine question, because honestly, i've never seen such pricing here
most of the stuff i get from amazon (which is, to be fair, not much and mostly non-food/perishables) has free shipping (without prime) to amazon lockers or to your house if you have a >25€ (or maybe >40€ now..?) order
also, may be biased because i live in france, but like, a loaf of bread is at most 3€ here, even in the most remote villages, you'll likely not have for more than 1.30€ for a baguette
what's your point? if flatpak makes it easier for developers to package their software and easier for users to install it, there's nothing wrong with it being famous
sony isn't a person
the package is maintained (will continue to install on modern ubuntu versions), but the software is unmaintained (no bug fixes, no new features, will stagnate and eventually become obselete as incompatible with future desktop standard modifications)
There are tons of ActivityPub implementations out there already
but none are widely used by such a massive amount of people as threads, and especially people who don't understand/care about spec compliance or even how federation works
honestly, i think in the best scenario, threads will create their own activitypub "fork", and most instances won't want to follow it, forcing the people who were on non-threads instances to chose between going to threads to keep in touch with their threads mutuals, or staying on non-threads instances and no longer having a reliable way of keeping in touch with those people.
worst case would be instances following what meta does and making them the spec dictators pretty much, the spec would become closed source and all other fedi implementations would lag behind in features compared to threads, and they can at any point change the spec and break other instances.
i think the point of defederating with threads isn't just the defederation, but is about sending a message that we don't want to play their game, we want to keep doing our things our ways. if they want to interract with the fediverse, they'll have to play by our rules, we don't want to follow theirs
and when they're caught, they'll dispute the claims with regulators, like every company does all the time.
i remember digging a bit into the french data protection office v. discord a while back, when they got hit with sanctions for not respecting gdpr, and they disputed every single claim, sometimes arguing in real bad faith, like them claiming they handle very little private user data, so they don't need to do data protection analysies like the law says.
considering google's sheer empire on data, i imagine they play the same tricks, but like 1000× worse
i swear i argued with someone that said killing lightning would create so much ewaste, and that still sounds like a stupid arguement to me…
you could, but they definitely pushed you to use a single account everywhere, even logging you in automatically to your google account in chrome if you use it on google search or vice-versa
i can understand that, but flatpaks are easier to upgrade and automatically integrated into your package manager, which (i believe) isn't as straight forward for appimages. also there's one major repo where you can find most apps (flathub) making app-hunting less daunting i feel like.
also, once your app is installed, it's always in your system menu, so that doesn't change much in the long run
can't you carry over flatpaks as well? you can probably copy /var/lib/flatpak or wherever they store their stuff from one system to another, or failing that, save all the app IDs you have installed, and re-install them onto your new system, backing up ~/.var to keep all your data!