[–] 7 points 2 days ago

Fun fact: "nuclear" comes from the Latin nucula, 'little nut'. The c and l being adjacent in modern forms is due to metathesis, the same process that results in some people pronouncing "ask" as "ax".

  • source
  • [–] 9 points 1 week ago* (last edited 1 week ago) (4 children)

    I will say that I don't understand their repeated assertions that sexuality is a choice. I don't see how anyone could believe that unless they're actively repressing something.

    But I don't know where that disconnect lies. Is it just a bad faith argument, and they don't really believe that? Do we have a fundamentally different understanding of what sexuality and sexual orientation consist of?

    Edit: spelling

  • source
  • parent
  • context
  •  

    I'm trying to write a package for the Zen Maru Gothic font, which is available on Google's font repository on github. (https://github.com/google/fonts) It's a huge repo with thousands of fonts, so I'm trying to use sparseCheckout to grab only the part I need:

    src = pkgs.fetchgit {
       url = "https://github.com/google/fonts.git";
       rev = "v0.4.9";
       sha256 = #snip long hash;
       sparseCheckout = [ "ofl/zenmarugothic" ];
    };
    

    I was originally using fetchFromGitHub pointed at the same repo. In both cases, what's actually being fetched into the store seems to be the root directory of the Google Fonts Axis Registry repository (https://github.com/googlefonts/axisregistry) which has a different url, name, and owner.

    I feel like I'm going crazy.

     

    Example of behavior: https://discuss.online/post/35408836

    In a browser, the post body contains two spoiler tags, the first is some text, and the second is an additional image. In the app, the image gets combined into the gallery, but the text is nowhere to be found.

    Also the "Combine markdown images to gallery" setting doesn't appear to do anything; even with it turned off, the image gets combined into a gallery and the text is still missing.

     

    Bug Report

    Describe the issue: The post in question:

    https://discuss.tchncs.de/post/53330380

    That's the url as connect copied it from my feed view in Connect, but I imagine my experience actually involved the federated copy on Beehaw. [Edit: the tchncs.de link crashes also.] A couple of attempts looked like the app was trying to throw up an error message of some sort, but it crashed back to the launcher so quickly I couldn't read it.

    Device Information

    • App Version: 1.0.372 (372)
    • Platform: android
    • OS Version: BP4A.260105.004.E1
    • Notice: Using legacy Shared Preferences

    Modified Settings

    The following settings have been changed from defaults:

    • isCommentActionsReversed: true (default: false)
    • alwaysShowInstance: true (default: false)
    • alwaysTrustDomains: true (default: false)
    • commentTextStyle: bodyMedium (default: bodyLarge)
    • enableCommentNavigator: true (default: false)
    • shouldHighlightNewComments: false (default: true)
    • isImageVerticalSwipeToClose: false (default: true)
    • nsfwView: show (default: blur)
    • applyNsfwInCommunities: false (default: true)
    • cardType: list (default: card)
    • shouldResolveOpenGraph: false (default: true)
    • shouldDisplayCommunityBanner: false (default: true)
     
    • With "force full-size thumbnails" disabled (the default) most thumbnails fail to load

    • With "convert to webp" enabled (the default) most images fall to load in app, but work in an external browser

    As an aside, is there an "open external" anywhere when viewing an image? It used to be in the three dot menu, but I don't see it now.

     

    It used to be that pressing the back button while in the settings menu would take you back to where you were before. For the last several versions, it would instead unceremoniously exit the app. I see from the notes for 271 that an exit prompt has been added, seemingly cementing what I would have considered the root bug. (i.e. that it exits at all rather than just going back)

    So how are we supposed to leave the settings menu if not the back button?

    view more: next ›