Chaos broke out among the BA Blueprint staff following website blockage.
BREAKING NEWS: BA Blueprint staff became locked out of their website on December 18th around 8:00 AM. Chaos and disorder soon followed.
On December 18th, the BA Blueprint website became blocked for student access. The issue was eventually resolved by 8:20 AM, however, the time period between the outage and the restoral of the website contained an immense amount of chaos.
The play by play was as follows:
- From 8:00-8:02 AM, the Blueprint staff made their way into the classroom. Mr. Naylor has a track record of being anywhere from two to five minutes late to class, however today seemed to be a good day for him.
- From 8:02-8:05 AM, the staff had gotten settled into their seats and many quickly started realizing the website was blocked and inaccessible.
- By 8:05-8:08 AM, the staff realized the severity of the situation. Editor in Chief Olivia Hess was first to realize, and she soon became panicked and passed out.
A picture snapped of Blueprint advisor Kerry Naylor in the midst of the madness. (Abigail Eckenrod) - Following that from 8:08-8:10 AM, two separate tribes of staff members started forming. The one tribe was arguing for the website to be unblocked so they could continue normal operations, however the opposing tribe argued to leave the site blocked so they didn’t have to do any work. Staff Writer Kate Wallace commented this after the fact: “I’m just trying to write my stories, man.”
- From 8:10-8:12 AM, a small fire was created during an argument between the two tribes. This in turn escalated the chaos and furthered tensions.
- Between 8:12-8:15 AM, the tribes continued bickering back and forth. Some turned to yelling. All the while Blueprint adviser Mr. Naylor was huddled in the back row underneath the desks desperately trying to get in contact with the technology support staff.
- By 8:15-8:17 AM, total chaos and disarray broke out. Chairs had been thrown, computers had been smashed, and the small fire was starting to grow. The staff team had turned into savages, and nobody thought there was going to be a happy ending to this.
- By 8:17-8:20, the technology support staff had gotten back to Mr. Naylor and fixed the website blockage. Operations slowly returned back to normal following the outbreak. Although the issue was resolved, some staff members were still experiencing issues. Because of this, they were exiled from the class and expected to work in the hallway.
Overall, the tragedy that occurred that day will go down in Blueprint history as one of the worst staff infighting to date. As of now, amends have been made, but the awkwardness still persists between staff members.
