SAI_Peregrinus

It's unmaintained, and off-topic for this discussion, but the Luminous JS event blocker¹ was cool because it allowed blocking specific event handlers while still allowing JS to execute.

¹https://gbaptista.github.io/luminous/doc/en-US/

> Our inferred A⋆ is consistent with the 13.6 Gyr expected in CMB-calibrated ΛCDM, assuming the first long-lived stars formed when the Universe was 0.2 Gyr old. This agreement casts doubt on solutions to the Hubble tension solely through new physics prior to recombination, which generally imply a cosmic age of 12.9±0.2 Gyr to match low redshift probes. It is difficult for stellar modelling uncertainties to reconcile such a low age with our result given the low metallicities of the oldest stars in our sample and independent asteroseismic constraints.

So the expected age of the universe hasn't changed, but some alternatives to ΛCDM look less likely.

Boo! Permanent Dawn time is better. Every day at 03:00, set the time when the upper limb of the sun will cross the sea-level horizon at the equator to 06:30. That means kids never have to wait for the bus in the morning in the dark, except at high latitudes in winter but who cares about those kids right?

/s

> So no via is necessary; just connect directly to that pin on each layer (kicad probably did this for you automatically). This trick works with all thru-hole pins.

Note that without a plated through hole (vias are small plated through holes, those designed for component legs are bigger) the solder will only adhere to one side. For mounting large components where vibration may be a problem this will make the pad weaker & more likely to lift off. A plated through hole lets the solder flow through & bond to pads on both sides. So you sometimes do need plated through holes.

Otherwise I agree. These days 4-layer boards are so cheap it's often worth just dedicating an entire layer to ground, and one to power. E.g. Signal, ground, power, signal. All your ground connections become vias. Most of your power connections are vias to a lower inside plane. Your signal traces are available to probe & rework easily. You get a bit of distributed capacitance from the power & ground planes.

Sure, but of course since there's profit to be made defeating these systems once someone makes a program to defeat detection they'll sell it. Complicated attacks only stop simple attackers until a sophisticated attacker scripts & sells the exploit. Not that you shouldn't try, just don't expect defenses to last long-term.

I find Sedra/Smith a terrible introduction, but a good reference. It's nice once you've already built an intuition for how things work to be able to go back & build up the mathematical models, but trying to understand the behavior of circuits from the math first is a bad order.

No, it's "jitter that mimics human cursor movements detected by Cloudflare's Precursor script". It'll just be another arms race.

I find I get significantly more cramping with cursive since there are fewer "rest" periods between the letters than with engineering block gothic lettering. Gothic lettering is much slower than cursive, but much more readable and (IMO) easier to write.

I'm dysgraphic, which probably plays some part in this.

Oh, they're much worse[1]. Is 4k 3840x2160 or 4096x2160? That's right, it's both! And 4096x2048! And 4096x4096! And about half a dozen other resolutions, many of which have no dimension of 4000 or 4096 pixels.

[1] https://en.wikipedia.org/wiki/List_of_common_display_resolut...

The double-slipped reef knot is a pretty nice shoelace knot. I prefer a more secure variant (a different tying method of the Ian's Secure Shoelace Knot/Turquoise Turtle that's a bit easier for me), but pretty much every kid should learn the double-slipped reef first. Scouts should already know it before they join!

Communications satellites don't have nearly as much long-term rewritable storage needed.

The reef knot (square knot in Scouts lingo) is a good binding knot. It's a terrible bend. Scouts teach it as a bend, for some idiotic reason.

Reefing a sail or tying a parcel, a reef knot the role will fulfill. But joining two ends one should only use bends, And a reef knot's a sure way to kill.

⸻Stuart Grainger, ex-Master Mariner, 1985. Referenced from "The Complete Book of Knots" by Geoffrey Budworth.

The scouts require a bunch of utterly terrible knots. They include the Granny Knot which you never actually want to tie, only to avoid tying by accident. They include the Sheepshank, which is quite possibly the worst way to shorten a line ever invented. Etc.

IMO it's important to start with what possible uses of knots there are, and then learn a knot for each use. I'll exclude decorative knots, because those are subjective & very diverse.

Stopper knots prevent rope from passing through a hole & keep the end from unraveling. The Overhand knot is the simplest. The Double Overhand is a very simple addition to an overhand. The Figure-8 is slightly bigger, and useful to know.

Single loop knots create a single fixed loop in a line. The Butterfly (aka Alpine Butterfly) can be tied mid-line (without access to the end) or with the end of a rope, and is two overhand knots interlocked in a particular manner.

A noose is any loop that tightens when a load is applied. I like the Scaffold Knot, it's a double overhand around the standing part of the rope. Its biggest disadvantage is it can be difficult to undo. Any fixed loop can also be made into a noose by tying it around the standing part, forming a "Running <name of fixed loop>".

Bends join the ends of two ropes. The Fisherman's knot (also has lots of other names) is two overhand knots, one with each rope, tied around the standing part of the other rope. It's strong, secure, but difficult to untie. The Double Fisherman's uses double overhands. The Butterfly Bend is a Butterfly tied as a bend, it's strong, secure, and much easier to untie. The Butterfly Bend is tied the same way the Butterfly Loop is when tying with the end.

Hitches tie a rope to a rigid object. They can attach a rope to something where you have access to an end of the object like a bollard, or where you don't like tying into a fixed ring. They can be for lengthwise pulls, or for right-angle pulls. Adjustable loops are hitches tied around the standing part of the rope. For right-angle pull, the scaffold knot works well (again). It can be tied without access to the end of an object, so it works for rings and bollards. For lengthwise pull, the rolling hitch is nice, and the Rolling Hitch Ziptie is a use of the rolling hitch which works as an adjustable loop and a binding knot.

Binding knots hold only when tied around an object. The Double-Slipped Reef Knot is a common shoelace knot. The Turquoise Turtle or "Ian's Secure Shoelace Knot" are different methods of tying a structurally identical resulting knot that's a bit more secure. Worth knowing at least one of these three, or you'll only wear slip-ons or Velcro closure shoes. Also the Rolling Hitch Ziptie is worth knowing.

There are also some systems of knots called "trucker's hitch"es, which are all ways to use loop knots as improvised pulleys with a final hitch to secure a load in place. IMO they're not independent knots. Handy to know at least one sort though in case you don't have ratchet straps or snatch blocks. The Versatackle is nice, self-locking, and tied with just Alpine Butterflies and any hitch.

So, a list of 5:

1: Overhand knot. 2: Butterfly loop (mid-line). 3: Butterfly loop (with the end). 3 (used differently): Running Butterfly. 3 (used differently): Butterfly bend. 4: Scaffold knot. 5: Rolling Hitch. 5 (used differently): Rolling Hitch Ziptie. 5 (used differently): two opposed Rolling Hitches for tying your shoelaces together works, with difficulty. 2+5: Versatackle trucker's hitch formed from two Butterfly loops and a Rolling Hitch.

All except the Rolling Hitch are based on the Overhand knot. If you're willing to add a sixth knot, pick something better to tie your shoes.

Flock also has facial recognition. There are Flock cameras on public walking paths.

I don't accept that it applies to parrots. Certainly not to Congo African Grey parrots.

DST is bad because it changes the clocks in huge jumps. Very poor for people's health. Noticeably increases excess deaths.

Fixed clocks are bad because they don't track the sunlight.

We should change the clocks by 10 minutes, every month. Keep dawn at roughly the same time every day, say 06:30. Add enough time zones so that dawn will always be within 10 minutes of 06:30 at the equator for a given longitude.

It's a nitpick, but testimony under oath is evidence to US courts. All evidence is either testimonial or circumstantial.

The laws which any contributors to the OSS project are subject to. Some projects geographically restrict who can contribute to avoid issues like this, but when laws are passed by a jurisdiction in which existing maintainers reside those maintainers have the choice to either comply or move to a different jurisdiction. Moving is extremely disruptive & expensive, so they often comply.

POSIX specifies a common subset of functionality of several different shells (and C libraries) that existed when it was created, and that any compliant shell (or C library) will share. Some functions like `echo` are guaranteed to be present but don't have fully-specified behavior, because the shells that POSIX was created to be the common functional subset of had different behaviors when POSIX was created.

POSIX doesn't guarantee portability. POSIX only guarantees that the things it specifies will work in a POSIX-compliant environment. POSIX makes no guarantees about portability to non-POSIX-compliant environments like Windows' shells or MSVC, the Fish shell, etc. POSIX makes no guarantees about the things it doesn't specify.

I agree. The problem is that anything which solves this won't be compatible with email, since these issues are inherent to the protocol. Fixing email isn't possible, so the solution has to be replacing it. Unfortunately that's very difficult.

The Register is highly irreverent, as a rule.

email can be read by any server in the chain between the sender & recipient. It's not secure. PGP doesn't fully fix this, it still leaks message content (subject) and metadata. So does S/MIME. That doesn't mean attachments are leaked, but it does mean email isn't compliant with any of the standards which require communicating securely.

To get excessively pedantic, he walks very poorly. Toddles around. So his gait makes him a literal toddler. All 1 & 2 year olds toddle, but not all who toddle are 1 or 2 years old.

Resistors don't go in the cable. They go in the device. They indicate that the device can't negotiate voltages above 5V, so just send 5V.

USB-A has no ability to provide voltages other than 5V, so there's no need for indicating it's the max.

Not all chargers have USB-A ports. Many laptops don't have USB-A ports, so if you want to charge a noncompliant device from a laptop it won't work. Or a laptop charger, which is dedicated USB-C.

In contrast, OS CSPRNG APIs usually only provide access to a CSPRNG that the OS seeds on its own, in some way not fully controllable by the user. E.g. using fast key erasure & hashing in data from a hardware entropy pool.

Most likely is either extracting the private key from the camera or getting the camera to sign arbitrary data. If the signing isn't part of the sensor die itself there's a bus where the image data gets transferred from sensor to signer, so an attacker can inject arbitrary data onto that bus to get it signed, even though they never actually extract the signing key.

It's always been about the safety of their valuation.

Disagree, availability is part of security. That's why denial of service attacks are a security issue. Bad enough usability is indistinguishable from a DoS attack.

More verbose code takes up more space in the context. It's harder for humans to review, but also harder for future AIs to edit. Unless you manage to keep the AI to firm module boundaries & have it replace modules wholesale it's not really equivalent to how assembly gets replaced wholesale when a compilation unit changes. Compilers aren't editing the `.o` files when you rebuild, they throw the old ones out & replace them. But when you prompt an AI it is reading & editing the source files, so excess verbosity in the source files is detrimental.