diff --git a/src/pages/blog/upl-people-counter.md b/src/pages/blog/upl-people-counter.md
index 4fc54a6..76c8453 100644
--- a/src/pages/blog/upl-people-counter.md
+++ b/src/pages/blog/upl-people-counter.md
@@ -77,40 +77,121 @@ It was around this time that I stumbled upon the homepage of [MITERS](https://mi
ℹ️
Note - Added 11/25/2024
- In response to this article's release, I've received a lot of questions asking me why I made the choice to track the status of the doors, rather than other attributes of the room. Many of these questions came from my post on Hacker News, as well as the article posted on Hackaday -- where one particularly amusing comment accused me of "...not looking at [the project] from a systems point of view." Here's my response to some of those questions, in no particular order:
- Why not...
-
+
+ In response to this article's release, I've received a lot of
+ questions asking me why I made the choice to track the status of the doors,
+ rather than other attributes of the room. Many of these questions came from
+ my post on Hacker News, as well as the article posted on
+ Hackaday
+ -- where one particularly amusing comment accused me of "...not looking at
+ [the project] from a systems point of view." Here's my response to some of
+ those questions, in no particular order:
+
+ Why not...
+
- ...point cameras at the doors?
- - That could work too! However, it would just be far more complex than simply attaching the two Zigbee sensors on the doors -- I would have to train a model to recognize the difference between viewing the interior side of the UPL versus the CS walkway.
+ -
+ That could work too! However, it would just be far more complex than
+ simply attaching the two Zigbee sensors on the doors -- I would have to
+ train a model to recognize the difference between viewing the interior
+ side of the UPL versus the CS walkway.
+
-
+
- ...point the camera at the lights of the room?
- - One of the main things that people seemed to be confused about was the difference between tracking the state of the room versus its occupancy. The key distinction is that people being in the room doesn't necessarily indicate that it's open to the public. There could be coordinators having a meeting (or a maintenance person in there cleaning, and so on). Yes, it would be possible to have other ways of knowing whether there are people in the room (like the other suggestions mentioned here), but none indicate its status as well as the doors (other than people just writing "the room is closed to the public" on Discord).
+ -
+ One of the main things that people seemed to be confused about was the
+ difference between tracking the state of the room versus its
+ occupancy. The key distinction is that people being in the room
+ doesn't necessarily indicate that it's open to the public. There could
+ be coordinators having a meeting (or a maintenance person in there
+ cleaning, and so on). Yes, it would be possible to have other ways of
+ knowing whether there are people in the room (like the other
+ suggestions mentioned here), but none indicate its status as well as the
+ doors (other than people just writing "the room is closed to the public"
+ on Discord).
+
-
+
- ...use a technological solution to detect devices in the lab?
- - I saw a few suggestions about this -- namely, this one by zdw mentioning the finger command, as well as this comment by zimpenfish about using rlogin and who to determine who's logged into the network. Well -- the UPL doesn't have desktop computers available for students to come in and use anymore. Most students just bring their laptop, as computers aren't necessarily hard to come by anymore...! We don't have the infrastructure (at least, right now) to allow students to ssh into our servers, and even if we did, there would be no way of telling if they were doing it on-premises. As for using WiFi/DHCP leases to detect devices (as recommended by q3k in this comment): UPLians use UWNet or eduroam, not the UPL's own WiFi network. There's also some privacy-related concerns about snooping/logging/aggregating users, even if anonymized, that highly dissuades us from implementing anything like that.
+ -
+ I saw a few suggestions about this -- namely,
+ this one
+ by zdw mentioning the
+ finger command, as well as
+ this comment
+ by zimpenfish about using
+ rlogin and
+ who to determine who's
+ logged into the network. Well -- the UPL doesn't have desktop computers
+ available for students to come in and use anymore. Most students just
+ bring their laptop, as computers aren't necessarily hard to come by
+ anymore...! We don't have the infrastructure (at least, right now) to
+ allow students to ssh into our servers, and even if we did, there would
+ be no way of telling if they were doing it on-premises. As for using
+ WiFi/DHCP leases to detect devices (as recommended by q3k in
+ this comment): UPLians use UWNet or eduroam, not the UPL's own WiFi network.
+ There's also some privacy-related concerns about
+ snooping/logging/aggregating users, even if anonymized, that highly
+ dissuades us from implementing anything like that.
+
-
+
- ...just use an online reservation/booking system?
- - The UPL isn't a conference room. While there is a list of the coordinators' individual hours, the actual occupancy of the room doesn't necessarily follow that schedule. Sometimes coords miss their hours, and other times the room remains open until 5am. All that to say: it is not possible to simply do a schedule lookup to determine the status of the room, and having preset times for determining occupancy would be inaccurate fairly often.
+ -
+ The UPL isn't
+ a conference room. While there is a list of the coordinators'
+ individual hours, the actual occupancy of the room doesn't necessarily
+ follow that schedule. Sometimes coords miss their hours, and other times
+ the room remains open until 5am.
+ All that to say: it is not possible to simply do a schedule
+ lookup to determine the status of the room, and having preset times for
+ determining occupancy would be inaccurate fairly often.
+
-
- - ...use WiFi signals to get an accurate number of the people in the room?
+
+ -
+ ...use
+ WiFi signals
+ to get an accurate number of the people in the room?
+
- - Uh... wow. That's insanely cool. But it still doesn't expressly convey the intent of the room's use. It would still be neat to have a count for the number of people as well as the status of the room, so I'm definitely stashing this away in my head.
+ -
+ Uh... wow. That's insanely cool. But it still doesn't expressly convey
+ the intent of the room's use. It would still be neat to have a
+ count for the number of people as well as the status of the room,
+ so I'm definitely stashing this away in my head.
+
-
- Hopefully that can answer some of the most common questions I've gotten about the project. Thanks for reading!
+
+ Hopefully that can answer some of the most common questions I've gotten
+ about the project. Thanks for reading!
+
I considered using similar components for a door status checker for the UPL -- it wouldn't have been too much effort to buy WiFi enabled ESP32 modules and off-the-shelf door-mountable reed switches. Then, I would have the chips simply send a POST request with their status every time the door was opened or closed.
