via this GitHub repository
We haven't written up this one. Simon Willison from Simon Willison’s Newsletter has the full story — the link below goes straight to it.
More in Tech
💾 Fighting DOGE's Data Grab | EFFector 38.19
When we give our private information to the government to pay taxes, apply for a job, or vote, we should be able to trust that our data won't later be used against us.
Nvidia debuts Nemotron 3.5 Transcribe, an open-weight model for multilingual audio transcription and translation, and Granary v2, its open-source speech dataset (Kyt Dotson/SiliconANGLE)
Nvidia Corp. today released a leaderboard-winning open artificial intelligence model for multilingual audio transcription and translation …
Last year’s Google Pixel 10 Pro is now cheaper than the Pixel 11 at Amazon
Go last-gen to save big on Android phones.
Check a domain's SPF and DMARC from code in 5 minutes (curl, JavaScript, Python)
Two DNS mistakes cause a lot of "why is our mail going to spam?" tickets: Two SPF records on one domain. The SPF spec allows exactly one v=spf1 TXT record.
- Multiple SPF records cause mail to be routed to spam folder
- DMARC record needed for domain owner's policy and reports
- Public DNS-over-HTTPS (DoH) resolver verifies SPF and DMARC quickly
Ofrenda Local: an offline ofrenda builder, and why a grandmother's sayings need one language per phrase
This is a submission for the Hacktoberfest Open-Source AI Challenge Week 4: Ghost in the Machine What I Built Ofrenda Local takes a voice recording of someone telling a story about a relative who…
Your trace UI can hide a secret that SQLite still stores
I made a tiny trace store hide a fake token in its display. Then I opened the database through a fresh connection. The token was still there. So was a made-up confidential sentence.
- Developer demonstrated hiding sensitive information in trace store
- SQLite database retained token and confidential prose
- Example highlights importance of proper logging practices