BlackEco

u/BlackEco@lemmy.blackeco.com
198 posts · 1.3k comments

Recent posts

Recent comments

Personally, I would put one of the 990 in the server, use it as system drive + storage for databases and such. Then, the EVO in NAS to store backups, as it's not very bandwidth sensitive and saves a little bit of lifespan out of the main SSD. And probably an extra copy of your restic repository onto the external 2TB SSD (though I would store that extra backup offsite on Backblaze B2)

Oh, and you should probably set up restic's rest-server, it makes backuping from other computers really easy (easier than SFTP, which I had issues with)

For me the most interesting piece from the Mastodon thread is the fact that the Motorola partnership was born out of Google making it more difficult for non-OEMs to get access to AOSP source code (emphasis mine):

Google replaced pushing Git tags for certain source code with obtaining source code via Google Drive after making a request through Google Forms. It's completely ridiculous and they've gradually become very slow at handling requests. They're in clear violation of the GPLv2 now.

[...]

These changes won't negatively impact GrapheneOS on upcoming Motorola Mobility devices. In fact, it's a major part of why our partnership exists. It only negatively impacts Pixels and hurts Google more than anyone else. Google wants to make Pixels worse for no apparent reason.

This also means that in the future Motorola devices will get faster security updates on GrapheneOS than Pixels.

After a couple of years using Kagi, I've been giving Uruky a try for the past two weeks. It's a European meta-search engines which uses European indexes.

In my experience, setting Serper (a UK-based privacy preserving proxy to Google Search) as the first index to use gives the best responses, but I still happen to go back to Kagi once in a while (like, maybe 2-3 times in the past week).