This bit is important.
At a glance, stubhub/ticketmaster/etc are pretty benign services that fulfil a pretty natural need for event tickets, but we've all seen the damage they can cause. There's a very real risk that OP's service could become a ticketmaster for UW classes, with all the perverse incentives that entails. Their reaction was probably excessive, but, from this perspective, understandable.
So while it sounds like his site would almost certainly wound up violating policy had it gone live _it never did so_. That's a pretty good reason for them to deny the API request (which seems like may have not been intended for the public anyway?) But it does not in any way seem to merit the threat of expulsion, or, even worse, the fact that (according to the student in an update), even though he immediately complied they still put a hold on his account anyways.
There is some nuance here for sure, but I do not see in any way that the universities response is proportional to what actually happened.
Still shit to lock him out after he pulled the site down.
While well-intentioned, if this was commonly used it would mess registration up even more by making the "constrained" classes valuable and would be filled up quickly by people who wouldn't take them.
There may have been some browser automation scripts about… I wouldn’t know.
You do have to be signed typically to actually make changes of course, I imagine this tool would have to have your netid login… (yikes)
I sign up for a class. I am on the roster. How is it possible for me to put your name on the class roster, for credit, transcript, and diploma, without the university going out of their way to help?
These aren't anonymous concert tickets or XBoxes. They are personally identifiable registrations.
This is important, because it's the only explicit reference to "trading open spots" they've made.
The Registration Abuse policy covers access to the registration system for:
* buying or selling one’s seat in a class,
* holding seats for another student,
* or otherwise registering for a section that one has no intention of taking.
It's unclear if HuskySwap actually violated this policy, given that it never actually accessed the registration system and no students used it in conjunction with the registration system of the school.
What isn't clear is how this site actually violated that policy, if there was no course slot trading actually occurring. You could describe it as an attempt, but in this situation, the student asked for permission from the school before doing something that would violate their policies.
To use an analogy, if I sneak notes into an exam, that is likely academic misconduct. However, creating a formula sheet and asking the professor if I can use it is not academic misconduct. I wouldn't consider that to be attempted cheating.
> The use of robots and other automated tools to submit registration requests is expressly forbidden.
Some sort of testing will likely have happened, in which case an automated tool has been used. Even if only by TFA himself.
Also note:
> Because use of scripts, robots, or other automated queries can adversely impact University network and computing resources and interferes with equal access to registration, such automated querying of registration-related resources is expressly forbidden. Violators may have their access to University network and computing resources terminated and may be subject to action by the University under applicable law, regulation, or policy, including but not limited to, discipline under any applicable University conduct code.
The whole purpose of the project is to violate this clause. I agree that if no testing had happened, no sanctions should apply because the clause above doesn't say anything about attempts of use being sanctioned.
1. They made substantial progress towards a working tool with available code, before requesting permission from the school. That request was to enable parts of the site, not requesting permission to develop/release it publicly.
2. It is pretty clear to students that you aren't allowed to mess with any of the registration systems/process (e.g. trading/holding classes). Your analogy has a very reasonable question (are notesheets allowed) vs a policy which is made very clear.
A different analogy is creating a hidden device to cheat on exams, then asking the professor for the exam room's wifi password as to enable it it in the future. While the situation is not as clear-cut as the analogy, I hope it helps show my perspective.
Until the author has used the tool on the UW server during registration, he is not violating their policies and procedures: He hasn't attempted to tamper with records. He admittedly hasn't used their registration system with this tool. Those are the two key phrases in their policy. The text goes on to specifically describe abuse as "use" of a script or robot. There isn't anything forbidding a student from authoring a script.
One problem here is that by releasing the source, it makes it easier for another student to exploit the system. In the case where another student uses this tool during registration, the other student is fully responsible.
Besides all that, it's a great project idea because everyone in his program would instantly relate to the problem.
It's easy to understand the University's overreaction---and it is an overreaction. The better solution from UW would have been to sternly inform the student(s), "The website can never go live. It dies as a proof of concept. Please use your own dummy data; no API access. A disclaimer must be added to any class demos (presentations, code, etc.) with the Tampering and Abuse policy, and that this only uses generated data. Our efforts to improve the registration system in the future will be X, Y, Z."
This student has done nothing wrong (yet) (based on what he revealed) and is getting punished for being near the border.
In my old days we did the same, only by finding someone who want to swap manually
So if you are planning to sell the slots and it does not work out, you just drop the course, no harm to you.
I won’t say no harm but you have to be pretty desperate to try to pull this off
It also just fucks with the University's ability to gauge class interest. In my university, if a class filled up early in the registration window, the University would try to increase capacity or add another copy of the class, but that's not always an option.
A reminder that this is not done for technical reasons. Plenty of colleges all across the US, big and small, custom-built registration software or purchased on the open market, have fully functional waitlist features. "first come first serve" is a policy choice.
Why can't UW increase the number of classes?
He was disciplined for blatantly trying to "hack" (in the YC sense, in UW's view) the registration process:
https://registrar.washington.edu/winter-2025-registration-ch...
"Know that trading, selling, or buying open spots is a breach of the Registration Tampering Abuse Policy. Consequences include referral to the Student Code of Conduct process, a Registrar’s Hold on your record, and potential diploma withholding for graduating students until the conduct process is complete."
https://registrar.washington.edu/registration/policies-proce...
"Registration Abuse The registration system is provided for the sole express purpose for students to register themselves into sections. Any use of the registration system other than for this purpose is considered abuse of the system. Such abuse includes, but is not limited to, buying or selling one’s seat in a class, holding seats for another student, or otherwise registering for a section that one has no intention of taking."
Disclaimer: I am making no claim about the ethical validity of this policy, and I don't know how well the policy is communicated to students. I am not commenting on the allegation that the University demanded free labor in exchange for not-expelling OP.