Show Navigation
Conversation
Notices
-
!Friendica Admins As you might have heard, there are issues with the Twitter API. Several favourite clients stopped working, while others (still) do. By now there hadn't been any word if there is some massive Problem or if this was some deliberate action.
Whatever is causing these issues, at least my connection still works. How about yours? Is the Twitter connector on your systems still running?
- Bob Jonkman repeated this.
-
Twidere has stopped working for Twitter accounts. My Mastodon account still works nicely. I thought maybe the Twidere API keys for the developer had been revoked, or that something had gone wrong with my phone (It's a vanilla Samsung with Android 12, but I've refused to install any of the Samsung or Google apps). I tried to re-authenticate my Twitter account with "Basic" (userID and PW; other options are OAuth, OAuth2, XAuth), but even "Basic" didn't work.
My Slim Social for Twitter app continues to work, tho. But Slim Social doesn't seem like it's an app, but just a browser that only goes to twitter.com.
I think this may be the event that makes me abandon Twitter altogether. I had reduced my Twitter activity since the Musk takeover, but hadn't entirely given up on it. Fortunately, I don't have any investment in anything I've posted there. I've always put #ImportantStuff on my blog or other self-hosted services.
-
I seem to recall there's a standard API that should be common to all the #StatusNet derivitave servers. I'm pretty sure that in its infancy Mastodon conformed to that API. But Mastodon's API expanded beyond that, and I suspect some of the common API was removed, probably around the time #OStatus was dropped from Mastodon too.
But that's sheer speculation on my part.
Time to upgrade my server, so I can upgrade PHP, so I can upgrade this GNUsocial instance...