Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)GR
Posts
1
Comments
361
Joined
2 yr. ago

  • Welcome to Gnome. "The defaults are good so you don't need customization" seems to he their montra. Honestly there probably is a way to change the sidebar however you like, but it will he buried in a config file and break between upgrades. Dolphin might be a better fit. KDE seems to go the other way, not great defaults, but you can customize as you want.

  • Just for market dominance I assume.

    Almost certainly. I'm glad they failed to buy it. It would have been a mess in the long run, but clearly they have plans for ARM.

    Yes, but that chip is old. It was already a bit outdated when the switch came out, and that was 2017.

    Correct, but they do work with ARM already. I'm guessing they will be making the chip for the Switch 2, which will probably be out of date when it comes out in 2024, but it will be a more modern chip.

  • I tend to fall on the AMD side of things on PC, but I'm glad to see things getting shook up on the ARM side. I'd love to see AMD and NVIDIA go ham on RISC-V, but that's a much bigger risk right now, and probably needs another 10 years of refinement to hit the efficiency of ARM.

  • Just a note, I'd recommend against fast charging unless you need it. It's not great for the battery of the phone. I know my phone automatically slow charges when I plug it up at night because it assumes it will stay plugged up for a few hours.

  • So I setup every "client" to have the "server" as the introducer and auto-accept shares. Then on the "server", I add the new client, and give it all the shares. The new device auto accepts, and all the other clients automatically include the new client.

  • I may be misunderstanding what you want, but the introducer feature seems to solve the problem. You setup your "server" as the introducer for all your other devices, then when you add a device, you just setup your new device with the server, and all other devices get the trust of the new device from the server.

  • After the phone restarts, you must unlock your phone with your PIN(or swipe pattern) before you can use your finger again. The same is true with the 24 hour timer. Android also has a feature that if you hit the power button a set amount of times, it requires the PIN/Pattern too. So if my phone and my finger print have been separate for more than 24 hours, my fingerprint is useless. If I have any warning at all, my fingerprint is useless. Also, after a set number of failed biometric attempts it requires PIN as well. Which means the law better get the finger print right in only a few tries or they lose their chance.

    Yes, it is technically possible that law enforcement may steal my phone, duplicate my finger print(in a way that works on my phone's finger print reader), and use that to unlock my phone while they have a chance, then suck everything out of my phone. But for anything government, that's moving pretty swift for anything they might want to book me for.

    I'm guessing you could reduce that to a lower number of hours if you really felt the need.

  • Finger prints on Android stop working after 24 hours, a reboot, and some other cercumstances. I feel pretty OK using fingerprint to unlock my phone, because in about 99% of cases I might be compelled to unlock my phone, I will either be able to restart it first, or that 24 hour timer will have expired.

  • Completely unrelated: A feature that server likely has that you should investigate is called "iDRAC". There is probably a dedicated NIC on the back for it. It allows you to power on the server, control most "BIOS" features, and see the screen remotely.

  • Often you can mirror ports on routers and switches, this lets you send the same packets to a device as gets sent to your router. This will allow you to use something like wireguard to capture the packets and inspect them. Unfortunately for you, the vast majority of traffic is encrypted these days. So most of the time you can see how much data is being transmitted to Google, but not what data. Tools like Fiddler will help you on a specific machine, where it can decrypt it on the fly.

  • Most distros use whatever DNS provider your router's DHCP gives them. That's not something the OS normally decides. Some browsers are taking upon themselves to use DNS over HTTPS, which often does use Cloudflare or Google, but that's not the OS doing it.

  • Doesn't surprise me. RISC-V seems to have hit a critical point where it can compete with ARM and x86 on some tasks. It probably wont be replacing our desktop processors just yet, but you might start seeing it in embedded applications more and more. I know nothing of it's technical advantages and issues, but being completely open and free for any manufacturer to take and use probably sets it above ARM for many uses.

  • I'm a fan of doing business locally for this reason. People tend to treat you better when they know if they piss someone off enough that person could take a baseball bat to their car. Joking aside, small local companies tend to care about reputation. You are 1 of 1,000, not 1,000,000. Your money constitutes a significant portion of their profits. Unfortunately, it seems like every day there are less small businesses to do business with.