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/)𝒍
𝒍𝒆𝒎𝒂𝒏𝒏 @ lemann @lemmy.dbzer0.com
Posts
6
Comments
486
Joined
2 yr. ago

  • I personally prefer Firefox's rendering, or even Edge's old and long deprecated EdgeHTML (Trident fork) renderer.

    IME Chrome performs way too much antialiasing on graphics that are not to scale, and their default font hinting technique doesn't match Windows or even common Linux distro defaults.

    It feels a lot like the enhanced speed and performance come from the shortcuts taken in the renderer, akin to Safari... except that Safari also opts to just refuse implementing new APIs and draft specs.

    Text heavy sites in particular are not really that nice to read in Chrome for me personally.

  • It also supports some funky stuff like raw H.264 over UDP if you use ffmpeg to prepend special packets to the start of the video stream (Ideal for a DIY low latency video streaming solution ). If you decrypt digital OTA tv signals (DVB format), VLC will play the live underlying raw mpeg stream just fine.

    Truly a swiss army knife of video playback, especially the underutilized network url file open option

  • Not exactly IMO, as containers themselves can simultaneously access devices and filesystems from the host system natively (such as VAAPI devices used for hardware encoding & decoding) or even the docker socket to control the host system's Docker daemon.

    They also can launch directly into a program you specify, bypassing any kind of init system requirement.

    OC's suggestion of a chroot jail is the closest explanation I can think of too, if things were to be simplified

  • I use certbot on only a single one of my oldest projects that has been going for almost a decade.

    For everything else I use acme.sh because it works so well and integrates with a ton of DNS providers. The one time I had an issue, it was already fixed in a PR, so I just checked out that fixed version and used it for renewals until it was merged in.

  • Just checked the whois history on that and wow.... purchased for $6000. That is a lot of money for a domain!

    It was $500 prior to Reddit's API changes, looks like another domain parking company purchased it around that time and hiked it up to $6000. Greed is one hell of a drug.

    Quite curious about the current owner though, since it's been registered privately via a proxy company.

  • From what I understand (based on smaller printed buildings anyway) it's identical to FDM 3d printing pretty much, except that instead of filament, a massive onsite silo contains a liquefied cement-like mixture. The nozzle also has a valve of some sort to immediately stop flow.

    Typically one operator has a computer running the printer host software, and others manually fix-up print errors (and things like blobs) while the mixture is still damp. A paperclip shaped rebar is also inserted into the walls every few layers for additional structural integrity

    There are challenges with things like rainfall retention in walls during construction, but various companies have their own way of dealing with that from what I understand...

    Due to the mixture it's usually restricted to walls AFAICT. Overhangs like doorways need beam supports to be inserted into the structure beforehand

  • I'd never imagine that the first time I'd encounter an in app purchase that outrageously expensive, would be on a wheelchair app.

    F me, why do companies have to extort people like this! Glad you got it cracked in the end.

  • Nah, I feel cheated by Fairphone. With the whole FP3 and FP3+, they were leading with the idea that they have settled on the form factor, and then just evolve the separate mainboard/camera/display modules independently

    Fair enough. From my perspective it was ambitious thinking anyway: I was actually curious as to how Fairphone got things like the replaceable camera to work (had a peek in their git, it kind of works: they init the old driver and try to turn on the camera, if it returns an error then they load the new driver). The truth is though, a 100% truly modular phone, in the same way a PC is modular, cannot happen without some serious standardization.

    Unlike webcams that use USB internally, and laptop displays that use standardized connectors and protocols (like eDP), mobile phones are almost entirely proprietary devices with a finite hardware-limited range of peripherals they can support at a low level.

    Qualcomm in particular doesn't care about backwards compatibility when it comes to their SoCs, meaning the MIPI interface for the phone display on one SoC may be moved to completely different pins on another Qualcomm SoC, or may use a completely different number of pins. The same applies to the camera interface, although the main concern there will be the SoC, as it ultimately determines what resolutions/framerates etc you can achieve within the limits of the camera module.

    Those are both solvable problems though. The real issue in my eyes is the lack of a proper BIOS to build a device tree and the other stuff that an OS build would need to be device-agnostic, like closed-source blobs for fingerprint scanners, display brightness control etc. These essentially limit mobile ARM devices to OSes made specifically for that hardware, preventing drop-in upgrades for cameras and the like from being a thing - unless you take Fairphone's approach and handle it in user space

    With the FP4, they scraped all that and just chased whatever was trendy at the time and cranked the "but the environment" marketing.

    I agree. To me most of the FP4 marketing material felt a bit like greenwashing, and the excuse for the headphone jack removal was pretty poor considering they also released completely unrepairable earbuds shortly after. The materials used may be fairer, but the pros end there as far as the buds are is concerned.

    The FP5 marketing material is not as bad in that regard I think, and the Fairbuds XL should have been what they released originally compared to the unrepairable buds cash grab, even if they offered it discounted (IIRC) with the FP4.

    I paid the Fairphone premium knowing that the specs were crap, but that at least in the future I wouldn't need to upgrade by buying a whole phone. Promising to have software upgrades for 8 years is nice, but it's worthless if you can not upgrade any of the hardware in the meantime.

    For now I will just go buy a "budget premium" Android and pray that the people from frame.work decide to extend into phones as well in the next 2-3 years.

    True. I feel unless the software updates are optimized to take advantage of the phone's hardware as it ages, the performance will fall off a cliff, especially as consumables like the EMMC storage uses up its write cycles, and takes longer to identify suitable areas of its NAND to use for operations.

    A Framework phone would also be something I'm interested in, especially if it follows the likes of Project Ara's design

  • Nice. I've personally been using Linux on a Mid 2012, and the touchpad responsiveness + gesture support has been one of my favorite things about the experience.

    Really nice to see gestures in general getting more support in the wider Linux dev community 👍

  • Ifixit has FP3 displays in stock in my region.

    As for a replacement... I don't think there's much devices that will fit the bill unfortunately. Closest thing is going to be a Pixel device IMO

    I personally use a FP3 too, and can't see a device that I can upgrade to whenever my FP3 kicks the bucket. I came from a Galaxy S5 and this was the only device available that offered all the same features, except the heart rate sensor, OLED display and ANT+ support (for connecting to Garmin fitness sensors Etc).

    Fairphone does make some really odd decisions, like none of their new devices having a headphone jack despite there being a DAC output still available on the mainboard. The main saving grace is that they know how to make a device you can actually own, and historically they were proactive in getting their OEM to implement user requested features into the OS.