if you .delete and do a .delete immediately after as the describedd case.
You instantly delete two messages.
So a unmod in that window is unlikely.
it takes a finite time to update anything when anything changes. Or new API’s are added.
I did work when the announcements API was added. And I will do more work when shoutouts or pinned message API’s are added.
Doing work/spending time to update code when changes occur regardless of the type of change occuring.
Sure it’s may be an inconvenience as you put it. But work to support streamers to do what they need to do or want to do via the available API’s is just work. And continuing to support streamers to do what they need to do is not an inconvenience to me.
The same thing happens in any market segment as a developer. API’s change or update things are added or removed. Whether thats due to external factors (do not get people started on GDPR) or the services makes changes.
This change Twitch is making is what it is, things get added and removed or changed.
Nothing has been removed it’s just changed how it functions. It’s all moved from the socket to helix which brings third party operations inline with first party operations. Since first party isn’t sending these commands over the socket.
So sure its an inconvenience for third parties but better in the long run if things are “common” again between third party and first party. So we should get new features as quickly as first party does.
So is new features an inconvenience to you? (Like the announcements API thats a new inconvenience feature to you?)
You also get a USERSTATE in reply to regular PRIVMSG’s (as least periodically) iirc so you can track it there.
Or just process the 4xx body response when you do an API call to do a moderation action.
Or to every moderation task are you making a “am I a mod” call each time first?