I am teaching a class and have a developer account with team access. The flow for my students is they create an account, share the handle with me, I invite them to the team, they get credentials and do their assignment.
Many, about 1 in 3, are getting 403 Forbidden when they run any command. When I run on my credentials there is no error. When they run on my credentials there is no error. When I run on their credentials I get the error. I can attach six screenshots so far from the many students who have encountered this, but two will suffice since that’s the forum limit and this clearly isn’t a client-side issue.
Possible leads:
- At least two students encountered this along with another error I just posted. So for some of my 1/3 of students, the 403 is due to not having credentials…
- … but some students are invited, accepted, verified, have credentials, and are still getting 403. Possibly some get it because they never accepted while others got it because they never verified? This is all really hard to diagnose since I’m not encountering these issues directly
- I thought it might be a verification issue, because several students just created their accounts for this class and have been forced to wait a week before they can verify, but one student encountering the problem has a 3yo account with email and phone both already verified.
- They are all accessing Twitter from a single IP (the IP of the machine hosting the class notebook server). Perhaps twitter doesn’t like so many accounts coming from one machine? But even if they’re on the same team?
- I’m certain that most of these students are entering their credentials correctly.
This problem is interfering with my ability to provide 100 students with access to the Twitter API, more if it continues into upcoming terms. That isn’t good for me, them, or Twitter. Please prioritize this issue so that I can continue to rely on the stability of Twitter for teaching introductory programming.
