• 1 Post
  • 28 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle




  • They could be upgrading hosting infrastructure - sometimes this requires servers to be shut down or restarted. They might also be applying database changes such as migrating data from one server to another, or updating the structure of the database to improve performance or support new features.

    Honestly, there are quite a number of reasons for planned downtime.

    Unplanned downtime is a different story. Usually that’s because something unexpected went wrong and there will be engineers trying to get things back up and running ASAP.








  • One really practical way to learn some new recipes is to use a recipe box service like HelloFresh or Gousto.

    They deliver a box with all the required ingredients and easy to follow recipe cards.

    For anything that you make & enjoy, you can keep the recipe card and cook it again using store bought ingredients.

    These recipe boxes regularly have deals and promotions (e.g. 60% off, refer a friend, etc.) so it doesn’t have to be too expensive.

    Or if you don’t want to order one at all, it’s worth knowing that HelloFresh make all their recipes available online for free. So you can download and print off any that you like the sound of, without ever even ordering one of their boxes.







  • To be honest, I think whichever approach you take is unlikely to have a significant effect on how much energy your website uses overall.

    For example, servers in datacentres are very powerful and are able to run more than one thing at once. So if you were hosting your own Lemmy/Mastodon instance, there’d be no reason why you couldn’t also host a standalone website on that same server. The difference in energy usage would be negligible.

    In contrast, you could argue that Lemmy is less efficient than a straightforward static website because the content of your blog posts will inevitably end up being federated to many other instances. That means multiple copies of your blog will be transferred between multiple servers and stored on multiple hard drives, etc. Whereas a static website lives in one place and doesn’t end up using so many resources.

    At the end of the day, whichever you choose will likely have very little impact. So I wouldn’t worry too much about your blog’s green credentials.

    I’m saying this as somebody who is pro protecting the environment, but also pro prioritising our efforts in the places they’ll have greatest impact. You’ll probably have a bigger impact by walking to the store instead of driving.




  • I do think Firefox gets a degraded experience on some websites.

    For example, Google Meet supports virtual video backgrounds and 3D face filters for Chromium based browsers.

    And Google Search serves up an older results page design with fewer features to Firefox users. Someone has literally had to create a Firefox addon to make it pretend to be Chrome so it gets the modern results page.

    I realise these are both Google-owned websites - but I don’t think it’s accurate to say that the average user isn’t going to come up across these differences.