[–] 1 point 1 hour ago

I don't know, maybe it doesn't work for people who are used to working with RGB colours.

#00FFF5 is and looks (to me) blueish green, #00F5FF is and looks (to me) greenish blue, anything in-between is up to calibration issues, or turquoise for short.

Maybe I've unwittingly trained myself to judge colours as objectively as possible regardless of what screen they're being shown in, I don't know.

Maybe it would be different with paint, but most computer screens have green pixels and blue pixels (and red ones), and simulate colours using those, so it's relatively easy to tell if it's biasing one way or the other.

Given an RGB screen maybe it'd be better to compare a gradient between, say, cyan and magenta, for instance, which combine different pixel colours.

I don't know, I'm not a neurologist or a colour theorist, just someone who's spent way too much time picking the right RGB values for UIs or documents to look adequate.

  • source
  • parent
  • context
  • [–] 9 points 6 hours ago

    People condemned to the death penalty are generally not existential threats to humanity. It's safe to simply keep them where they can do no harm.

    Financially obese parasites, on the other hand, are existential threats to humanity, so, while the death penalty is morally abhorrent, they must be put down to ensure the survival of civilization and the human race as a whole.

    Forced to choose between two bad options (murder or extinction), we can only choose the less abhorrent one.

    Of course, though, this obligation doesn't justify or absolve the crime, it just makes it necessary, an existential imperative. Whoever commits it should still face justice.

    (In Luigi's case specifically, he shouldn't be absolved because his alleged victim was objectively a cancer on society and it's death made the world slightly less worst, but because there's a reasonable doubt that the evidence against him might have been fabricated.)

  • source
  • [–] 9 points 6 hours ago* (2 children)

    Why isn't there a “this is turquoise” option?

    Or the possibility of marking it as both green and blue? (Or neither, whatever floats your boat.)

    RGB #00FFFF is objectively as green as it is blue (well, in my screen the midpoint at which I'd be more likely to call it green seems to be at or around #00FFF5 ± 5, but that's probably due to the screen being imperfect)... it makes no sense to call it (or sufficiently close hues) one or the other...

  • source
  •  

    Bug Report

    Describe the issue:

    The font size of the comments appears to be random (see attached screenshot).

    The global and comment font size settings don't seem to have any effect.

    It doesn't seem to correlate with comment length, depth, age, score, or any other variable I can think of.

    I just updated the app and it's still happening.

    Steps to reproduce:

    1. Open a post's comments.
    2. Scroll. Unfold folded comments.
    3. Notice the rich variety of font sizes.
    4. Struggle to read the smaller ones because you're not as young as you used to be.

    Device Information

    • App Version: 1.0.344 (344)
    • Platform: android
    • OS Version: SKQ1.220303.001 test-keys
    • Notice: Using legacy Shared Preferences

    Modified Settings

    The following settings have been changed from defaults:

    • alwaysShowInstance: true (default: false)
    • alwaysTrustDomains: true (default: false)
    • shouldUseHighRefresh: false (default: true)
    • shouldShowPageNumbers: true (default: false)
    • mediaSecondaryAction: download (default: none)
    • isVolumeNavigationEnabled: true (default: false)
    • shouldAlwaysDisplayAvatars: true (default: false)
    • shouldHighlightNewComments: true (default: false)
    • nsfwView: show (default: blur)
    • applyNsfwInCommunities: false (default: true)
    • cardType: fullwidth (default: card)
    • postActions: [comment, save] (default: [comment, save, none, crosspost])
    • shouldCombineMarkdownImages: false (default: true)
    • shouldRemembercommentPosition: false (default: true)
    • shouldDimBrightBackgrounds: false (default: true)
    • shouldForceBlackImageBackground: false (default: true)
    • textSizeMultiplier: 1.25 (default: 1.0)
    • maxCacheSizeGB: 1 (default: 2)
     

    Bug Report

    Describe the issue: Images are loaded at extremely low resolution.

    Steps to reproduce:

    1. Find a post with an image, preferably with text.
    2. Touch it to open it full screen to see the details or read the text.
    3. Observe the meagre amount of pixels (see example above).
    4. Squint to try to read the text.
    5. Fail due to pixel insufficiency.
    6. Despair.
    7. Touch “open external” to open the post on the browser (https://mander.xyz/post/43475080 for the attached example).
    8. Open the image in the browser.
    9. Marvel at the difference in resolution compared to the one opened in the app.

    Device Information

    • App Version: 1.0.298 (298)
    • Platform: android
    • OS Version: SKQ1.220303.001 test-keys

    Modified Settings

    The following settings have been changed from defaults:

    • alwaysShowInstance: true (default: false)
    • alwaysTrustDomains: true (default: false)
    • shouldUseHighRefresh: false (default: true)
    • shouldShowPageNumbers: true (default: false)
    • mediaSecondaryAction: download (default: none)
    • isVolumeNavigationEnabled: true (default: false)
    • shouldAlwaysDisplayAvatars: true (default: false)
    • shouldHighlightNewComments: true (default: false)
    • nsfwView: show (default: blur)
    • applyNsfwInCommunities: false (default: true)
    • cardType: fullwidth (default: card)
    • postActions: [comment, save] (default: [comment, save, none, crosspost])
    • shouldRemembercommentPosition: false (default: true)
    • shouldResolveOpenGraph: true (default: false)
    • shouldDimBrightBackgrounds: false (default: true)
    • shouldForceBlackImageBackground: false (default: true)
    • maxCacheSizeGB: 1 (default: 2)
    Example of a mangled image.
    view more: next ›