dweekly

Yay, I'd love to have your help!

1) Anyone can join the W3C group; you don't need to be a formal member of W3C!

2) What's dumb about the proposal itself? How could it better achieve its goals?

3) You can see some dialogue at https://github.com/WICG/proposals/issues/261 - what resonates and doesn't in the feedback and critique?

I've begun an AI content disclosure working group at W3C if folks are interested in helping to craft a standard that allows websites to voluntarily disclose the degree to which AI was involved in creating all or part of the page. That would enable publishers to be compliant with this law as well as the EU AI Act's Article 50.

https://www.w3.org/community/ai-content-disclosure/

https://github.com/dweekly/ai-content-disclosure

Hot saltwater is the worst substance on earth, excepting, maybe, hydrofluoric acid. You really don't want to cool things with ocean water over an extended period of time. And filtering/purifying it takes vast amounts of power (e.g. reverse osmosis).

Are there solutions to this like https://github.com/marketplace/actions/ssh-to-github-action-... ?

I heard Germans hate American root beer because they think it tastes like toothpaste and that very thought ruined root beer for me for a few years (until a sunny day when I was just dying for a root beer float and it absolutely hit the spot).

I think one interesting context to consider in this is cloud repatriation. Economics that didn't really pencil out half a decade ago may be worth revisiting for a lot of organizations who now find that their actual bare metal needs are quite modest and can be well met by a few modern servers. The IOPS/$ graph here contrasting on-prem w/cloud in particular is quite telling.

A solid refutation to the first point but not the second suggestion.

On slimness: wouldn't an alternative implementation be to "do the Magic Mouse" and put the USB C port on the back of the phone instead of the edge? Alternatively I could imagine MagSafe alignment / charging magnets plus an NFC like inductive communication (or contact pads) to allow for a range of "snap on" peripherals for phone backs that could be implemented on devices thinner than a USB C port.

There are two reasonable-sounding takedowns of any critique of an industry:

- You haven't worked in that industry so don't know what you're talking about, so be quiet.

- You worked in the industry that you are now critiquing and benefited from it, so be quiet.

Good points, all - there is a lot of subtlety here.

CFHostStartInfoResolution is deprecated, no? https://developer.apple.com/documentation/cfnetwork/cfhostst...:)

That leaves us with DNSServiceGetAddrInfo? https://developer.apple.com/documentation/dnssd/dnsservicege...:) or some kinda convoluted use of Network and NWEndpoint/NWconnection with continuations could do the same?

Whoops, my bad. Sorry.

I was able in an afternoon to implement a pretty decent completely async Swift DNS resolver client for my app. DNS clients are simple enough to build that rolling your own async is not a big deal anymore.

Yes, there is separate work to discern what DNS server the system is currently using: on macOS this requires a call to an undocumented function in libSystem - that both Chromium and Tailscale use!

The absolute zenith of mobile keyboards was the Blackberry, which included F & J nubs. I could type without looking at my phone at full speed and not get a character wrong.

The fact that Apple will as often as not autocorrect grammar from actually-correct to wrong -- and systematically screw up spelling -- in not just transcribed Siri but also in typing is just inexcusable at this point. It will even Randomly capitalize Certain words!

That model does not exist. Do you mean Opus 4.5?

Prior HN posts/discussions:

Chromium Team Re-Opens JPEG XL Feature Ticket https://news.ycombinator.com/item?id=46018994

FSF Slams Google over Dropping JPEG-XL in Chrome https://news.ycombinator.com/item?id=35589179

Google set to deprecate JPEG XL support in Chrome 110 https://news.ycombinator.com/item?id=33399940

Chromium jpegxl issue closed as won't fix https://news.ycombinator.com/item?id=40407475

Note prior HN Discussions on this topic:

FSF Slams Google over Dropping JPEG-XL in Chrome https://news.ycombinator.com/item?id=35589179

Google set to deprecate JPEG XL support in Chrome 110 https://news.ycombinator.com/item?id=33399940

Chromium jpegxl issue closed as won't fix https://news.ycombinator.com/item?id=40407475

Note Chrome ATLs formally declaring yesterday: "Since JPEG XL was last evaluated, Safari has shipped support and Firefox has updated their position. We also continue to see developer signals for this in bug upvotes, Interop proposals, and survey data. There was also a recent announcement that JPEG XL will be added to PDF.

Given these positive signals, we would welcome contributions to integrate a performant and memory-safe JPEG XL decoder in Chromium. In order to enable it by default in Chromium we would need a commitment to long-term maintenance. With those and our usual launch criteria met, we would ship it in Chrome."

https://groups.google.com/a/chromium.org/g/blink-dev/c/WjCKc...

There's some irony in that, given how many other companies have "created browsers" that are just Chromium forks and rubbed Google the wrong way.

The intro checklist for Antigravity includes watching VS Code tutorials!

Lovely find!

/Applications/Xcode.app/Contents/PlugIns/IDEIntelligenceChat.framework/Versions/A/Resources/AdditionalDocumentation/Swift-Concurrency-Updates.md

is exactly the primer to give an agent.

A few hours of playing around and I'm suitably impressed.

Claude 4.5 Sonnet definitely struggles with Swift 6.2 Concurrency semantics and has several times gotten itself stuck rather badly. Additionally Claude Code has developed a number of bugs, including rapidly re-scrolling the terminal buffer, pegging local CPU to 100%, and consuming vast amounts of RAM. Codex CLI was woefully behind a few months ago and, despite overly conservative out-of-the-box sandbox settings, has quite caught up to Claude Code. (Gemini CLI is an altogether embarrassing experience, but Google did just put a solid PM behind it and 3.0 Pro should be out this month if we're lucky.)

Codex with 5.1 high managed to thoughtfully paw through the documentation and source code and - with a little help pulling down parts of the Swift Book - managed to correctly resolve the issue.

I remember getting the thread manager right being one of the harder parts of my operating systems course doing an undergrad in computer science; testing threaded programs has always been a challenge. It's a strange circle-of-life moment to realize that what was hard for undergrads also serves as a benchmark for coding agents!

I appreciate the correction, anonymousiam! You are absolutely right - it's AM and for exactly the reasons you articulate.

Technically correct...and yet let's not kid ourselves that even with a nice radio and a pair of Bose A30's, it can be hard to tease out exactly what's being said when in a congested airspace.

As a commercial pilot, your response is a little glib and kind of ignores the meaningful advances that have been made with D-ATIS, ADS-B In, CPDLC, DUATS, XM weather, etc. Voice is absolutely not perfect, analog FM audio often comes through garbled, pilots have to wait their turn on a busy single-user channel for timely information, etc.

This doesn't even begin to touch on the complexities that will come from full integration of drones and eVTOL into the national airspace, which will absolutely swamp a one-speaker-at-a-time analog FM comms system.

I am so glad to hear your child got the care they needed.

I've found that people often forget to call their state senator or assemblyperson. It has consistently amazed me how quickly a large company that's sitting on their butts about a topic will move lickety-split once their Government Affairs and/or PR teams are on the thread...

Another tip from having worked at a regulated entity: a physical letter to the CEO mailed to HQ creates a mandatory-response paper trail that will produce a very, very different (better) outcome than e.g. asking to talk to a supervisor while on a call that's not going well.

Meta has been rolling out PQC: https://engineering.fb.com/2024/05/22/security/post-quantum-...

And Apple: https://security.apple.com/blog/imessage-pq3/

Cloudflare started rolling it out three years ago! https://developers.cloudflare.com/ssl/post-quantum-cryptogra...

The same argument could reasonably be used to explain why no YouTube influencer would ever get more than 1,000 subscribers - if everyone can upload videos that anyone can watch, nobody will really be famous because fame will become very evenly distributed, right?

Website: https://satcom.sysnet.ucsd.edu/

Wired: https://www.wired.com/story/satellites-are-leaking-the-world...

Genuinely curious: what could the Mars rover possibly capture about this object that other instruments cannot? Is it our highest resolution imagery in the vicinity of Mars?

So a social network that's 100% your friends doing silly AI things?

I feel like this is the ultimate extension of "it feels like my feed is just the artificial version of what's happening my friends and doesn't really tell me anything about how they're actually faring."

I'm working to build a tool for macOS and Windows desktops to help non-technical users figure out what's wrong with their home internet and how to fix it. https://www.networkweather.com/

It's literally just me in the garage right now banging out prototypes, talking to MSPs, and probing networks/WiFi/OS to make this tool.

The hope is that companies care whether employees are productive when remote/hybrid/on-the-road, or at least are sick of trying to triage first line helpdesk tickets about home network issues and Zoom glitches.