redjard

Sugar beet seeds are produced via wind pollination in dedicated very compact setups. They plant strips of male and female plants with controlled distances.
As far as I can tell no pollinators are involved anywhere in the sugar beet industry.

Then just say the world has ended and remove the burger.

Andy Grote is a dick

Better to use a general foss redirect extension than slowly accumulate various service-specific ones.
Libredirect natively does xitter -> xcancel, bluesky -> skyview, fandom -> breeze, reddit -> redlib, and like 50 more. All with tons of prefilled mirrors and uptests …

It’s a great place to find those alternative frontends. If you’re annoyed by some enshittified platform, good chance you can just enable a redirect in there.

https://libredirect.github.io/

https://equal-earth.com/equal-earth-projection.html

forces me to commit to one issue at a time

Skill issue

Paperclips in your comments are a bit more annoying in comparison, also you’ll just forget them.

The newest rossmann video explains the idea more, but in short the goal is to get a feel for how large the movement is, not creating some slogan.

Let’s see where this goes

Oof, I see.
Kinda a bad look for type I when some of the users follow a different spec and ruin all attempts at improving safety or even keeping standards like earth being down.

In comparison the european plugs are moving closer together, for example F+E combo plugs are increasingly common.

Some images of the plugs, since I didn’t know what they looked like.

It was mentioned the pins started being insulated like that second image 20 years ago, but going by the images I found the older uninsulated style is still more common. This is ofc a major shock hazard when plugging in your stuff.

Even with the insulation, you can still reach under the half inserted plug, just less easily and maybe only if you have smaller hands (like children).

Fundamentally flat sockets are doomed to be shock hazards, compare it to the recessed sockets where the entire surface the contacts insert into is cut off from reach before the pin insertion starts, and on top of that the pins of say type F have been insulated for so long many don’t know there were uninsulated variants.

Another bonus of the recessed style is the plug doesn’t stick as far out of your walls. For extension cords it’s probably a bit bulkier, but when you sink the recession into the wallbox of the outlet you can get as flush as the width of the cable with an angled plug.

Also pretty sure you can step on angled type I plugs resting on their backs. The recessed plugs usually have grips on top so can’t rest on their back even when angled. Their pins are also ball-shaped on the end, type I looks quite angular and more painful.

In practice tons of outlets are wired the wrong way around.
F actually has a convention for the socket, which is probably ignored even more often, but I would never trust live and neutral not to have been swapped somewhere regardless of outlet.

Just forcing plug designers to consider live/neutral being randomized in a very obvious manner might be safer in the long run than working on a partially broken system where someone manufacturer might be fooled into trusting it.

What about ye olde “googles on ddg”?

Great! Could you kindly extract them to further our article-non-reading habits?

100k left

Can’t you just replace the entire game folder?
Running a verify and repeating the action would even show how many files were changed.

It isn’t usually. If it was, the server-side function wouldn’t need a constant runtime at different-length inputs since the inputs would not have differing lengths.

The problem with client-side hashing is that it is very slow (client-side code is javascript (for the forseeable future unless compatibility is sacrificed)), unpredictable (many different browsers with differing feature-sets and bugs), and timing-based attacks could also be performed in the client by say a compromised browser-addon.

For transit a lot of packaging steps will round off transfer-sizes anyhow, you typically generate constant physical activity up to around 1kB. Ethernet MTU sits at ~1500 bytes for example, so a packet of 200 bytes with a 64 char password or a packet of 1400 bytes with a 1024 char password containing some emoji will time exactly identically in your local network.

Most attacks on servers are on the connections. All IPs are owned by entities part of countries, so your IP is always under someones jurisdiction. The same is true for regulsr DNS entries, so the domain of that server.

For getting the data however, there also isn’t any protection in international waters. Someone would just raid you and you could do nothing about it. What good is lawlessness if you don’t have the ability to enforce your own “laws” about not having your data taken away?

You could lay low so noone bothers with that, but then you could also just lay low with regular secretive hosting.

The admin team is distributed and the infra is in europe iirc.
So no

Cryptographic hash functions actually have fixed runtime too, to avoid timing-based attacks.
So correct password implementations use the same storage and cpu-time regardless of the password.

That is a huge red flag if ever given as a reason, you never store the password.
You store a hash which is the same length regardless of the password.

sure