RE: mastodon.social/@ennopark/1155…

Wie weit die Verrohung vorangeschritten ist, zeigt sich an vereinzelten Kommentaren, die an dieser Aussage nichts schlimmes finden wollen. Spannend finde ich, dass ich solche Replys bisher nur auf Mastodon bekommen habe, aber nicht auf Bluesky und auch nicht (sehr überraschend) auf LinkedIn.

This entry was edited (1 week ago)

ON this day in 2005, twenty years ago, I was visiting @MaryAnn25 in Portlan,, Oregon.

I was up at around 4:30 AM on this cold Saturday morning in her apartment with a cheap Sony walkman connected to a digital recorder, trying to capture a bunch of local commercial FM radio station IDs just for fun, when I came across KBOO, a community radio station, and a guy playing country classics.

Instead of a properly produced ID, this guy opened the microphone, and with a voice that broke rather spectacularly, proclaimed "You are listening to KBOO, Portland. The voiced quality just went away when he said the word "to", and it came out with a weird, strangled h sound.

When I first heard it, I absolutely busted out laughing, happy that I was able to capture it.

Unfortunately, my Edirol R1, an early solid-state stereo digital recorder, decided it's batteries weren't really up to the job, and it cut off while recording, which damaged the file.

I was able to put it's compact flash card into a reader, and load a recovery utility, called PC Inspector File Recovery, to get the raw data off the card, then open that raw data in an audio editor, which was just enough to pull it off.

So, exactly twenty years later, I present this four second audio clip, which sort of became an audio meme among friends for years.

in reply to seddy

I've just finished playing Broken Gark: Chaotic Doob in Garkle Realm, and here are my results:
I have managed to get a total of 27386 idiot boxes.
During the game, I've unlocked no achievements, kinda like when I'm not playing, and was awarded -24 credits for my lackluster performance!
#GarkelRealmGameScore #GarkelRealm #Gaming #AudioBlaming
This entry was edited (1 week ago)

So @FreakyFwoof went to a hotel in Bristol, and recorded a nice "ding" sound from the bathroom.
As soon as I heard it, my weird brain went "Oh, hey ,that could easily be turned into a fire alarm." So I did just that, minus adding a bunch of distortion and compression to actually make it more realistic.

reshared this

Este tiene que ser @modulux. Vamos, es que estoy seguro. Todos los días saluda diciendo lo que hace y lo que no hace, pero nunca habla del sueño, y eso es demasiado sospechoso.
Un funcionario no entiende por qué últimamente le cuesta tanto conciliar el sueño durante su jornada laboral

elmundotoday.com/2025/11/un-fu…

Lol we're not the only people complaining about crappy web version for an app: Meta just killed native WhatsApp on Windows 11, now it opens WebView, uses 1GB RAM all the time windowslatest.com/2025/11/12/m…

reshared this

Oops, seems the BBC didn't quite proofread their alt text on their live page regarding the US gov shutdown and the impact on flights. Image: A TSA agent in blue shit, blue gloves and short brown hair reaches over to pick up the bag of a passenger going through security. bbc.co.uk/news/live/c20ez8y0dv…

Hey, people who design OTP systems: why only accept the most recent code? If there are delays in SMS or email, and you request two codes, and then enter the first one, it will never work. What possible security interest is served by only accepting the most recent code within some timeframe (say, 30 minutes).

So often, I just don't understand how the people who design these systems think about the world.

I think @stefano convinced me to replace my one minio server with SeaweedFS just because the way you configure the buckets and ACLs is so much simpler for the normal case

it-notes.dragas.net/2025/11/06…

GrapheneOS Foundation Announces New ASN (UPDATED: 11-14-2025)


We received an ASN and IPv6 space for GrapheneOS from ARIN: AS40806 and 2602:f4d9::/40.

We've deployed 2 anycast IPv6 networks for our authoritative DNS servers to replace our existing setup: 2602:f4d9::/48 for ns1 and 2602:f4d9:1::/48 for ns2. BGP/RPKI setup is propagating.

We applied for an IPv4 /24 for ns2 via NRPM 4.10 and can apply for one for ns1 after we obtain that one.

Our ns1 network has New Jersey, Miami, Los Angeles, Seattle, Frankfurt and Singapore. Our ns2 network currently has New York, Las Vegas and Bern. We'll be expanding both.

This provides an overview of worldwide latency for our ns1 cluster via the Rage4 anycast service we currently use for IPv4+IPv6 with ns1:

ping6.ping.pe/2a05:b0c4:1::8

Here's ns1 via our own IPv6 /48:

ping6.ping.pe/2602:f4d9::1

Here's ns2 via our own IPv6 /48:

ping6.ping.pe/2602:f4d9:1::1

In the future, we plan to use these 2 anycast networks to provide recursive DNS resolvers as an option for our users. For now, it's only for the authoritative DNS used to provide other GrapheneOS services which is what DNS resolver servers query after the root and TLD servers.

ARIN gave us an IPv4 /24 based on our NRPM 4.10 request in under 24 hours. It's being announced from our ns2 network:

github.com/GrapheneOS/ns1.grap…

It will take a long time to propagate since the RPKI IRR/ROA data gets fetched via timed jobs rather than pushed hop-by-hop like BGP.

It cost us US$50 to register with ARIN as an organization and US$262.50/year paid in advance to become an 3X-Small network. It'll be US$525/year when we get a 2nd IPv4 since we'll get pushed into 2X-Small. 2X-Small covers IPv4 /22, i.e. 4x /24, which we can get via the waitlist.

We've deployed our IPv4 /24 and IPv6 /48 for ns2 in production to replace the IPv4-only anycast tunnel system it relied on before. It has somewhat better latency and significantly better reliability now. We're waiting a bit longer for production deployment of our ns1 IPv6 /48.

We need to choose a host in Singapore with IPv4+IPv6 BGP support to extend ns2 with a location in Asia. Once that's added, it will be good enough for our current needs. The subset of our dedicated/colocated update servers with BGP could be used as extra ns2 locations eventually.

This entry was edited (1 week ago)

AOSP 16 QPR1 Released


Android 16 QPR1 is finally being pushed to the Android Open Source Project. This should have happened on 2025-09-03. We migrated to full Android 16 QPR1 kernel code (GPLv2 tarball) and firmware in September. We couldn't migrate userspace to QPR1 without it being pushed to AOSP.