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/)BI
Posts
2
Comments
425
Joined
2 yr. ago

  • Use vanilla Debian. It is well suited for that purposes and it is great in terms of long time support: stable distro updates almost never break anything and upgrading to new release is possible and relatively simple. Don't listen to those recommending Arch or Fedora, upgrading them is a pain especially when you have to support many servers.

    If you want something more lightweight, you may try Alpine. It is also a distro of choice for docker containers. However I'd prefer Debian for the host.

  • I agree that autocrap is the worst build system in use now. However writing plain Makefiles is not an option for projects that are more complex than hello world. It is very difficult to write them portably (between various OSes, compilers and make implementations) and to support cross compiling. That's why developers used to write configure scripts that evolved to autocrap.

    Happily we have better alternatives like cmake and meson (I personally prefer cmake and don't like meson, but it is also a good build system solving the complexity problem).

  • There is a browser working natively in any system. I don't see any point in bundling a web app together with a browser and calling it a "native" app. The only difference is that you have no address bar in that case.

  • You are lucky. My laptop's fingerprint scanner did not work out of the box. I also had troubles with audio ("subwoofer" was disabled) and WiFi (losing connection). This all was fixed in later Ubuntu updates, but I had to wipe out Dell's spyware manually. So I'd say Dell with preinstalled Ubuntu is the same as any laptop with FreeDOS: you have to install the OS you need instead preinstalled one and troubleshoot all the driver issues. No guarantees that all hardware is Linux compatible.

  •  
        
    % libtree /usr/bin/zstd
    /usr/bin/zstd 
    ├── libz.so.1 [ld.so.conf]
    ├── liblz4.so.1 [ld.so.conf]
    └── liblzma.so.5 [ld.so.conf]
    % lsb_release -a
    No LSB modules are available.
    Distributor ID: Debian
    Description:    Debian GNU/Linux 12 (bookworm)
    Release:        12
    Codename:       bookworm
    %
    
      
  • If we assume that GitHub activity occurred during working hours 9:00 – 18:00, then the timezone is UTC+0, not UTC+2. There are only 6 events outside that interval, 5 of which occurred between 18:00 and 19:00 UTC.

  • It's a window manager feature. I don't know which one is used in Cinnamon by default and if it is able to do so, but you can switch to another one anyway even without changing the complete DE. E. g. xfwm4 provides such a feature. I believe that kwin also does.

    I also suggest you to try some tiling WM, you may like it.

  • almost no one lives in Siberia

    LOL, seriously? There are ~1 mln people living in Irkutsk, Bratsk and Angarsk (all UTC+8). And there are much bigger cities in UTC+7 like Novosibirsk and Krasnoyarsk. Of course there are much fewer people than in China but that's not "almost no one".

    However I agree that the malicious actor is likely from Europe or Middle East. I also investigated their activitity time but instead of commit timestamps that are easy to fabricate I looked at their GitHub activity time. Unfortunately, the GitHub API only allows to get events for the latest 90 days, but that is enough make some guesses (but not to say if they live in a country with the daylight savings time switchover).

    Below are extracted timestamps for those who want to examine them.