That beeing said, there are people that insist on obscurity beeing security (sigh) and want to keep doing dns views when using IPv6. But even then things are much easier when the result would be the same in either view.

OMG!!

This guys a bee! Everybody run!!!

Its as long as an ipv6 address

The : is ok. I dont struggle with the shortening part. I struggle the “everything else” part.

I’ve had a look into it, and it doesn’t work if you try to do it mathmatically. You always need more than 3 gos on the seesaw.

There is a solution in the replies to my original comment that is the actual solution, and it works every time and is much simpler than any grouping method.

It involves assigning a letter to each person and then aligning that with a grid of positions “left” or “right” or “none” on the seesaw. Over the three rounds. So, person A is on the right all three rounds person b is on the right for 2 rounds then on the left for the 3rd round.

You end up with a list of 12 patterns that do not repeat or mirror any other pattern like “LLL” “LLR” “LRR” “LR-” etc. Then you do all three rounds and compare the position the seesaw was in with those patterns.

If the seesaw was down on the left 2 times the down on the right the third time then you look for which person had that pattern in this case it was person B. So they are the one with a different weight and they were heavier.

Equally, if the opposite pattern occurred. It was down on the right 2 times, then down on the left for round, then that is the opposite pattern of person B and does not occur anywhere else, so it was person B, and they were lighter.

person:  A B C D E F G H I J K L

round 1: L L L L R R R R — — — -

round 2: L L R R R — — — L R L -

round 3: L R R — — L R — L L — R

Oh i get it. So if in round 1 it tilted down on the right. Round 2 it was even then round 3 it tilted down on the right then it was person G and they are heavier. However if it was reversed and tilted on the left then even then left then it was still person G but they are lighter. Because that pattern only occurs once. This is brilliant. Thankyou to you and the person you corrected the formatting of.

Im sorry when i read weigh two of them i counted it as two separate weighings of two sets of groups. My bad.

What about the 4th group? There are 12 people

Thats 4 uses of the seesaw. It has to be 3.

The question was to find who doesnt weigh the same and if its heavier or lighter. Watch the clip again.

How do you solve that? I saw a solution in the comments where it says to start with numbering all the people and butting 1234 and 5678 on the see saw, then it says if they weight the same then continue and that seems to work. But if they dont weigh the same it doesnt work and it doesnt say what to do in that case.

Its CIDR notation. So /0 means the subnet mask has no on bits and would read as 0.0.0 0 if you had a /1 that turns 1 bit on in the subnet mask, so it would be 128.0.0.0.

If i had a /24 which is the subnet mask used for most small networks like your home router. There would be 255 minus 2 addresses available for clients (phones, pcs etc) so the subnet mask would have 24 on bits and read 255.255.255.0, which you may be familiar with.

(Assuming you dont know much, not to insult you, you might know plenty), but when writing any kind of instructions or guides, i was always told to assume the reader knows absolutely nothing and miss nothing out.

Remember, when we abbreviate an ipv6 address all leading zeros are reduced to a single 0.

E.g

0003 would just become 03

When there are geoups of 4 zeros these can be represented as a single 0 or as a double colon ::

But we can only use the :: once so when summarizing an address containing multiple groups of 4 0s one after the other they can all be abbreviated to a single ::

Eg

fe80:0000:0000:0000:0210:5aff:feaa:20a2 would become fe80::210:5aff:feaa:20a2

Therefore it is perfectly valid to abbreviate an address of 0000:0000:0000:0000:0000:0000:0000:0000 /0 to just ::/0

0.0.0.0 /0 ::/0

SUCK MY DICK, GRU!

I was about to say an error message pops up about an auth token when i try with username and password. However, i tried it just now, and it did what yoh said. I’m logged in now. Goodbye sync.

Theres nowhere to enter my code on the log in screen.

But cannot be used if you have 2fa set up on your lemmy account.

This is how my secure crt is set up when im accessing switches. If i use ctrl+c it cancels what im doing and drops back to priv mode and its so frustrating.

Now that i think about it, i think it was an activation issue. I had a dodgey made legal copy of windows 10 when they offered the free upgrade to even those with illegal copies of windows, but when i moved it, i needed to activate and didn’t know the key.

But two replies offering different bits of advice to my comment shows that at least in part its true that this is not straightforward

We use both. Its not my department but i know the server guys are using windows for some servers and linux for others and the decision is normally made based on which is going to be best for the specific needs of the function of that server.

Pretending one is outright better than the other is childish. Just use whats best at the time.

The windows boot drive? Dont think thats possible anymore. If its completely new hardware.

Im not sure what the trigger is but if enough hardware has changed it wont boot.

I had to install windows fresh on a new hard drive when i bought a new pc last year.

Ill be waiting for the Neuralink - X