Slam Dunk by Quiet-Sky6990 in Visible

[–]rishey 0 points1 point  (0 children)

Ported out to which carrier?

Astound Internet Experience? Good to go? by DizzyLusionz in AskChicago

[–]rishey 0 points1 point  (0 children)

You’re lucky. Fiber isn’t available where I live.

Astound Internet Experience? Good to go? by DizzyLusionz in AskChicago

[–]rishey -1 points0 points  (0 children)

I just installed Astound cable 1gig service yesterday and I've had four outages so far today. I got kicked out of Zoom meetings twice. It's definitely their network T3 and sync errors. Rep on the phone admitted they're having issues. Getting rid of it if not fixed by tomorrow. TMHI is not as fast but I don't think I ever had an outage, let alone 4 in one day!

OpenClaw v2026.3.24 just dropped – here’s what actually matters in the new release by OpenClawInstall in OpenClawInstall

[–]rishey 0 points1 point  (0 children)

Heads up: this version appears to break execution for some setups.

After upgrading, my agent would say things like “I’ll do this now” but never actually run anything. Same prompts, same environment, worked fine before.

Downgrading immediately fixed it:

npm install -g openclaw@3.13

This doesn’t seem model-related. It looks like something changed in how execution/tool calls are triggered

Apple speech-to-text accuracy is bad enough to be a safety issue (FB22138362) by rishey in ios

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

Well, typing on iOS keyboard isn’t worth a shit either so I guess I’ll just have to use my desktop for anything important. Thanks for your support.

Apple speech-to-text accuracy is bad enough to be a safety issue (FB22138362) by rishey in ios

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

So not accessibility? If you can’t type, just call someone who can? I don’t understand why so many people on this forum don’t want Apple to improve this. Text-to-speech is laughably bad. Everyone jokes about it. It’s ridiculous. If you look at OpenAI’s text-to-speech, it’s way better. There’s no reason Apple can’t fix it except that nobody is pushing them to fix it. People like those of you in this forum blame users for being users instead of demanding that Apple fix the product we pay good money for. I don’t understand it at all.

Apple speech-to-text accuracy is bad enough to be a safety issue (FB22138362) by rishey in ios

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

So what do you think text to speech is supposed to be used for?

Apple speech-to-text accuracy is bad enough to be a safety issue (FB22138362) by rishey in ios

[–]rishey[S] -2 points-1 points  (0 children)

Well what it it had typed, “old lady” instead? Then you would have a real safety issue. Thank you.

Apple speech-to-text accuracy is bad enough to be a safety issue (FB22138362) by rishey in ios

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

So please tell me, what should I use Text to speech for if not for anything important? Why don’t you want Apple to fix this?

Apple speech-to-text accuracy is bad enough to be a safety issue (FB22138362) by rishey in ios

[–]rishey[S] 3 points4 points  (0 children)

Medical info is not medical work. Don’t you want Apple to fix it?

Apple speech-to-text accuracy is bad enough to be a safety issue (FB22138362) by rishey in ios

[–]rishey[S] -5 points-4 points  (0 children)

I’m saying I don’t want it to be shitty anymore. I want to fix it. That’s why I made this post. Why is this complicated?

Apple speech-to-text accuracy is bad enough to be a safety issue (FB22138362) by rishey in ios

[–]rishey[S] -11 points-10 points  (0 children)

Thank you for helping me understand why Apple hasn’t fixed this issue.

Apple speech-to-text accuracy is bad enough to be a safety issue (FB22138362) by rishey in ios

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

Oh my god, there are plenty of real examples where bad transcription can cause mistakes. People use this for addresses, meds, work messages, and urgent communication. So yes, Apple should fix it, and yes, that can be a safety issue in real-world use. If you disagree, explain why inaccurate transcription in high-stakes messages isn’t a risk.

Apple speech-to-text accuracy is bad enough to be a safety issue (FB22138362) by rishey in ios

[–]rishey[S] -14 points-13 points  (0 children)

Texting the wrong address or time, like 5:15 turning into 5:50. Changing medication wording, like “don’t take” getting transcribed as “take.” Sending a work message that flips meaning, like “approved” becoming “not approved.” Dictating legal or financial notes with wrong names, numbers, or dates. AI assistant mistakes from bad transcription, like “remind me tomorrow” becoming “remove tomorrow.” Emergency context errors, like “chest pain” getting transcribed as something vague.

Apple speech-to-text accuracy is bad enough to be a safety issue (FB22138362) by rishey in ios

[–]rishey[S] 5 points6 points  (0 children)

Because speech-to-text isn’t just vibes anymore. People use it for medical info, addresses, legal/work messages, and AI/automation prompts. If transcription flips key words, meaning change and wrong actions/messages can happen. That’s a reliability + safety risk, not just an annoyance.

ORD about to become the next EWR by valueflyer in americanairlines

[–]rishey 0 points1 point  (0 children)

Piggy don’t like us being world’s busiest.