home.social

#lossypng — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #lossypng, aggregated by home.social.

  1. @amin @axxuy

    I got the cert warning on both my phone and my computer :/

    (With my phone's wifi turned off)

    #LossyPNG

  2. Further experimentation into #9front...

    ...I still feel like I landed on Mars, but I've just now (finally) managed to walk in a straight line for ten paces without landing on my face, so... XD

    #Plan9 #ThePlanFellOff #TheFrontFellOff #UnixSurrealism #PostUnix #WhatAmIDoingHere #AmIKoolKidNAO? #ReadTheHashTags

    #LossyPNG: original 40-color image reduced to 23 colors for a reduction down to 65% of original size, only losing some of the colors in stats(8) display.

    Yeah. ;) (text after hashtags to force clients to fully display them, because [hashtags are poetry], dadgummit! ;)

    P.S. Bitmapped fonts are SOOOO CLEAAAAAN. Dude. XD

  3. mini-rant

    I guess I'd be less annoyed if a reboot-to-apply-changes cycle didn't mean that I'd have to enter my LUKS password twice.

    #Linux #LossyPNG

  4. I really must confess, after all of the insane #UI stuff we've been seeing lately, I really don't hate this (UI, that is).

    #LossyPNG

  5. @wyatt @kawa There have been a few attempts at "lossy PNG". One method, anticipated by the standard, involves reducing colors in a continuous-tone image to store it in indexed mode. The other involves adjusting pixels of 24-bit images to be better predicted by PNG's line filter, giving more zero bytes for DEFLATE to use

    Indexed: pngquant.org/
    Blurizer: github.com/kornelski/mediancut

    #png #LossyPNG #pngquant #ImageCompression

  6. It's really something that my e-reader has better and more usable scrollbars than most desktop interfaces (Windows, MacOS, and Gnome). :/

    The scrollbar is thin, but the grabbable region is large (kind of like the default in KDE), and easy to manipulate directly with your finger. This is actually better than #iOS' implementation, and many #Android apps.

    #Kobo #UI #UIDesign #LossyPNG

  7. If anyone's curious why I'm always doing the little #LossyPNG dance, it's because you can get some crazy good compression sacrificing color depth, instead of using a traditional lossy algorithm which gives you good compression by sacrificing detail:

    tmp $ ll kate*
    -rw-rw-r-- 1 rld rld 124,117 Feb 23 12:51 kate-kwrite1.png
    -rw-rw-r-- 1 rld rld  23,710 Feb 23 12:51 kate-kwrite2.png
    -rw-rw-r-- 1 rld rld  19,936 Feb 23 12:54 kate-kwrite3.png
    -rw-rw-r-- 1 rld rld  18,572 Feb 23 12:55 kate-kwrite4.png
    186335 total
    tmp $ colors kate*
    kate-kwrite1.png     (unknown)
    kate-kwrite2.png     16
    kate-kwrite3.png     9
    kate-kwrite4.png     8
    

    (kate-kwrite1.png was the original (truecolor) screenshot)
    (kate-kwrite2.png was automatically reduced to 16 colors by ImageMagic)
    (kate-kwrite3.png was reduced to 9 colors by hand-picking dominant colors in GIMP)
    (kate-kwrite4.png was reduced to 8 colors by hand-picking dominant colors in GIMP)

  8. @moses_izumi

    > I wonder if someone's already built a graphical environment where most of the apps are TUI stuff launched from desktop/XDG-Menu shortcuts.

    Sounds like most tiling wm enjoyers' workflows, honestly. I'm attaching a photo of my own #sway setup and launcher (fuzzel)

    > One thing I appreciate about DOS that the entire bootup/sytem configuration process is contained to two moderately long textfiles.

    You should look into the various BSDs' init systems. They're relatively simple, and elegant.

    > Never looked into the Linux init system debates, as the average Debian (and derivatives) install tends to work well enough out of the box.

    *sigh* init system debates are usually about as productive as debating reproductive health issues, and about as polarized/unreasonable.

    > The main thing that makes a program "bloated" in my book (beyond the use of heavy foundations/frameworks like Electron or whatever) is the practice of having a splash screen to mask loading times.

    #LossyPNG

  9. WHAT.
    THE.
    FORK.

    Up and down (increment/decrement) arrows for account numbers.

    WHAT.

    #LossyPNG

  10. I love how the #WebP "preview" that #GoToSocial generates is 3.77x larger (file size) than the original 16-color #LossyPNG. 😄

    [WebP] (56,212 bytes)
    [PNG] (14,907 bytes)

  11. New #blog post: Why You Need A Stack of Thinkpads

    https://rldane.space/why-you-need-a-stack-of-thinkpads.html

    Thankful to Nanoraptor/Dana (will tag her elsewhere) for inadvertently reminding me to write this down. XD

    Welp, I'm back in the saddle, I guess? Writing this gave me some nummy dopamine, so thank God for that!!!
    Also, man is imgur ever a dreadful webshite. Just horrifying to use. XD

    cc: my wonderful #chorus: @joel @dm @sotolf @thedoctor @pixx @orbitalmartian @adamsdesk @krafter @roguefoam @clayton @giantspacesquid @Twizzay @stfn

    (I will happily add/remove you from the chorus upon request! :)

    #rlDaneWriting #blost #Thinkpad #Thinkpads #Linux #BSD #RunBSD #eWaste #LossyPNG (in the blost)

  12. #filter time!

    Suggestions welcome!

    #MentalHealth #filters #LossyPNG

    cc: @ossobuffo @gumnos

    P.S.: updated list, (WW) means whole word:
    trump(WW)
    maga(WW)
    fascist
    nazi
    fash(WW)
    ukraine (I'm sorry)
    israel (NOT sorry)
    elon(WW)
    zuckerberg
    tim cook(WW)
    Microsoft

  13. Woot, my #Commodore #64Ultimate came in the day before Christmas, and I didn't even realize it!

    I'll have to wait a few days to order a monitor for it, and to clear off some space on my desk, first.

    #C64 #C64U #LossyPNG

  14. I created a syntax highlighting config for my programming language Slang, for GNOME 's GTKSourceView :D

    This will make working on my videogame much more comfortable I think 😊

    gitlab.com/golemwire/subsky/-/ (XML warning)

    (an @rl_dane hashtag lol. I had changed the DPI in so I could capture larger screenshots, and I think my NVidia driver might be breaking the Wayland xdg-output protocol, so its scaled funny)

  15. The almost perfect #Gaussian distribution here tells me I might have actually structured a #poll correctly. ^___^

    #LossyPNG

  16. Since the #PNG spec is getting some updates, I was thinking... you know what would be sick? Baking classic #lossy compression right into PNG.

    I don't mean #JPEG or anything like that. Not even the #LossyPNG scheme I enjoy using where I reduce the number of colors to reduce the entropy. That wouldn't need any changes to the spec.

    I'm thinking #Amiga HAM modes! Instant 3:1 (well, 2.4:1) lossy compression with (hopefully) minimal artifacting. That would be SICK!

    Makes me want to throw together a Python script or something to read PNG files, apply the HAM "compression," and then see how the output looks. It wouldn't provide much compression savings with regular PNG, it would need a change to the format. But since I never had an Amiga, I'm curious to see how it looks, and how well it might scale to modern image resolutions.

    Conceptually, it's not much different than 3:1 horizontal chroma subsampling, but might actually look a lot better.

    Quick explainer: instead of having a 24-bit-per-pixel image, you have a 10-bit-per-pixel image, where the first two bits are a mode selector, and the last 8 bits are the actual pixel data. The modes are Hold and Modify{R,G,B}. Modify{R,G,B} modify just the red, green, or blue component of the 24-bit color for that pixel with the 8 bits specified. The modify mode assigns that pixel to be equivalent to the 8-bit value from a pre-defined palette or some pre-defined bit-assignment mode like RRRGGGBB or something. So basically, the horizontal color resolution is divided by 3, but sometimes you get lucky and there's no noticeable loss.

    #HoldAndModify #Imaging

  17. with a classic skin is giving me serious late-1990s feeeeels. XD