I think it is a result of the impersonal "contact us" intake forms companies have all moved to. You have no indication that you aren't just screaming into the wind. There is no personal touch. So you take to social media where your are sure at least someone hears you. It also scratches the justice itch: if the company doesn't pay attention it looks bad in public and you get some vindication for being ignored.

I'm not saying it's a good or bad thing to do, but I understand it.

I don't know. I'm always confused when social media accounts ask to report issues over different channels when it's so much easier to just reply to customer and ask for additional (non PII) information there. In this case it's unlikely that this was the only or even first report about this issue. So why place the initial burden on a paying customer? If your social media is just a marketing channel, at least make that clear so i don't even bother reporting issues that route.

I am the OP.

I admit my second message was terse, but the correct social media response for a critical outage is "we're looking into it". Not "if you want support, go here".

Like I said, I do not have time to hunt for whatever support channels exist and file a ticket. I pay $50 a year so they can deliver a working product, including triaging their own issues.

> Next week, DOGE and IRS leadership are expected to host dozens of engineers in DC so they can begin “ripping up the old systems” and building the API, an IRS engineering source tells WIRED. The goal is to have this task completed within 30 days. Sources say there have been multiple discussions about involving third-party cloud and software providers like Palantir in the implementation.

Well yeah, obviously bring in Palantir. 10x the headcount so they can have the task completed in 3 days.

I hoped OpenAI would support OpenAPI for connecting to tools. Having created a couple of MCP servers, it feels like a less flexible and worse documented API to me. I can’t really see anything that is made better by MCP over OpenAPI. It’s a little bit less code for a lot less options. Give it some time and it will also get Swagger built in.

It’s solving a problem that was already robustly solved. So get we go with another standard.

I am not sure I agree that we lack major economic indicators flashing red.

For instance, GDPNow from the Atlanta Fed looks quite bad at the moment: https://www.atlantafed.org/cqer/research/gdpnow

I also have been looking at deliquency rates on industrial equipment leases lately, and they seem to be trending sharply upward: https://www.fitchratings.com/structured-finance/abs/equipmen...

Major retailers are also managing expectations for the next quarters. It seems like they're bracing for soft aggregate demand.

For this to work they must have already done facial recognition on everyone’s ID photos, so I fail to see what opting out even does for me from a privacy perspective. Seems like shutting the barn door after the horse is already out.

Does anyone else want to talk to Siri like a normal human? Like an actual assistant?

It drives me nuts that Siri can't interact correctly when spoken to like this: 'Siri, could you text my wife that I will be home in 20 minutes'

Converts to:

Text Wife: That I will be home in 20 minutes

Should be: I will be home in 20 minutes

Drives me nuts. This is what I actually want. It's just so much more natural. This is my biggest grievance with virtual assistants. I want to talk to it like a real assistant. Hopefully after the LLM refactor of Siri this will happen, but on 18.2, still doesn't work with redesigned Siri. I don't know if they have added the LLM integration with her, but I thought they had in 18.2