I built a little demo where you give three models (Apertus, Llama, Qwen3) the same prompt and in the end you have to guess which is which just based on their answers.
A live community radio for AI-generated songs, powered by tracks created with ACE-Step.
You can tune in, discover community-made songs in many languages, vote on what sounds good, and mark your real favorites as Bangers.
The more people listen, vote, and create, the better the station gets.
Under the hood, it connects a few Hugging Face pieces together:
Spaces for the live app, HF buckets for community tracks, OAuth for signed-in listeners, server-side streaming with ffmpeg, hourly playlist refreshes, moderation, jingles, and community feedback loops.
It’s not just a playlist.
It’s a shared taste experiment: new songs get a shot every hour, and the community helps decide what deserves another spin.
Come listen. Find weird gems. Support the Bangers. Shape the radio.
Great technical guide by Nico Martin on the Hugging Face blog, showing how to use Transformers.js inside a Chrome extension and run ONNX models from the Hub locally with WebGPU inside a Manifest V3 extension.
The interesting part: this is not just a chatbot in a side panel.
The article walks through the architecture behind a browser agent that can read open tabs, query webpages, search history, and highlight elements directly on the page — with models downloaded from the Hugging Face Hub, cached under the extension origin, and executed locally instead of being called through a remote API for every prompt.
A strong blueprint for building local-first web copilots, reading assistants, and AI-powered browsing workflows.
The paper asks a simple but important question: what if the chatbot interface is not just a neutral wrapper around AI models, but part of the problem?
A chatbot can make a system feel more capable, more certain, and more “human” than it really is. That matters, because interfaces shape how we trust, use, and delegate to AI systems.
When everything becomes: ask → answer we can lose sight of the actual workflow: - parameters - alternatives - uncertainty - intermediate steps - failure modes - human control
For creative AI especially — image, video, editing, animation — I’m not sure “chat” should always be the default interface.
Sometimes we need a conversation. But often we need a canvas, a timeline, sliders, masks, previews, comparisons, and visible pipelines.
This is also why I find many open ML demos interesting: Spaces, Gradio apps, visual tools, small focused interfaces.
They often explore another direction — not just better assistants, but better tools. 🤗
PASD isn’t recent, but still delivers strong results — worth restoring rather than replacing.
Getting it to run again wasn’t a simple dependency issue. It relied on parts of diffusers that no longer exist, while moving to Gradio 6 forced a much newer HF stack — and I couldn’t modify the original source directly.
Recreating the old environment wasn’t practical. So I patched the downloaded code at runtime before import and made it compatible with today’s stack.
That ended up being the only approach that held without forking or freezing everything to outdated versions.
If you’ve used it before (or are curious), feel free to give it another try.
My TIGER app is now fully working again, with fixes and full compatibility with Gradio 6 🚀
It lets you: - 🎙️ Separate multiple speakers from an audio file - 🎬 Extract each speaker directly from a video - 🎧 Split audio into dialog, music, and sound effects (DnR) - 🎥 Apply DnR separation directly on videos
All powered by lightweight TIGER models for fast and efficient speech separation.