Indeed.
It would also mean, in the case of follows, you can utilize webhooks, which for follows, would only need a app access token (no user ID), which you can make at will, and the user just needs to provide the twitch username/password, (no auth), course if you are adding subscriber events you’ll need a user token.
Then you just need a way for the frontend/alert display to connect to your server for the feed of events.
And having a “real” server or AWS serverless, you can persist a follow cache for as long as you see fit server side, without relying on local store (streamer updates OBS, which might dump localstorage or other $things affecting localstorage as OBS browser source is seperate chromium instance to the main browser on the computer), and the user decides “I’m gonna try xsplit today” or “I’m using a new PC” or “streaming from my friends/conference place” etc