• 533 Posts
  • 6.2K Comments
Joined 2 years ago
cake
Cake day: June 2nd, 2023

help-circle
  • I guess I’m not the only one, but I haven’t heard of this before. It seems hospital rates have been a thing for a long time (the sickness benefit hospital rate was 26.98 in 1998).

    What’s the reason for this policy? I get that if the tax payer is paying for your stay in hospital then they may not want to also be paying for your house elsewhere, but is forcing you to end the tenancy so you have no choice but to stay in hospital really going to help? Or is it supposed to be a threat (leave hospital or you will lose your house)?

    How many people stay in hospital longer than 13 weeks? I can’t imagine the cost is significant compared to the overall welfare bill if we keep paying people so they have less to worry about.



  • The main thing covered is the actual chain of events from the “black box” (my word for it) transcribed from the voice recordings from the report.

    Yeah I think you’re right. All this stuff:

    Basically there was a lack of training, the crew didn’t figure out that the ship was still on autopilot until it was way too late.

    The Crew had control of the throttle but not control of the helm direction. So when the crew thought they were doing a full reverse they were actually making the problem worse. The crew went up to 100% throttle because they thought they had changed helm direction but in reality they we’re just getting to the reef quicker because autopilot still was in control of the direction of the ship.

    They didn’t follow procedure didn’t check if the autopilot was off and didn’t discover this until after they had hit the reef

    Was in the video about the initial report. I think what it didn’t have is the transcripts that provide that next level of detail.

    It will be interesting to see what happens with this (if anything that we hear about). While you could place some blame with the commanding officer, it seems from this that the bulk of the blame belongs higher up the chain.




  • I don’t have a Pixel 8 but that sounds highly unusual. I suspect you’re right, maybe the option didn’t exist in the same way on Android 14 and so it’s copied over in a weird way.

    I don’t know a way to fix them other than just updating them all one by one. In recent Android versions the app can prompt you if it’s missing the settings so it should be pretty safe to just disable it for everything that doesn’t obviously need background usage.


  • Whoever is running the Alexandrite frontend you are accessing definitely could modify it to steal your password, so it’s another point of trust. To help reduce this risk, many instances will run their own Alexandrite (and other third party frontends). With a quick search I didn’t find lemm.ee hosting any though.

    I believe OAuth support is planned for Lemmy but not sure on the timeline or the exact implementation.

    On the relay emails, I believe some instances block their use, but the benefit of having many instances is you can find one that aligns to your values.



  • There is currently no OAuth, which sounds like what you’re asking for.

    Currently you need to trust the app and your instance. Most instances are implementing off-the-shelf lemmy but there is no way to confirm that.

    Lemmy apps could steal your password if they wanted to, but if you use an open source app through say F-droid that compiles the apps from source, you can check the code if you have that skillset.

    Ultimately the answer here though is not to trust your instance or app, but to instead not need to. Your account should be treated as disposable and (like every other site) you should be using a unique password not used anywhere else.

    This way it doesn’t matter if your instance steals your password, since they already know everything you’ve given them. Lemmy is all public anyway so there isn’t much risk involved.

    I’d argue the biggest risk is if your instance requires email validation, and it’s easy enough to use a relay email (Firefox Relay, Simplelogin, Addy.io, etc) so that’s unique as well.










  • I think it is, and I’ve also seen it happen more lately as well. Though I feel like it might be that previously the UI would freeze where as after a recent update it seems to go to an error page more often.

    I know other instances have the issue (and have had the issue for a while as well), and have reduced the problem by deploying multiple containers for the UI. Hence why I’ve done it, hopefully it will help 🙂