I will say, this is nothing like a Dunkin’ Donuts flavored coffee or anything like that. You can still distinguish the flavor profile of the bean’s origin and such, just with a little bit of added complexity.

PERC is a local roaster for me and they’ve earned my trust with some exceptional traditional roasts over the years.

Yeah it’s certainly wild. It was a bit pricey but with a description like that, I had to check it out.

I hadn’t heard of co-fermenting before this either, but apparently they added dried strawberries and specific yeast strains to the fermentation tanks during the natural processing to influence the flavor. There are more details on the website.

I’ve never had a coffee’s tasting notes come through as prominently as this one does, absolutely crazy.

• Location: USA
• Retailer: Local PERC location
• Beans: PERC Colombia Young Producers - Single Origin: Antioquia, Colombia; natural process + red fruit flavor co-ferment; elevation: 1900 MASL; variety: Castillo, Caturra
• Roast: 74.2 agtron (medium-light)
• Advertised tasting notes: Pink Starburst & frosting
• Brew method: V60 pour-over
• My tasting notes: Intensely fruity. Less of a pink starburst flavor and more of a cherry or raspberry flavor, but that direct flavoring step really comes through.
• Price per unit: $29/13oz

(I added brew method since different brew methods can accentuate different tasting notes)

Just installed a soup profile on my GaggiMate earlier this week. I also picked up a bag of light roasted Ethiopian beans from my local roaster yesterday. This inspired me to finally try it out with a nice light roast.

Out of curiosity, what made you choose the Gagguino over the Gaggimate?

yeah that sounds like a totally mentally stable guy

Way better than mine looked when I first started learning. And better than the art on a latte I got at an actual expensive coffee shop today. Nicely done!

Qwen3.8 is out now and blows Qwen3.6 out of the water in pretty much every metric

I have a setup very similar to this. Although I’m fully on the Plasma Bigscreen bandwagon. But then again, I don’t have many custom services such as NFC login/custom background image logic like you do, and I doubt Plasma Bigscreen would play nice with that stuff. A couple of things I learned through my many attempts of setup:

• HDMI CEC doesn’t work on pretty much all x86 devices except for like some particular mini PCs, the Framework desktop, and the Steam Deck dock. Most ARM devices do though which is how I got around this by just using an Orange Pi 5. Another option is tunneling over DisplayPort if your device has a DisplayPort and you have a supported DP-HDMI adapter. Then finally, there’s also the PulseEight USB adapter if nothing else works.
• I’ve been using Waydroid for any application that doesn’t support Linux natively like YouTube or most streaming services (although I only use YouTube and Jellyfin for all of my content). You can use Waydroid Android TV which launches a near-native Android TV translation layer running Lineage OS which is de-googled and privacy protecting by default. You can launch the normal Android interface which has the entire Android TV UI, or you can enable multi window mode and just launch specific Android apps directly from whatever Linux launcher you use and they launch and work like normal Linux apps with TV controls. Very useful since Android has a much larger TV app ecosystem.

I wish I had some, but I honestly just follow all the standard guides I see online. Start with the wand just below the surface and inject air (paper tearing sound) for around 6 seconds, then bury the wand a bit deeper and find the right angle for a vortex, then keep it spinning until the pitcher is too hot to touch. Tap the pitcher a few times and swirl it around for a bit to pop the large surface bubbles and pour.

I follow this exact set of steps every time, and I still don’t get consistent results. I think the problem lies with the vortex step, I can never consistently find the right angle that produces a strong enough vortex.

I’ve been using the Flatpak version of Ungoogled Chromium for a while now (for websites that don’t work natively with Librewolf). Is this really that new?

I’ll probably continue working on my Swift GTK/libadwaita wrapper and the demo project that makes use of the library. Doing it this way has been very pleasant, it allows me to put it through real world tests and helps me identify stopgaps in the toolkit I wouldn’t otherwise notice through unit tests alone.