Dat lijkt me een goed idee :)

If you have to ask if something is legal, the answer is likely no. When the answer actually matters, consult a lawyer. For the record, I’m not one and don’t pretend to be one on the internet.

Further down the article it talks about why it’s that colour.

What’s even more remarkable is that someone actually did that, in January 1998.

https://en.m.wikipedia.org/wiki/Bliss_(photograph)

So … hot air doesn’t float … that’s a thesis right there.

So … hot air doesn’t float … that’s a thesis right there.

I understand.

I’m not trying to discredit your response, just pointing out that this is not a trivial problem to solve and any quick solutions are unlikely to make this easier for anyone involved.

For example, if you do burn a new DVD as suggested, you just created a versioning and distribution issue for yourself and your loved ones.

Before you start consolidating, consider what might happen if the switch is in an unexpected state. For example, someone turned off the heater or pump and you were expecting it to be on.

In other words, you need to consider what a “safe state” is for each thing and how your code, when it fails, reverts to that state. This is an example of “failsafe”.

Note that I said “when it fails”. This is true for all software, even on mission critical systems.

Source: I write software for a living.

Yes, this is an option. It requires that your password(s) don’t change. Setting up a password store somewhere and granting access to it using this method is a potential solution, but not great.

I have previously looked at this as one potential solution, BUT it requires that bitwarden exists when you die and the page that you link to states: “If your premium features are cancelled or lapse due to failed payment method, your trusted emergency contacts will still be able to request and obtain access to your vault.” – what it doesn’t do is state for how long, or what happens if they access it before you die, let’s say while that you’re on holiday away from the internet for a period exceeding the “wait” time, which is an issue in its own right, how do you deal with access where you’re no longer available, since you’re dead, but the access needs to happen NOW, to pay the electricity bill, or something else.

Additionally, the system requires a level of skill that’s not evident in most non-computing users (from the same page): “Trusted emergency contacts must be existing Bitwarden users, or must create a Bitwarden account before they can accept an invitation.” – which means that now they need to get a “computer person” to help, which introduces even more risk.

Don’t get me wrong, I’m not saying that attempts at solutions are non-existent, it’s that they are clunky at best and in my experience horrendous in general use – for example, look at what happens when one of the signatories of a joint account dies – the account is automatically locked – sometimes for years – even if that account is what’s paying for food and lodging for both parties. All because we haven’t made systems that make sense, despite the guaranteed event of our death.

As I get older this conversation has become increasingly bewildering. We are all guaranteed to die, but we still treat it as an exception, which as a programmer makes no sense to me at all. I’ve seen the fallout of people dying for much of my life and we still get no better at it. Why is that?

I’ve been attempting to come up with a way to do something “simple”, create a foolproof way to share my credentials with appropriate people in such a way that they can access what they need to after I die. So far an actual solution has eluded me. This is just one example of what I’m talking about.

The article raises questions about what end of life might look like for an individual, I think that’s part of the conversation. Ultimately after your death, it’s not your concern any longer and anything you can do to alleviate the stress would, at least in my opinion, be a good thing. Having a good time, well, a the best time you can have until then, is absolutely part of the equation.

Anyone?

Removed by mod

To get a sense of just how bad this is, Sports account for 1% of global GDP, Science accounts for 2%.

Now compare how much coverage the daily news broadcast has for either.

These are job titles I’ve actually used:

• Brain for Hire
• Elephant header
• Janitor
• Troubleshooter

Over the past 25+ years I’ve worked for myself and whilst doing the exact same job, fixing complex ICT problems for my clients I’ve had to complete job title fields in countless corporate forms.

It’s fun to interact with colleagues who get the joke and hilarious when they don’t.

There’s a reason why there’s only privileged write access to /dev/sda.

If you run unknown software as root on any computer you get to experience first hand the impact of: “fuck around and find out”.

All fine and dandy … got any realistic alternatives?

I can absolutely guarantee that you are not the only person to have spent quality time getting to know the intimate backwaters of a codebase tracking down a bug that you introduced whilst tracking down a bug.

Source: I’ve been writing software for over 40 years.

From the article:

A Microsoft spokesperson confirmed the company has been aware of the issue since at least August 2023, but maintains that changing the behavior could break compatibility with existing applications.

• Changing your Microsoft or Azure password does not immediately revoke RDP access for old credentials.
• There are no clear alerts or warnings when old passwords are used for RDP logins.
• Microsoft’s security tools, including Defender and Azure, do not flag this behavior.

So … this article published today, 5 May 2025, says that the Microsoft policy will start on 5 May 2025.

Some questions:

1. When did Microsoft announce this and where?
2. Is this a reasonable rollout timeline that affects pretty much anyone on the planet who does email?
3. As a society we run most of our activities through Google and Microsoft. At what point does this get classified as a utility and get regulated.

You should consider that snafus with paperwork have undoubtedly happened for as long as there has been a border between the two countries.

It’s not the paperwork that’s the issue.

It’s the harrassment and incarceration that’s the problem.

Consider this: If family coming to Canada isn’t a concern, why not go and see them instead?