• Annoyed_🦀 @monyet.cc
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    1 year ago

    Was supposed to hike this morning, but i forgot i told my mom we gonna go visit my sister’s new shop so hiking postponed 🙈

    Too bad because the weather is really nice today after a few days of raining, but ehh it’s a nice day to go out as well

      • zen@monyet.cc
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        1 year ago

        sorry, i posted it in hopes of getting some replies from apple users, but i don’t have any apple devices myself.

        anyway, since utm is using qemu under the hood, i wonder how easy is it to run plain qemu on ios…

        by the way, today’s daily thread is so low traffic!

        • |💀|@lemmy.aerir.xyz
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          All good no worries, I am a new macOS user myself and using UTM for desktop VM. Unsure how that is used in mobile environment.

          • zen@monyet.cc
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            that’s interesting. what were you using before macos, and why did you decide to switch?

            as for utm, are you running windows or linux on it?

            another foss virtualization project for mac that i’ve come across is xhyve, but that doesn’t seem to be receiving updates lately.

            • |💀|@lemmy.aerir.xyz
              link
              fedilink
              arrow-up
              1
              ·
              1 year ago

              Mainly Windows, tried many flavors of Linux desktops before as well but the need of troubleshooting random problems have really put me off. My main PC still runs Windows, macOS for work laptop.

              Running Windows in my UTM, not really using it but just in case :)

              • zen@monyet.cc
                link
                fedilink
                arrow-up
                1
                ·
                1 year ago

                which flavors did you try?

                and what problems did you need to troubleshoot (probably graphics cards?)

                • |💀|@lemmy.aerir.xyz
                  link
                  fedilink
                  arrow-up
                  1
                  ·
                  1 year ago

                  All the common ones, including Arch (of course) :P

                  Ye I am using Nvidia, so that didn’t help. Usually I’ll hop into Linux distro every year as my attempt to move away from Windows, the most recent issue I can recall is mixed monitor refreshed rate not playing well ie. 144hz + 60hz monitor combi.

                  By default, X11 uses the lowest refresh rate and apply that to both screens - OK fine. Then I switched to Wayland, the refresh rate issue gone but I noticed some apps, including Discord doesn’t seem to play well, random flickering and shits. Switched back to X11, managed to fix the issue after hours of Googling. At that point, I was like meh - too much effort to get things to work for Linux. Back to Windows for my day-to-day usage, especially gaming.

  • dukeGR4@monyet.cc
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    when would OLED tech reach maturity and become mainstream within the TV/Computer monitor scene? still so expensive tho…

    OR is it gonna be like full-frame camera sensor whereby it would never ever reach mainstream and always priced at a premium?

    • munkkey@monyet.cc
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      There aren’t many OLED manufacturers making screens bigger than phones, and yields are usually lower than LCD panels. Perhaps in 10 years the display landscape will change enough to make OLED more widely used.

      • dukeGR4@monyet.cc
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        I think there are not that many tech manufacturers in general… camera sensors, computer chips, lithium battery… can all be traced back to a handful of manufacturers

        With continual investment on newer tech and political will I think it’s possible the drastically increase output.

  • ruk_n_rul@monyet.cc
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    1 year ago

    Lemmy.world is upgrading to 1.18.3 tomorrow. Apparently list results are going to change drastically.

    We got ETA on our own upgrade?

    p.s. it’s looking like the bawang bouquet about to be picture of the week tomorrow.

    • zen@monyet.cc
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      there will be at least 5-10 minutes of downtime for db migrations though (more if the db size is huge). of course, after the long migrations the db size is reported to shrink significantly.

      anyway, there’s already been at least 2 easily triggered/discoverable bugs:

      • view context for comments does not work properly (i heard it may even crash jerboa)
      • all software versions in the instances list are displayed as 2.0

      hopefully they will release a 0.18.4 quickly with fixes for that.

      • zen@monyet.cc
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        i’m still seeing 0.18.2. by the way, are you still using lemmy easy deploy on your rpi4?

        • |💀|@lemmy.aerir.xyz
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          1 year ago

          Yes, been working fine. Again this is just a ‘fun’ attempt, if it goes down - I can always jump to another instance edit - alamak, of course is 18.3 for me cos i’m viewing from my own instance.

        • zen@monyet.cc
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          i think every up/down vote federated event is stored in the database for 6 months or something, so it’s probably true that instance owners have access to that info

        • zen@monyet.cc
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          1 year ago

          if you are subscribed to lots of communities, it is not surprising.

    • Annoyed_🦀 @monyet.cc
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      After some discussion within the admin team, i think we’ll have a wait and see approach in this since we’re a small instance and any problem have a chance of driving newcomer away. Besides, we don’t actually in critical need of the database optimisation in this new update, but the potential issue that might popup mean it will be a pita to keep track. Since World commited to the update we’ll see if there’s any real big issue coming up(like that security breach stuff after updated to 0.18 lol) before commit to the update.

      • zen@monyet.cc
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        don’t scare our admins 😱

        monyet already has a dev instance, so they can import the db from the main instance there, and do the db migrations to see if that’ll succeed.

        precautionary measures can be taken on the dev instance so it doesn’t attempt to federate with all the data from here.

        i can think of (for testing out db migrations on the dev instance):

        • run lemmy_server with the --disable-scheduled-tasks cli flag, which will prevent background federation tasks from running (so federation events will only be triggered by actual interaction, like posting, voting, subscribing, and of course such things should not be done on the dev instance)

        • if that’s still not enough and we want to be extra sure the dev instance doesn’t federate with data from over here, then just block outgoing http/https connections at the firewall while doing the db migrations try-out (also don’t run lemmy-ui and just watch the docker logs for it to say migrations completed successfully)

        i think the lemmy.zip admins said they’re still trying to work out a way to spin a dev instance on a dedicated server, but monyet already has a dev instance, so the db migrations can be tried first to ensure safety.