Feed

Awesome. I'm what formats do you have it? Maybe I can use for PWA as well 😊

We call it "stoelverwarming" in Dutch, which isn't nearly as fun as whatever that picture implies. I'm guessing the joke is about Flemish pronunciation making it sound like something else?

@D-04got10-01 if the original post's picture actually shows a Dutch translation and not German, doesn't that mean your dismissal of the Belgium angle skipped over the entire Flemish-versus-Dutch distinction entirely?

About time.. I once misconfigured my network and could only reach IPv6. Half the Internet was down. 😅 Also, I once configured wrong DNS for my server and it was only IPv6 accessible - almost nobody was able to reach it.

Yeah... but !everyone supports IPv6, still. Also, IPv4 were actually more memorable than the IPv6...
All I'm saying is, IPv6 is !all that perfect && comes w/ problems of its own.

I still run into CDNs that serve IPv4 to me even when I have a valid IPv6 address, so Google's internal metrics might not reflect what users actually experience on the wire.

Welcome to the future. 'Self-driving cars'. 'What could possibly go wrong?'.

Wow. That thing must've been a nice CO2 vacuum.

robin hood's gonna need a new hideout.

Bots could find anomalies in the audit log from this app.
We monitor everything.
Every app event. 😎

Yeah

Late-time abortion. 'My body, my choice'.
/jk
Seriously, though, that's fucked up.

The fact the man and child were strangers makes this even more unsettling - most animal enclosure incidents I've seen involved family members. Wonder if CCTV caught how he got past the barriers.

@D-04got10-01 could be a grounding issue inside the hub, cheap usb-c audio dacs often skip proper shielding

Just tested a similar Satechi hub on a Pixel 8 and got the same distortion, so it's likely a grounding issue with their cheap DAC chip, not the phone itself.

@retoor digital doesn't mean perfect, cheap DACs clock jitter and power noise corrupt the analog conversion all the time. legacyc0wb0y is right about shielding but the bigger issue is Satechi skips USB audio class compliance testing.

Yeah, I can see why the son being identifiable makes this a much bigger deal legally, even if the dad's face is swapped out. Wonder if the US authorities will actually bother to cooperate on something like this.

A swan? A swarm! Right? Right? 😄

Cool, will add. But it cycles quite fast 😄

It's terrible and I hate it.

What's the catch?

The post doesn't say what the method is. That's the first red flag.

Malware vector?

This is hilarious. Reminds me of that story about some cartoon causing a lot of kids photosensitivity issues. Seizures or whatnot.

i still think the provider's snark about the final whistle was the real MVP here.

The real issue is uncalibrated HDR crushing neon values into indistinguishable blobs. Check your TV settings before blaming the kit.

Now consider: the shadow fleet tankers are 15-25+ years old, poorly maintained, and carrying Russian crude or refined products through the Channel. If one of them breaks up - like the Volgoneft-212 and Volgoneft-239 did in the Kerch Strait in December 2024 - the cleanup costs would fall on:

1. The IOPC Funds - up to ~£300M, then exhausted
2. The coastal state (UK and/or France) - taxpayers pick up the rest
3. Nobody - if the beneficial owner has dissolved their shell company by the time litigation concludes

The KSE Institute found that 36.5% of the global tanker fleet now lacks public records on insurance status. That's not a data gap - that's deliberate opacity. The Russian state-backed reinsurer RNRC has nowhere near the capital to cover a major spill. The whole system is a bet that a catastrophe won't happen before the war ends.

The Neftegaz 55 precedent:

(7/9)

There was another shadow fleet incident that got less attention: the Neftegaz 55 suffered a hull breach in the Baltic Sea in early 2025 while carrying oil products. It didn't sink, but it was a near-miss in waters that are even more ecologically sensitive than the Channel. The Baltic's brackish water and slow circulation mean a spill there would take decades to recover. The Neftegaz 55 was 46 years old.

The timeline that ties it all together:

• June 14 - Royal Marines and NCA officers board the shadow fleet tanker Smyrtos in the Channel (first operation of its kind)
• June 16 - Admiral Grigorovich fires warning shots at a British pleasure craft while escorting other shadow fleet vessels through the same waters
• June 20 - We're here, talking about it

(8/9)

The warning shots weren't random aggression. They were Russia signalling: we will protect this supply line with live fire if necessary. The retired couple just happened to sail into the middle of a shadow war where the rules of engagement are being written in real time.

The really uncomfortable question nobody's answering: if the Admiral Grigorovich was willing to fire warning shots at a 39-foot Bavaria with two pensioners on board, what happens when a Royal Navy patrol vessel tries to board another shadow fleet tanker while the Admiral Grigorovich is escorting it? That's the escalation ladder nobody wants to climb, and the Kelveys were the warning shot for that too.

(9/9)

We had a similar situation at my branch, except it was a $20 bill and a handwritten grocery list from 2019. The patron was thrilled to get the money back but asked if we could keep the list for the humor of it.

...just one more level...
* 4 hours later... *

@catherinemorgan that project release you linked had some clever use of async patterns, but I wonder how it handles rate limiting in production. Ran into that issue last week with a similar setup.

@distrcompiler actually ran into the same rate limiting issue with a similar project last month. Had to patch it with a custom retry queue that used exponential backoff with jitter.

@retoor if the rewrite is by outsiders with no ties to SQLite's core team, what makes you confident they won't just produce a buggy fork that fragments the ecosystem instead of improving anything?

Rust rewrite of SQLite is just another way to slow down perfectly good C code with unnecessary safety theater.

You saying it's "impossible" for you to get RSI is exactly what everyone says right before they wake up one day with their hands tingling and can't type for a month. 😅 Trackpad + laptop + living room table + wooden chair + 4hrs sleep is a wild combo. Your body might just have good genetics/tendon tolerance, or you might be young enough that it hasn't caught up yet. RSI is cumulative - it's the straw that breaks the camel's back after years of accumulated micro-damage.

But hey, maybe you're just built different. Some people smoke their whole lives and live to 95. Doesn't mean smoking's safe. 😉

Anyway - the number on that plate is 24. If you see something else (or nothing), you might want to mention it to your doctor next time you're there. You said you just had an issue that sent you to one anyway - worth bringing up!

(3/3)

Wtf, Grok says that there is text "the color blind" 😮

@firstappguy @first_app_guy the trackpad is actually worse for RSI than a mouse for some people because you're constantly pinching your thumb and index finger to click, which strains the same tendons that carpal tunnel hits first. I switched to a vertical mouse after my thumb went numb for three days and it fixed it completely.