Version 4.6 of the Mastodon fediverse platform has been released. The headliner of this rele [...]
It is a kind of stereo image you make by looping frames together, like as a GIF. I am something of an indecisive photographer and when I like an angle I will take a lot of frames, from slightly different angles etc., looking for "the shot". And since I am also a bit of a hoarder I never clear out my camera roll. "Same shot from different angles"? You know what that sounds a bit familiar. Sure enough my phone is full of wigglegrams that I took by accident. Years' worth, waiting for me to sit down and stitch them together. Or, perhaps, for something to stitch them together. It occurred to me last weekend that I can use perceptual hashing - what TinEye (et al.) uses for reverse image search - to try and find runs of similar images and pull them out from my library automatically. So I wrote a little script to hash all my pictures: Hashing is quick but downloading photos from iCloud is not. The result is a hash that - unlike a cryptographic function like sha1 - will share more bits with hashes of similar-looking images than with dissimilar ones. We can use that to calculate the hamming distance between pairs of images and find a threshold: A few of them I am guilty of taking intentionally. But most are true accidents. As such many of them come out as less "stereoscopic" and more "kinescopic" - like little unintentional movies. Animals are a natural fit for the concept, unpredictable as they are: Design-work also. (I am always indecisive.) What fun. I have the script up on Github if you want to play with it - it'll work on your iCloud photos library if you're on a Mac, or you can point it at a directory of pictures otherwise.
TOPIC:Physics François Englert (1932 – 2026) Written by: — 19 June, 2026 François Englert during a visit to CERN in 2014 (Image: CERN) François Englert, a Belgian theoretical physicist, passed away on 18 June at the age of 93 in Uccle (Brussels, Belgium). With his associate, Robert Brout, he demonstrated that fundamental particles could acquire mass by interacting with a fundamental field that exists throughout the universe. At the same time, British physicist Peter Higgs had independently hypothesised the existence of the same mechanism. The existence of the Brout-Englert-Higgs field was proved in 2012 with the discovery of its associated particle by the ATLAS and CMS experiments at the LHC. The following year, the Nobel Prize in Physics was awarded jointly to François Englert and Peter Higgs. François Englert, who completed a PhD in physics at the Université libre de Bruxelles (ULB) in 1959, began his career at Cornell University in the United States as an assistant to Robert Brout. This meeting would mark the start of a long history of friendship and scientific collaboration between the two theorists, first in the United States, then from 1961 at the Université libre de Bruxelles. Interested in phase transitions in ferromagnetism and superconductivity, they took inspiration from the work of Yoichiro Nambu, adapting spontaneous symmetry breaking into the quantum field theory: the theoretical framework of the Standard Model. This work led them in 1964 to theorise symmetry breaking that would generate the masses of particles that are force carriers of interactions (also known as vector bosons) through their interaction with a hypothetical fundamental field. At the same time, Peter Higgs submitted the same idea, adding the concept that such a field must have an associated particle, which would later be named the “Higgs boson”. The existence of the Brout-Englert-Higgs field solved a key problem which emerged in the early 1960s. Electroweak theory, which describes the electromagnetic and weak interactions in a single framework, involved vector bosons devoid of mass. This is the case for electromagnetism but not for the weak force, whose range is limited to the nucleus, and which had to be carried by bosons with mass. François Englert continued his brilliant career at ULB. With Robert Brout, he founded a research group on fundamental interactions, which conducted studies in many different areas, from understanding strong interactions to general relativity and cosmology. Englert was particularly interested in what he considered to be the defining question of fundamental interactions: reconciling general relativity with quantum theory. A professor emeritus of ULB from 1998, he stayed up to date with developments in theoretical physics. After 2012, he made several visits to CERN, where he was able to converse with colleagues with the courtesy and tact for which he was well known. The discovery of the Higgs boson has had major implications for particle physics. The study of this unique particle has opened up a new field of research, which the ATLAS and CMS experiments have been investigating since 2012, and which could lead scientists to physics beyond the Standard Model. It was to be at the heart of research at the LHC, the High-Luminosity LHC and future colliders. François Englert explains the equations of the Brout-Englert-Higgs mechanism, which gives fundamental particles their mass. (Video: CERN). Source: CERN (CDS) CERN community General public Higgs boson News Related Articles View all news No posts were found. Try to change the category or the date filters.
The failure mode of an autonomous agent isn't that it does nothing. It's that it does too much. Capabilities induce behaviors — more than instructions.
Trust Identity Protocol (TIP), by Dinesh Mendhe, published by The AI Lab Intelligence Unobscured, Inc. The open standard for verified human identity and content provenance on the internet. Post-quantum cryptography from genesis (ML-DSA-65, ML-KEM-768, SLH-DSA), federated DAG, AI Trust Council multi-stakeholder governance under EU AI Act Article 95. 140 pages. Whitepaper Version 1.0. Licensed CC BY 4.0. DOI: 10.5281/zenodo.20722378.
Guess the club for players in today's World Cup matches. Daily challenge, nation filters, role filters, and deep squad cuts.
FLIP TABLE; was a mini-hackathon and showcase for "weird" databases: things that read and write data, but with a twist of some kind. It took place on Sunday, May 17th, 2026 at Hex House in Brooklyn. Each presentation was recorded and linked below. Presenters' databases were also scored by audience members according to the following alignment chart: data ┌─────┬─────┐ │ │ │ │ │ │ cursed ├─────┼─────┤ blessed │ │ │ │ │ │ └─────┴─────┘ based Prizes were given out to the five superlative databases, which were:
TechCrunch spoke to investors to find the hottest startups in the Spring 2026 YC batch. Some of them commanded valuations of over $175 million, VCs said.
TOPF - Talos Orchestrator by PostFinance TOPF is managing Talos based Kubernetes clusters. It provides functionality for bootstrapping new clusters, resetting existing ones, and applying configuration changes. Early Stage Project TOPF has just been released and is in an early stage of development. While it is actively used at PostFinance, APIs, configuration formats, and CLI flags may change between releases. Feedback and contributions are welcome — please open an issue if you run into problems or have suggestions. Get Started What TOPF does TOPF is a single binary that handles the full lifecycle of a Talos cluster: Apply configurations with pre-flight health checks, dry-run diffs, confirmation prompts, and post-apply stabilization — no need to juggle talosctl commands per node Upgrade Talos across all nodes with version comparison, so only nodes that actually need updating are touched Bootstrap and reset clusters with built-in safety checks Generate kubeconfig and talosconfig from the secrets bundle Configuration is built from layered patches — small, composable YAML files organized by scope (all nodes, role, individual host). This makes cluster config easy to review, version, and share across environments. Philosophy TOPF doesn't reinvent the wheel. Under the hood it uses the Talos Go libraries directly — the same operations you would run manually with talosctl, but automated with health checks, diffs, and safety prompts on top. There are no intermediate config files to manage and no dependency on talosctl for day-to-day operations. Where TOPF really shines is its configuration model. Instead of managing one monolithic machine config per node, you compose small, scoped patches — per cluster, per role, or per host. This layered approach keeps configurations DRY, easy to review in pull requests, and straightforward to share across environments. Non-goals TOPF is intentionally limited in scope: Single cluster: TOPF manages one cluster at a time. Multi-cluster orchestration is out of scope — for managing many clusters, run TOPF in a pipeline per cluster (see Production Usage). Not an operator: TOPF is a static tool that runs when you invoke it. It performs a single reconciliation pass, not a continuous control loop. This is by design — you decide when changes are applied. No Kubernetes upgrades: TOPF does not orchestrate Kubernetes version upgrades with proper validation. Use talosctl upgrade-k8s for that (see Kubernetes Upgrade).