eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

216
active users

#devtools

4 posts4 participants0 posts today

🧠 Novità in Chrome #DevTools: con #Gemini è possibile modificare il CSS attraverso #prompt testuali, e salvare le modifiche direttamente nei file sorgente.

👉 I dettagli: linkedin.com/posts/alessiopoma

___ 

✉️ 𝗦𝗲 𝘃𝘂𝗼𝗶 𝗿𝗶𝗺𝗮𝗻𝗲𝗿𝗲 𝗮𝗴𝗴𝗶𝗼𝗿𝗻𝗮𝘁𝗼/𝗮 𝘀𝘂 𝗾𝘂𝗲𝘀𝘁𝗲 𝘁𝗲𝗺𝗮𝘁𝗶𝗰𝗵𝗲, 𝗶𝘀𝗰𝗿𝗶𝘃𝗶𝘁𝗶 𝗮𝗹𝗹𝗮 𝗺𝗶𝗮 𝗻𝗲𝘄𝘀𝗹𝗲𝘁𝘁𝗲𝗿: bit.ly/newsletter-alessiopomar 

Just published a blog post tearing into hCaptcha’s so-called “accessibility” mode.

It’s not accessibility. It’s a cookie. And to get that cookie, you now have to submit your email and send a code via SMS to an U.S. phone number. It fails silently. It doesn’t confirm anything. You click “Confirm Code” and get “An error has occurred.” No cookie. No fallback. No support. And if you somehow get it? It’s a third-party cookie your browser probably blocks, and it expires. Then you get to do it all again.

Meanwhile, hCaptcha’s text-based challenge — the only mode that might actually work with a screen reader — isn’t tied to the cookie at all. It only shows up if the website owner specifically enables it. Most don’t. So even if you’re blind, even if you’re using assistive tech, you get the same unusable image grid as everyone else.

This isn’t accessibility. It’s exclusion wrapped in PR.

The blog post breaks it all down: how the cookie flow works (or doesn’t), why the system is broken by design, how developers got misled, and what real alternatives look like. If you care about accessible design or just want to understand how bad this gets, read it.

Link: fireborn.mataroa.blog/blog/hel

fireborn.mataroa.blogHellCaptcha: Accessibility Theater at Its Worst — fireborn

🌀 Introducing **Chakra** - a blazing fast in-browser WebAssembly runtime for builders.

```sh
chakra myfile.wasm
```

– Runs WASM in-browser with logs
– Supports Rust, TinyGo, C, Asc and Python
– One-line introspection & verify commands

Chakra is an open source project and we're building it *with the community*.

🌟 github.com/anistark/chakra
📖 Read more: blog.anirudha.dev/chakra

Give us a shout-out or star the repo on github if you like the idea. 🙌

Run WebAssembly instantly in your browser with a single command. - anistark/chakra
GitHubGitHub - anistark/chakra: Run WebAssembly instantly in your browser with a single command.Run WebAssembly instantly in your browser with a single command. - anistark/chakra

💻 OpenAI just released Codex, its first full-fledged AI agent for software development — and it’s not just autocomplete anymore.

Key features:
🧠 Built on a fine-tuned “codex-1” version of the o3 model
⚙️ Operates in a containerized replica of your actual dev environment
📝 Accepts prompts and instructions via an AGENTS.md file
⏱️ Can spend up to 30 minutes on a task, showing its work step-by-step
✅ Still requires manual review before integration

Codex is designed to take on rote, low-complexity engineering tasks — with traceability and context. This could be a big leap toward agentic dev workflows, but also a test of whether AI can truly own small pieces of production code.

Rolling out now to Pro, Enterprise, and Team ChatGPT users. No extra cost (yet).

#AI #Codex #OpenAI #DevTools #SoftwareEngineering #AIagents
arstechnica.com/ai/2025/05/ope

Ars Technica · OpenAI introduces Codex, its first full-fledged AI agent for codingBy Samuel Axon