Not exactly - unless you mean “Creating Tweet Alerts” by “receiving tweets through the app”. Tokens are only needed for posting tweets.
Ordinary users and those wishing to follow your alerts just need to follow one of your accounts - like
TAMUCM_LAW (i’m assuming those are the ones you mean)
When telling people to follow these accounts - i’d also suggest strongly encouraging people to “Turn on mobile notifications for this account” - that option appears after you follow an account in the
... burger menu on web or as a Bell icon in the App - people might miss it, or not realise it’s there. This will mean that their twitter app will very likely generate a phone notification (not SMS) any time the emergency account tweets (but you can’t 100% guarantee these app notifications).
Only the “Owner” account’s Access Token is visible in the Developer Pages - As for other Authenticated accounts, you are right - no, they are not visible and these should be kept separately and managed by you somehow.
Nope - It doesn’t matter how those tokens are generated, with Twurl or something else - they don’t expire. To properly invalidate / reset tokens you can log in using the account on twitter, and go to https://twitter.com/settings/sessions and remove the application there. Or if it’s the application owner, also in the developer App page under Keys & Tokens, or using a call to https://developer.twitter.com/en/docs/basics/authentication/api-reference/invalidate_access_token after invalidating the newly created token will be different
The limit for the number of accounts you can Authorize to one application is something like 100,000 last time i checked. But these are just for the accounts that will be tweeting alerts, anyone wishing to receive alerts isn’t limited in any way.
Oh, and as for using
twurl, i just noticed that it doesn’t actually output the Access tokens after successfully authorizing, it stores them in a
.twurlrc file - so they can be found there.
The whole process should be down to Log in to twitter web as
twurl authorize --consumer-key ... --consumer-secret ..., open the webpage, enter the PIN from there in twurl, open
.twurlrc (should be in home directory) to save the tokens, log in as a different twitter user
TAMUCM_LAW, run twurl again, etc… Don’t know how many accounts you need to do this for but it shouldn’t take that long.
Incidentally, while logging in to those accounts to authorize, that would be a good time to make sure other settings are enabled like passwords / security, unnecessary apps are not enabled on those emergency accounts, the emails and phone numbers in settings are valid, descriptions link to the site and other stuff like that. Hope that helps!