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/)CH
Posts
96
Comments
1,013
Joined
2 yr. ago

deleted by creator

Jump
  • Visually impaired people prefer being able to use the browser and actually be able to understand the content of websites.

    These features are local, private and improve accessibility, so I really don't see any similarities with telemetry which can be turned off anyway.

  • deleted by creator

    Jump
  • The recent addition of local in-browser website translation is an awesome feature I've missed for many years. The only alternatives I've found previously were either paid or Google Translate plugins. This translation feature is an example of an AI feature they've added.

  • As a former LineageOS for microG user I'm happy to say that it's no longer necessary to use it instead of official LineageOS because they finally added signature spoofing to upstream LineageOS [1].

    As far as I understand, this allows microG to work perfectly fine with any app on official LineageOS, without any patching of the ROM needed.

    I haven't tried it and there's no reason to switch of LineageOS for microG, but I'll definitely give it a shot on a future device.

    [1] https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/383573

  • Yes, NixOS does need quite a bit of RAM while rebuilding (~1GB) and takes lots of storage because it keeps older generations (similar to OS snapshots) around.

    Otherwise NixOS isn't any more resource intensive than other OS. Anecdotal experience, but my NixOS system boots faster than Fedora Atomic with the same window manager and packages installed.

    In any case, I've been using NixOS, Fedora Atomic and OpenSUSE MicroOS on my T480s without problems, so OP will be fine with any distro.

  • It doesn't seem like there's much ongoing work on suyu, which isn't surprising since emulators are difficult to develop. Not many people have the necessary knowledge and are willing to work for free.

    So yes, suyu is there for people who need it for it's performance, but it seems likely that Ryunjinx continues to improve while suyu won't change much in terms of performance and compatibility.

    It's great for the games that are already running well though, especially on low end hardware like the Steam Deck.

  • I don't see how the ability of users to actually know which repository an app comes from and change the repository makes it more likely for devs to not remove anti-features.

    I've had this exact issue a month ago where an app was available in official F-Droid repos and Izzy's and I didn't know which repo F-Droid selected by default.

  • My Pixel 4a is slower with GrapheneOS than stock. Disabling GrapheneOS' Secure App Spawning helps noticeably.

    With newer hardware it's likely not noticeable. (The 4a is old and even only receives security updates by GrapheneOS (no firmware updates by Google), so I really should replace it at some point.)

  • If they chose an open source license, a fork under a different name would be possible (else it's not open source).

    Their wording is ambiguous, so maybe they only talk about keeping the name/trademark to themselves, which is definitely a good choice.

    It's also not clear if they accept contributions, but they'll likely keep deciding what features should get added or not.

    At least that's how I understand it.

  • The 13T Pro, as well as the standard 13T, come in two versions - dual-glass design and glass front with vegan leather back, both featuring plastic frames with matching colors and metal-like finish. [1]

    The Xiaomii 13T Pro is available with a vegan leather back (plastic) which won't break from a drop. Instead vegan leather likely deteriorates in look and feel over the years, but I'd prefer it over broken glass.

    [1] https://gsmarena.com/xiaomi_13t_pro-review-2622p2.php

  • Glass backs were already popular on Android phones when Apple started using them. Previously they used metal backs, but they aren't compatible with wireless charging so manufacturers have to choose between plastic and glass — guess which one is more popular with reviewers?

  • Note that some devices aren't able to correctly mount the second partition.

    I guess this is because the first partition is used to boot ventoy, while the second partition holds data and some devices (e.g. printers) won't mount the second partition.

    PS: I nearly wasn't able to hold a presentation because of this, luckily a second stick/phone/copy on web storage saved me, iirc.

  • Hyprland and sway are the most feature complete tiling compositors I've tried. But since I strongly prefer dynamic tiling, there's not much of a choice. River tiling is the best in my opinion. Sadly it doesn't support moving workspaces between monitors, as each monitor has its own set of workspaces, which is a deal breaker to me.

    In general I strongly prefer Wayland over X11, as I've found Sway to be a better experience than i3 + picom for many years (not having to disable the compositor while gaming, better multi monitor support, etc), but having to switch to wayland-native tools is necessary coming from X11 wm's. For DE's that's not an issue.

  • Banks were able to create their own NFC payment app, which can be set as default payment provider.

    I'm not sure what else Google Wallet is able to do, but I guess this might be about being able to have a default wallet with tickets for events and similar.

    Hopefully there'll really be open-source wallets. With banking/nfc pay this isn't possible for service ands security reasons.

  • I prefer swap files over swap partitions, because it makes it my partition layout simpler to manage.

    If your using a swap partition, make sure it's located on an encrypted partition, else it exposes data stored in RAM (encryption keys etc). With SSD's it's difficult to make sure this data is actually deleted, even after overwriting.

    My preferred setup for a long time was LUKS with btrfs on top. Then subvolumes for /, /home and the swap file (+ /var/cache, /var/log etc.). This gives me peace of mind nothing is unencrypted except /boot.

    Nowadays I simply use zram, which allows for a small part of RAM to be compressed for swap. It's great, simple to setup and performs well. Imo it should be default for all desktops.

  • For swap files on btrfs COW and features like compression have to be disabled. I believe for btrfs the swap file even has to sit on a subvolume with those features disabled, so it's not enough to only disable them for the swap file.

  • One always has to be suspicious of Mozilla these days.

    As far as I know Mozilla never lied on technical details, at worst they didn't know about wrongdoings by their partners and acted once known about.

    The translation being done locally is advertised and should be simple to check with it being open-source. It also has to download for a while on first use, as well as translations take a considerable amount of time depending on the hardware. E.g. for larger sites it takes a short while until the last paragraph shows up as translated.