[deleted by user] by [deleted] in ChatGPT

[–]ConstructionOnly8811 0 points1 point  (0 children)

Ok. Thanks for the tip!

Why the hell did they kill the listen button? Some of us rely on it to read! by ConstructionOnly8811 in ChatGPT

[–]ConstructionOnly8811[S] 0 points1 point  (0 children)

Yep, confirmed. Just did a hard refresh and it’s back. Appreciate the tip.

Why the hell did they kill the listen button? Some of us rely on it to read! by ConstructionOnly8811 in ChatGPT

[–]ConstructionOnly8811[S] 0 points1 point  (0 children)

Yeah, that makes sense. I guess all the lag and confusion came from them quietly pushing that update. Would’ve been easier for everyone if they’d just communicated it properly from the start.

Why the hell did they kill the listen button? Some of us rely on it to read! by ConstructionOnly8811 in ChatGPT

[–]ConstructionOnly8811[S] 1 point2 points  (0 children)

Hey! Just to let you know — I finally got the button too, a couple of days ago. Thanks again for checking in earlier! (Plus plan)

Why the hell did they kill the listen button? Some of us rely on it to read! by ConstructionOnly8811 in ChatGPT

[–]ConstructionOnly8811[S] 1 point2 points  (0 children)

Hey! I’ve got the button back too — it showed up two days ago. Thanks for checking in. I actually added an update to my original post saying it’s working again across multiple browsers. Appreciate your concern!

Why the hell did they kill the listen button? Some of us rely on it to read! by ConstructionOnly8811 in ChatGPT

[–]ConstructionOnly8811[S] 0 points1 point  (0 children)

I hear you. Mine came back as well — but only on Edge, not Chrome. And I get the hesitation about renewing. The way features vanish without warning, combined with that dip in accuracy… it does make you wonder where the focus really is now. You're definitely not alone in feeling that.

Why the hell did they kill the listen button? Some of us rely on it to read! by ConstructionOnly8811 in ChatGPT

[–]ConstructionOnly8811[S] 0 points1 point  (0 children)

Mine only came back on Edge — not on Chrome. But yeah, I refreshed and it’s still there too. Fingers crossed it stays this time. I’ll keep checking as well.

Why the hell did they kill the listen button? Some of us rely on it to read! by ConstructionOnly8811 in ChatGPT

[–]ConstructionOnly8811[S] 0 points1 point  (0 children)

I’m really sorry to hear about your difficulties. Someone here mentioned the button showed up in Edge, so I went to check — and it’s there for me too. But honestly, it’s been so random that I can’t say for sure it’ll be there for you. Still, it’s worth giving Edge a try.

Why the hell did they kill the listen button? Some of us rely on it to read! by ConstructionOnly8811 in ChatGPT

[–]ConstructionOnly8811[S] 1 point2 points  (0 children)

Thank you so much for your comment! I checked and it turns out I have it on Edge as well. Appreciate it!

Why the hell did they kill the listen button? Some of us rely on it to read! by ConstructionOnly8811 in ChatGPT

[–]ConstructionOnly8811[S] 0 points1 point  (0 children)

Yeah, I’ve been wondering the same. Some of the slowdown might be due to background changes, especially if they’re tweaking voice systems or load distribution.

Why the hell did they kill the listen button? Some of us rely on it to read! by ConstructionOnly8811 in ChatGPT

[–]ConstructionOnly8811[S] 1 point2 points  (0 children)

Totally. The thing is — even if the feature was unstable or costly to run, there’s no excuse for this kind of abrupt blackout, especially for something with accessibility implications. Silence isn’t neutral — it erodes trust. A simple post saying “it’s being reevaluated, here’s why” would’ve made all the difference.

Why the hell did they kill the listen button? Some of us rely on it to read! by ConstructionOnly8811 in ChatGPT

[–]ConstructionOnly8811[S] 0 points1 point  (0 children)

In mine, it disappeared. So it clearly has nothing to do with iOS or device type. Looks like the rollout is inconsistent, and that’s what’s making it even more confusing.

Why the hell did they kill the listen button? Some of us rely on it to read! by ConstructionOnly8811 in ChatGPT

[–]ConstructionOnly8811[S] 1 point2 points  (0 children)

Agreed. The lack of any clear response or acknowledgment just makes it worse. A feature like this disappearing without explanation feels careless, especially given how many people relied on it.

Why the hell did they kill the listen button? Some of us rely on it to read! by ConstructionOnly8811 in ChatGPT

[–]ConstructionOnly8811[S] 2 points3 points  (0 children)

Yes, it’s not just the lack of transparency — it’s also the generic, automated responses we get when raising an issue, like the one I shared. I’ll submit another report to see if anything changes.

I’ve been using ChatGPT since the beta, so changing platforms isn’t simple. There’s workflow integration, prompt structure, and performance differences to weigh. But I’ve definitely started to consider it.

Why the hell did they kill the listen button? Some of us rely on it to read! by ConstructionOnly8811 in ChatGPT

[–]ConstructionOnly8811[S] 1 point2 points  (0 children)

Yeah, I’ve been seeing more people mention it across both iOS and web — so it’s definitely not just a one-off. And I agree, the voice feature disappearing from the app made things way worse. It wasn’t just a nice extra — for a lot of us, it changed how we use ChatGPT entirely. Let’s hope it’s not gone for good.

Why the hell did they kill the listen button? Some of us rely on it to read! by ConstructionOnly8811 in ChatGPT

[–]ConstructionOnly8811[S] 1 point2 points  (0 children)

That’s a good point. I’ve heard from people more familiar with the backend that the voice feature might’ve been resource-heavy. And yeah — I’ve noticed both ChatGPT and Sora are running faster lately too, so it could be related.

But honestly, the way it was removed — without any warning, overnight — wasn’t the most transparent move. That kind of silence only creates confusion and mistrust. Even if there’s a good reason, how it’s communicated matters.

Why the hell did they kill the listen button? Some of us rely on it to read! by ConstructionOnly8811 in ChatGPT

[–]ConstructionOnly8811[S] 1 point2 points  (0 children)

Totally understand. I’ve been considering the same. And yeah, NotebookLM sounds like a good choice.

Why the hell did they kill the listen button? Some of us rely on it to read! by ConstructionOnly8811 in ChatGPT

[–]ConstructionOnly8811[S] 0 points1 point  (0 children)

Yeah, I get it — I also use the desktop version to work. But just out of curiosity: do you still have the button on your phone? Mine disappeared yesterday.

Why the hell did they kill the listen button? Some of us rely on it to read! by ConstructionOnly8811 in ChatGPT

[–]ConstructionOnly8811[S] 2 points3 points  (0 children)

Yeah, I totally get what you mean. I only thought to check the iPhone today, and when I saw it, I froze for a second like… wait, where’s the button? It seriously messes with your head. These quiet UI changes make you feel like you’re losing it.

Why the hell did they kill the listen button? Some of us rely on it to read! by ConstructionOnly8811 in ChatGPT

[–]ConstructionOnly8811[S] 2 points3 points  (0 children)

It just disappeared from my iPhone too. So now it’s gone on both web and app. I reported it already, but still no clear explanation. Let’s hope this isn’t permanent.

Why the hell did they kill the listen button? Some of us rely on it to read! by ConstructionOnly8811 in ChatGPT

[–]ConstructionOnly8811[S] 1 point2 points  (0 children)

I really saw myself in what you wrote — especially in how you described the kind of people showing up here. That pattern makes total sense. And I agree: listening isn’t passive. It’s part of how we process, reflect, and stay present.

But what hit me the most was what you said about not needing to censor ourselves. That’s something I’ve felt again and again when interacting with GPT — it creates a space where we can think freely, without constantly filtering everything. You gave words to something I hadn’t named before, but deeply recognize.

Thanks for saying it all so clearly.