• 0 Posts
  • 335 Comments
Joined 2 years ago
cake
Cake day: June 23rd, 2024

help-circle









  • Here’s the list of logos row by row so you don’t have to awkwardly ask what they are

    Steam (not FOSS)*
    “LL” (likely OP’s own design, not a FOSS project)*
    Zigbee
    Obsidian (not FOSS)*
    Brave
    Protonpass

    Tailscale*
    Home Assistant
    Raspberry Pi (not open HW)*
    Ubiquiti (not open HW)*
    Android (not really FOSS)*
    Signal

    DigitalOcean (service)*
    Ubuntu
    Linux
    Claude (not FOSS)*
    Proxmox
    Nextcloud
    Jellyfin (rotated)

    Trilium
    Nginx
    Tabby
    Bash
    Debian (rotated)
    Docker

    NodeJS
    Python
    HomeBox
    XPipe
    PiHole
    Prometheus
    Grafana

    * not in gallery of printable sticker images





  • ChaoticNeutralCzech@feddit.orgtoSelfhosted@lemmy.world•My self hosted badges of honor
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    edit-2
    9 months ago

    FOSS source is here.

    The second “S” in “FOSS” is “software”. You did not publish software, just its output: bitmap assets needed to print the stickers. Thanks for CC-licensing your creative work but source would mean showing what’s under the hood. We don’t know how you sourced the images used in each triangular tile: generated to best correspond with AI? Matching pieces from Wikimedia Commons photos?

    Edit: Look closely at Arch for example. It’s clearly just the logo placed in a hexagon, approximated by a mosaic of 24 triangles with AI images of differing quality. Is that snow or whipped cream? How can PCB traces be as blurry as watercolor and go nowhere? At least they’re topical: for Arch the prompt was probably “mountain OR architecture OR arch OR technology”.

    Presumably, the process for each tile is this:

    1. you make some direct artistic choices to create the base image (place the logo in a hexagon, choose a background color, add a border)
    2. you make some indirect artistic choices: pick keywords/themes for the AI to use
    3. you use a script to divide the hexagon into 24 triangles (presumably with “overscan”)
    4. you use generative AI to stylize the triangles’ bitmaps according to thw keywords, perhaps regenerating bad output
    5. you use a script to reassemble the image

    To consider this open source, I’d expect you to at least post the scripts you used in steps 3 and 5. To consider this good open source, it should contain a guide detailing this process, best with examples. I’d expect the AI part will be “bring your own model” but you could tell which one you used and its settings.

    The idea is creative and “human” enough for me not to condemn it. “FOSS” or not though, you should disclose use of AI, especially since you’re selling the printed stickers.


  • ChaoticNeutralCzech@feddit.orgtoSelfhosted@lemmy.world•My self hosted badges of honor
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    edit-2
    9 months ago

    Edit: yup, it’s made of AI images


    This is not an AI-generated pic, it’s a photo taken with a real camera. The logos, however, are hexagons divided into 24 triangles each, and these triangles contain often thematically related (e. g. lions for Brave) photos or photorealistic AI images (the info I found online does not state either way) cropped to best correspond to what the triangle would contain if it just had the original logo. Basically, that corner of the whale surrounded by white was taken from a face photo (or AI pic).


  • ChaoticNeutralCzech@feddit.orgtomemes@lemmy.world•Cursed plumbing
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    10 months ago

    I would get headaches from watching PAL (50Hz) CRT TVs for a long time. 60Hz monitors were noticeably better, and 75 or more was good to endure all day. Modern screens don’t go blank between refreshes (except PWM-based AMOLED) so the refresh rate is mostly irrelevant unless you want to shave off a few milliseconds of latency for serious gaming (then it’s best to match the refresh, render FPS and video signal).

    But as I’m walking down the street and move my eyes, I notice cheap lighting whose drivers don’t smooth the 100Hz ripple of rectified AC. Especially if they reach 0% brightness during the ripple. This applies to:

    • sodium and mercury vapor lights in street lamps
    • single-board (aka mains-voltage) LED modules in cheap, powerful reflectors
    • any LED bulb or fixture with a constant-current driver whose mains smoothing capacitor is too small or has failed due to heat (however, some such as EMOS and Solight spherical 18W ones refuse to turn on if the capacitor gets too bad, making for an easy repair)
    • any dimmable light powered from DC (like 12V and 24V non-addressable LED strips with those cheap flat remotes, or multi-mode flashlights) whose manufacturer was too cheap for a constant-current driver (fair enough) but could have very easily set a higher PWM frequency YET DIDN’T and therefore deserve a PWM shower.
      • This is especially annoying with RGB ones because the hue changes during the cycle, creating off-color fringes or even “rainbows” when moving my eyes. I can’t believe some people use things like that in/on/around their battlestation: this would totally distract me as my eyes dashed around the monitor while gaming.
    • multiplexed displays, especially with low duty cycles (look up charlieplexing, chances are your powerbank or similar gadget uses that to minimize the pin count of its chip) - these are usually over 100 Hz though

    So yeah, it’s not unhealthy, especially above 60 Hz. But it’s annoying for me to look around badly smoothed Christmas lights. And if they are of different phases (this is uncommon for Christmas lights (and even impossible in most American homes because they have 180° aka split-phase 240 V, not 120° 400 V) but always the case with multiplexed displays), I say a long rolling R to vibrate my face and see them wiggle.




  • I did’t know much about the German keyboard layout but I know the Czech one, which is derived from it (we both use QWERTZ) and was able to look up most of what I didn’t know.

    So, the keyboard has 4 layers: default, Shift, AltGr, AltGr+Shift (the fourth one is not standard but is recognized by xkb; in Czech I use it for custom character mappings, in German it is standardized but Linux-only).

    • Default layer prints lowercase letters a-z and äöüß, numbers and the symbols in the lower-left of each key.
    • Shift layer prints uppercase letters A-Z and ÄÖÜ and symbols at the top left of each key.
      • Caps Lock only affects letters. I don’t know what happens when you press ß with Caps Lock on a system too old to know about ẞ (only in Unicode since 2008, and “allowed” in German since 2017) and I don’t want to make vintage computers explode at 39c3.
    • AltGr layer prints lower-right symbols, most of which are only populated in a later version of the layout.
    • AltGr+Shift (Linux only) prints upper-right symbols.

    As you can see, AltGr+2 produces ², and AltGr+3 produces ³. I think the full-size “2” and “n” are misprints. My old Czech keyboard has some errors too. Edit: found out why there is “n” printed: the keyboard layout was designed for the OEM 850 code page that includes “ⁿ” but not “³”.

    By the way, Czech is more chaotic:

    • we have lots more diacritics so the number row only prints numbers on its Shift layer (most people therefore use the numpad only)
    • to print rare diacritics (ó, ď, ť, ň, and German ä, ö, ü), one has to first press the corresponding modifier key (´, ˇ, ˚, ¨) like on typewriters
      • an alternative for common capital diacritics (á, é, ě, í, ú, ů, ý, ž, š, č, ř) is to briefly turn on Caps Lock (advantage over typewriters)
      • pressing the ˚ key twice prints the degree sign (°) twice (Windows) or once (Linux)
    • there is a bloody dedicated § key but we need to press AltGr+7 twice, then backspace (or Alt+96) for a grave (`), which is part of ASCII and used in Markdown
    • physical keyboards almost always reserve the right side of the keys for the English-US layout (very confusing for novices) so one has to type in the AltGr layer blind (except for €); it contains useful symbols ([]{}<>|\€$@#^&×÷`) as well as useless ones (Đđ – these are Slovene, why not the Slovak Ôô?), leading people to prefer Windows-only left-Alt+numpad codes (such as Alt+64 for @) that use the obsolete OEM-1252 codepage (the Unicode extension has to be enabled via registry and Alt+letters hex codes get passed to programs anyway, often defocusing the input element). I only found a Slovak one on Wikimedia Commons
    • some lazy manufacturers combine the Czech/English and Slovak/English layouts, which are similar except ľ, ť and ô, leading to 5 (!) symbols per key, 3 of which are irrelevant unless you switch layouts
    • Gboard for Android offers QWERTY for Czech, which looks normal (hold for diacritics, potentially swipe for ě and ů) and the unpopular QWERTZ-PC, which has all the physical keyboard’s quirks, but its “Czech QWERTZ” is based off German QWERTZ, containing ú and ů but not the other diacritics for some reason. All other keyboard apps with Czech language layout get this right (hold for diacritics, potentially swipe for ě and ů)!

    Edit: found out why there is “n” printed: the keyboard layout was designed for the OEM 850 code page that includes “ⁿ” but not “³”.