Alex HallI keep getting the error "endpoint not found" with FastSM. I'm on mastodon.social, so I wouldn't expect much server instability. And if that were the problem, I'd expect a 500-level error. A 404 suggests that FastSM is using an API endpoint that doesn't exist anymore. So far, it's only mentions that can't be updated.
Oh good, the problem is random. My previous post never appeared in my home timeline. I tried to send a reply just now, got a 404, and tried again. It sent. My notifications timeline got a 404, even though a new notification appeared. This is going to be fun.
Tim Appleby@alexhall Perhaps, it's time for you to migrate to another instance?
@carrottop1023 @alexhall No. It would be more appropriate to stop using fastSM until that is fixed. This is not an instance specific problem. I also had these issues and so did the majority of users I have spoken to. FastSM also has a very annoying taking up your resources when it can't properly fetch stuff problem.
@flamulous @carrottop1023 That's too bad. It wasn't a problem until this morning, and now it's persisted for hours. Knowing it's not an instance problem helps.
Al Puzzuoli@alexhall @flamulous @carrottop1023 I've been seeing the same thing today. FastSM has randomly given those errors since I've been using it but today it's every few minutes. I'm also on Mastodon.social for what it's worth. Switched to TWBlue for the moment, which is working fine.
@flamulous @alexhall Ah, good to know.