• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle









  • Actually, we just entered spring, on late September. And we did so in the midst of a heatwave that broke heat records for this year - we had days with 37C, which is high even for summer, and it won’t be summer here until December.

    Yes, I’m scared af as well. My family is sort of ignoring my warnings and actually planning to move to the coast (Santos), which is even hotter.

    Some guys here in the comments said about migrating to the north, and that’s something that has been on my mind as well as a long term plan, although I find it unlikely I can move to North America in the short term, so I’m thinking more realistically maybe southern Argentina?



  • Same here. In fact, I bought my Legion (which btw I feel like it was a good choice on OPs part because I believe Lenovo’s laptops tend to have better cooling engineering in general, for whatever laptop category, compared to other brands) to serve first as a work laptop, and then some gaming on the side, which I’m not too picky about because I don’t really play on PC that often anyway. My reasoning for that is that the business laptops I had been looking before going with the Legion were frankly overpriced crap with limited expandability, shoddy components and build, and full of built-in bloatware pre-installed. I find that gaming laptops tend to have higher quality components and slightly better expandability, so it was a win all around.




  • Wikipedia and other places says 1984 - I think 1983 is when development started. I wasn’t quite sure how much RAM the BBC Micro had, so I played safe and went with the ZX Spectrum’s configuration, which I had, although thinking about it now, the way the Speccy mapped memory meant that it actually had about 32Kb useable RAM as well. I don’t know how the BBCM mapped memory, so I’m not sure if a similar situation applied (less actual available memory).


  • To properly qualify how groundbreaking Elite was for the time, for those who don’t know it: it was a space sim that simulated 8 galaxies with 256 star systems each, each system with a star, a planet, and a space station. All of that was wireframe-3D rendered, had a lot of complexities like different ship and enemy types, different playloops like trading, mining and combat, and it was one of the few games of that time that pioneered open-world gameplay.

    This was initially released on the mid-80’s for 8bit computers of the time, which had anything between 48Kb to 128Kb of RAM, and thus, the game binaries was also that small - they accomplished that by also being one of the few games of the time that pioneered procedurally generated content.




  • I don’t know about Jerboa, but this happens on the web too, and it’s usually on more fringe / less popular communities. There’s a workaround that works for me, I mostly heard about it from someone else here on Lemmy. It’s not great user experience, but it works.

    • Go to the search function;
    • Type in the name of the community, hit enter;
    • Select “Commnities” on the search type dropdown (yes, you have to do it after submitting the search as per the previous steps, seems like another UI bug);
    • If after doing the above the community is not found, then here enters the magic sauce:
      • Change the search terms so the community is fully qualified / keyed as !communityname@instance.server, all in lowercase. So, for example, if you’re looking for the “kreisvegs” community on feddit.de, type !kreisvegs@feddit.de on the search field;
      • Submit. It still won’t be found. Give it a few seconds, change back the search terms to only the community name (without the instace and “!” at the start). Submit. It should now show up.

    You may have to repeat step 4 onwards a couple times, sometimes.

    My uneducated guess as to what’s happening: the federated communities listing is probably cached on the instance, and by default it’ll only look for communities cached on your instance. My guess is that federated communities only gets into the instance cache when members of the current instance have searched / subscribed to that community. Typing the fully qualified community name on the search field (which is the tip I got from someone else) apparently forces the search function to actually contact the external instance to look for the community, instead of looking in the cache, but that can take some time, hence why you should wait a few seconds on the 6th step. That guess could also explain the problem also happening on Jerboa, since the problem would be server-side.