cypherpunks

1

The retreat is scheduled for August 12–16 at a venue near Dublin, Ireland.

The original version of the source article identified the location as the Powerscourt Hotel; in an act of journalistic cowardice (to be expected from a Condé Nast Publication) Wired later edited their article to remove that detail "to address a security concern raised by a Dialog representative".

Esquire is unsurprisingly sticking with Wired's "near Dublin" description of the location, but fortunately it looks like some Irish media outlets (eg this and this) are reporting where it actually is so hopefully there will be some local opposition present.

1

Arthur Besse @lemmy.ml 2mo ago

ima keep it real with u chief

2

Arthur Besse @lemmy.ml 2mo ago

For each participant, Dialog logs a membership status, every retreat the person has attended, a biography, a home city, and a private access token. WIRED is not publishing the tokens, which function as login credentials, or the personalized account links that contain them.

This is an odd thing to say given that neither Wired nor their source ("the Swiss hacktivist maia arson crimew") appear to be publishing any of the actual data whatsoever, beyond the handful of mostly nonspecific references to it in the article text. (Eg, lots of sentences like "The website directory names sitting Trump administration officials, two US senators, six members of the Paypal Mafia, a former Middle East chief of intelligence, and a sitting ambassador to the United States, along with the founders and directors of many of the country's largest surveillance, data-broker, and advertising-data companies." - omitting names of any of these people.)

Also, the linked archive says:

Update 6/16/2026, 5:47 pm EDT: WIRED updated this article to correct a conflation of two people named Jeff Epstein. A small revision was also made to address a security concern raised by a Dialog representative.

Someone helpfully had already made an earlier archive before that, so we can see what information Wired journalists Dell Cameron and Yulia Almazova removed at the request of a Dialog representative: where it now says "The retreat is scheduled for August 12-16 at a venue near Dublin" it originally said "The retreat is scheduled for August 12-16 at the Powerscourt Hotel outside Dublin".

Arthur Besse @lemmy.ml 2mo ago

Fendit, refusing this meme:

who's Fendit?

Maybe some Tamarian from a novel, or maybe made up for an academic paper? The only search engine result i see for "Fendit, refusing the flame" is the paper Picard understanding Darmok: A Dataset and Model for Metaphor-Rich Translation in a Constructed Language which "assembles a Tamarian-English dictionary of utterances from the original episode and several follow-on novels".

(it seemed appropriate to respond to this meme with some apocryphal Tamarian.)

Arthur Besse @lemmy.ml 2mo ago

He even managed to pull off cardassian with sideburns

Combs did not ever play a Cardassian.

Are you referring to his appearance on Voyager, where he played the vaguely-cardassian-resembling Penk?

Arthur Besse @lemmy.ml 2mo ago

don't threaten me with a good time

Arthur Besse @lemmy.ml 2mo ago

yep. (see my other comment in this thread)

4

Arthur Besse @lemmy.ml 2mo ago

another screenshot of a tweet, no link, no alt text, smh my head.

imo science memes should link the science!

Here is the paper from April which this tweet is actually referring to: https://royalsocietypublishing.org/rspb/article/293/2069/20252994/481340/The-phonology-of-sperm-whale-coda-vowels

Unsurprisingly the tweet's characterization of the research as finding whale language "structurally comparable to Chinese" is an exaggeration; they are actually saying it is similar to tonal languages and then using Mandarin as one example of a tonal language.

here are the two paragraphs which actually mention Chinese

Human vowels consist of a sequence of glottal pulses produced by vocal folds. Whale codas consist of a sequence of clicks produced by vibrating phonic lips, which play a role similar to the human vocal folds [15]. In human languages, the frequency of glottal pulses corresponds to pitch—closely spaced glottal pulses give rise to a higher pitch, while more widely spaced pulses give rise to a lower pitch. In linguistics, tone refers to pitch as recruited to express linguistic meaning. Many languages use tone to distinguish between different words. For example, in Mandarin Chinese, the following four words differ only in their tonal contour, while having the same consonants and vowels [21]: high and level tone ma ‘mother’, rising tone má ‘hemp’, falling-rising tone ma ‘horse’ and falling tone mà ‘scold’. The coda types can therefore be compared to human tone: ‘regular’ coda types can be compared to level tones, codas with ‘increasing’ ICIs to falling tones and codas with ‘decreasing’ ICIs to rising tones. (However, our analogy has a limit: while in human languages, different tones can be associated with different meanings, the meanings conveyed by sperm whale codas have not been established.) In figure 1, the ‘F0’ (fundamental frequency) of each coda is represented with a blue line.

Beguš et al. [15] show that different coda vowel qualities can be instantiated on the same coda types and propose that coda type and coda quality are orthogonal [15]. This points to another parallelism between the sperm whale communication system and human language, as tone and vowel quality are often similarly orthogonal. For example, in Mandarin Chinese, the falling–rising tone may appear on any vowel, e.g. ma ‘horse’, ma ‘rice’ and ma ‘smear’. Orthogonality, in this case, is used to describe the independent mechanisms of production between the traditional timing or source features and the vocalic or filter features. In other words, the rate of vocal fold or phonic lip vibration can be independent of the shape of the resonant body (the vocal tract or the distal air sac), and both vowel types surface on several traditional coda types. However, while the production can be independent, there can still exist distributional patterns, where a vowel quality is more frequent on certain tones or some coda vowels are more common on certain traditional coda types. Our paper builds on Beguš et al.’s [15] findings and reveals further complexities within the system of sperm whale vocalizations.

Here is an article about it: https://www.theguardian.com/environment/2026/apr/15/sperm-whales-alphabet-vocalizations-similar-humans ...which also links this other fascinating news from the same lab from back in March https://www.theguardian.com/environment/2026/mar/27/scientists-film-whale-giving-birth-other-whales-help-her ("This is the first evidence of birth assistance in non-primates")

finally here https://xcancel.com/kuso_otoko/status/2062224294835540161 is the tweet this post is a screenshot of, where you can find people in the replies already making the predictable "met them at a very Chinese time in their life", "that's why japan hates them", etc jokes.

note

i'm definitely not working in China's Cetacean Ops and trying to prevent the western world from finding out that whale speak is just super slowed down Mandarin, i swear

Arthur Besse @lemmy.ml 2mo ago

One shot rewriting the whole test suite

tridge's blog post makes it clear that this was not "one-shotted" at all.

You should read the whole thread

I regret reading it; I'll assume in good faith that it wasn't LLM generated but it is ironically as confidently wrong as if it were.

It almost (and should have) lost me when it started by quote-agreeing with someone else saying "rsync was basically done until the maintainer discovered vibecoding" - no, pay attention, it was not "basically done", there were/are a mountain of CVEs!

But then this got my interest:

This does not “translate tests into pytest” or a unit testing framework, it writes its own testing framework where tests are whole python scripts that redefine basic test functions in every script. Surely there would be a single way to “run rsync and get the results” - nope, well, there is, but then every test file will randomly redefine its own _run_and_capture function.

tridge says he has used pytest on other projects and had good reasons not to use it here; I'm inclined to believe him.

But the notion of every test defining its own way to invoke rsync sounded like a valid criticism, and an easy one to verify, so I checked: It turns out that there is in fact a common run_rsync function which is used by the majority of the tests. One test defines its own _run_and_capture function (which differs in that it writes the output to a file, for reasons I didn't investigate), and it looks like a few others invoke rsync other ways, but the majority of them use the common function.