oh, I see now, sorry! from mechanical I instantly thought you mean an HDD

yeah, but for OP’s amount that’s an overkill, the drives are very expensive

unless you span multiple boxes of discs which is a pain in the ass

FTFY

with two drives (preferably different brands/age, HDD or SSD doesn’t really matter) in it using a checksumming filesystem like btrfs or ZFS so that you can do regular scrubs to verify data integrity.

an important detail here is to add the 2 disks to the filesystem in a way so that the second one does not extend the capacity, but adds parity. on ZFS, this can be done with a mirror vdev (simplest for this case) or a raidz1 vdev.

went with an ssd in this idea since its more durable than a mechanical, better price for storage capacity

how? sorry but that does not add up to me. for the price of a 2 TB SSD you could by a much larger HDD

and most likely to be compatible with other computers in the future in case you need it for whatever reason.

both of these use SATA plugs, it should be the same

yeah. the reason is that they can get away with that.

this change was bundled with another one that was kind of good to have: building apps to an .aab file and making split apk’s out of it.
but in this scheme the dev builds the .aab, and google makes the split apk’s, and google needs your signing key to make the signed split APKs. the reason they need your formerly used signature’s keys is because if they would have started signing apps with a new one, users who had your app already installed would have had to first uninstall the app and lose their data, because android has a security feature that does not allow an update that has a different signature.

of course, while at first it was an option, the play store has soon made it a requirement that you upload your apps as .aab files.
developers basically didn’t have a choice, other than not releasing any more updates to the play store and letting google delete “outdated” apps when they want, like they’ll have a sweep soon.

the play store version isn’t as trustworthy even if the original devs published it there, since google forced all developers a few years ago to hand over their signing keys. the signature is how you know the app wasn’t modified by anyone, and that actually the developer released the apk

I was hesitant to open this post because I already know about rustdesk, but eventually I did to see the community’s opinion on it. I’m so glad that I did because this is terrible!

I think more people should hear about all of this

or neither, when cloosing open source tools worth their salt. in more and more fields such tools appear, fortunately

I had the impression that it has a Russian connection, but anyways, it’s good to be in the lookout for such things

in my book they are more of a risk than the USA. The USA already has political influence, for china to do it they need to use more extreme methods, like infiltrating your computer and use it and perhaps you as their tools

honestly I use the man command whenever I can. It gives distro-specific info, that documents the right version and any distro-specific patches

to be quite honest I don’t want to see any large business around my project unless they are paying. They are not my target audience, and I’m not eriting to funnel money into their pockets

you can have third party apps as system apps. you can even write your own, but the API docs are somewhat harder to find. nowadays you install them with magisk modules (not all of them contains an app), so that it is easier to revert and also to hide from those looking for it with a bad intent

Official Signal app. It asks Google to check Signal servers for notifications and to send them to you if there are any.

I don’t think that’s how push notifications work. It would not be instant, and very frequent polls are very resource intensive, even more if you had to do it for the servers of a million different apps.
UnifiedPush has a diagram here, and the popular proprietary push providers should work the same way too.

Also, Linux does not auto-update itself, and that’s bad mostly when looking at the programs (like the web browser) that did that automatically, and here it can’t anymore.

I understand that most users don’t update their system and the utils they downloaded, but that’s essential for a web browser.

I was considering that I should just install Firefox as the fatpak for everyone, instead of the core package manager, for this and other reasons, but my users have so little memory in their old machines that it’s already barely necessary.

I hate to say this, but windows rarely breaks itself from updates. basic things like the desktop, audio and the lock screen is essentially never broken after an update.

yeah it may reset the audio settings and other such things, and I don’t know how do they manage to do that, but that’s relatively simple to revert.

probably it’s just thanks to old, battle tested code though. can’t wait for Linux desktop systems to reach that point

having it just work is a necessary step to gett there

Automatic updates are essential. and unfortunately, it should not be an option to keep an old version of something, because through shared libraries it will hold back the entire system. fatpaks should be used for those programs.

Fortunately it’s getting there, like KDE is working on it too, but it’s still got a long way.

ok, but on a smartphone, with touch screen?