If they show up I hand out the candy and I’ve been doing it that way for decades. No telling some kid or teens situation in life and there’s no need in making it harder on them.

God created us to be clever, surely that includes using logic and science to learn about the world.

The argument can be made that since God created humanity in their image that we’re all just fledgling gods with the big difference being our lack of immortality. We’re just not long lived enough as individuals to reach God’s level of power and insight. We are who God created us to be, logic and science included so If we don’t kill ourselves off we may eventually reach a collective godhood, or something akin to it, as a species.

I’m not saying I believe that argument, I’m just pointing out that it’s there because it supports your point.

You have to be extremely willfully ignorant to think the earth is only 4,000 years old.

The Bible itself makes it obvious that the 4,000 year old thing is a lie.

So even if you’re working strictly from the bible, how the hell do you get 4000 years?

You can’t. The “Young Earth” people are morons.

Even the original wording could be read as eon instead of day.

Most people don’t know that the Hebrew word “yom” (day) can be and is used to denote wildly different lengths of time.

If anyone is interested you can read a fine destruction of the stupid “Young Earth” argument at the link I provided.

The “Young Earth” people, both Christian and Jew, are trying to shoe horn something into the Bible that doesn’t fit and doesn’t need to exist. It’s nothing more than a desperate attempt to hold onto an old, wrong headed, and man-made theory.

It’s actually a shit article that doesn’t do anything to explain why this is happening, because once you know WHY you realize this is NBD and will be going away when 24H2 is actually released.

This article isn’t great but at the bottom it does explain what’s going on.

I wouldn’t. This isn’t a real problem but you’ll probably make one if you force delete things marked as necessary for Checkpoint Updates. This 8.5gig of “stuff” is only there because 24H2 is still in Beta and it has incorrectly marked some things from the 23H update as required for future updates.

WTF is up with this 24H2 update I keep hearing about?

The first thing you have to know is that it hasn’t been released yet! That’s right, every one of these articles screaming about 24H2 bugs is based on Preview, commonly called Beta, software.

This particular issue being caused because Microsoft is moving to “Checkpoint Updates” so that updates will install faster and be smaller in size.

Right now 24H2 is marking parts of 23H3 as necessary for future updates so they can’t be deleted. This will 100% be fixed before 24H4 goes RTM.

Basically this one is a non-issue. It’s being used as an outrage generator.

I didn’t know about Canada and after thinking about it for a minute the United States does something similar for the States with .gov. Many, if not all, States have their own subdomain such as wyo.gov, montana.gov, and nebraska.gov.

Honestly it’s always seemed wrong and somewhat confusing that non-country specific TLDs, such as .gov, are dedicated to the United States.

What data does this app have that isn’t freely available somewhere else?

I’m assuming .io just stands for Indian Ocean in this case

British Indian Ocean Territory, it was just shortened to .io so it would fit into the naming scheme.

That’s a great question and the answer can be found in the wikipedia entry for the .uk domain.

In a nutshell the volunteer “Naming Committee” setup back in 1985 established a rule that entities needed to register into specific subdomains based on entity type such as .co, where the .co part stood for “Company”. They did this to make managing registrations easier and to provide an “at a glance” way to see what kind of website you were visiting (commercial, government, charity, etc). The “Naming Committee” was extremely strict about ensuring that domains were registered to a specific entity and in the correct subdomain.

By the mid-90s the volunteer “Naming Committee” was entirely overwhelmed by the sheer volume of domains being registered so that volunteer group was replaced by Nominet UK. Nominet didn’t open the .uk TLD to registration until 2014 and by then the subdomain thing (.co.uk) was so embedded into the United Kingdom’s internet structure that it had become tradition and NOT using was confusing to many people.

There’s more subdomains than just .co as well and both wikipedia articles I linked list them.

tl;dr .uk absolutely exists in the UK, it’s just used differently than almost anywhere else in the world.

<facepalm>

Dammit! Why did I mistype that?

Obviously it should be RHPS. Sigh.

If you ever decide you want to see it please for the love of Tim Curry don’t watch it on TV.

The only way to experience the RHPS is at a theater, movie or stage, with a floor show. Without the floor show you will not get what makes RHPS an adored Cult Classic. Seriously, the floor show is what makes (or breaks) the experience.

If you walk into the show and you’re not surrounded by people in costumes spouting weird lines, or if you don’t see them in the aisles within the first 90 seconds of the show starting then you may as well get up and leave.

Edit: Fixed my typo’s as pointed out by @shiny_idea@aussie.zone

deleted by creator

deleted by creator

Which would mean that every single StarLink system in Ukraine would have to be registered with the Government, even the ones owned by private citizens. They’d have to be in person registrations as well because any automated system, such as a website, could be used by Russia to get their own gear registered.

It’s really not all that difficult from a technical perspective.

I’ll go ahead and reply to you, @BurningRiver@beehaw.org and @School_Lunch@lemmy.world at the same time since you all three had the same idea.

All that Ukraine or Starlink would need to do is keep track of the MACs in use, blacklisting those which have been lost or destroyed.

A whitelist of authorized MAC addresses is easy from a “technical” prospective. It would simply be a looong list of 48 bit addresses but you are ignoring the massive challenge of managing that list.

Making this work would require the Ukrainian Government to setup an official StarLink registration process for every StarLink system in the country, including the ones that are privately owned. Then once a SL system was registered with the Government SL would have to setup a whole separate system to process those registrations.

Now you also need the opposite. Every time that a registered system shouldn’t be used because it was destroyed or someone stopped paying their bill the Ukrainian Government would have to process that and send it StarLink to have it de-authorized.

So no it’s not at all difficult from a “technical” perspective but doing this would require stomping privacy rights into a mudhole and without perfect execution across a warzone the size of a nation it will do little to nothing to solve the problem.

If this was a practical solution Ukraine would have already requested that StarLink make it happen. The fact that the really smart people in Ukraine haven’t asked for this means that they’ve already dismissed the idea as unpalatable, unworkable or both.

It’s very difficult for Starlink to stop this from happening while still allowing the capability for Ukraine to do it. If Russia obtains SL systems through intermediaries and then uses them over Ukrainian territory there’s realistically no way for SL to know whether it’s Russia or Ukraine using the service.

Okay that I’m aware of but I’ve never heard of it referred to as “bootstrapping”. Thanks for the explanation.