We just had "`rlogin` to every machine in the lab, run `who`, and collate the output". IIRC there was an early version written by 'flup that I extended with a tidier output (including an X11 window), auto-refreshing, and easier machine selection (eg. you could select rooms by name with regex filtering.)
Good times.
I'm not suggesting you don't do this, but you /could/ setup a speaker to play the classic remix of Steve Ballmer's "developers! developers!" whenever there are >=2 people in the room. On April 1st, of course.
I hope this is intentional
> I hope this is intentional
I mean, it's not unintentional..
Eventually I realized that it just made sense to suck it up and get my own hardware, as it was either going to be esoteric "workstation" hardware with a fifth of the horsepower of a Pentium 75 or it was going to be in a room like the UPL jammed with CRT's and the smell of warm Josta.
How do students operate these days? Unless one is interacting with hardware, I'd be very tempted to stay in "fits on a laptop" space or slide to "screw it, cloud instances" scale. Anyone with contact in the last 5 years have a sense of how labs are being used now?
It's firmly in "not a laptop" scale, and for anything that fit it was much faster than all the modern cloud garbage.
The other lab I was in around that time just collected machines indefinitely and allocated subsets of them for a few months at a time (the usual amount of time a heavily optimized program would take to finish in that field) to any Ph.D. with a reasonable project. They all used the same in-house software for job management and whatnot, with nice abstractions (as nice as you can get in C) for distributed half-sparse half-dense half-whatever linear algebra. You again only had to share between a few people, and a few hundred decent machines per person was solidly better than whatever you could do in the cloud for the same grant money.
In my recent physics experience, this is basically what it was unless you had to rely on some proprietary software only on the lab machines like shudders LabView
Computers were also ubiquitous in places like the coffeehouse, the library, practically every classroom, etc. And, of course, there were ubiquitous WiFi and USB charging ports, so that students with BYOD could get by (although WiFi was often overloaded and contentious.)
Within the main computer lab I was using, there was also a networking hardware lab, with genuine Cisco equipment such as routers and switches. The Cisco certification prep classes would go in there and do experiments on the hardware, so that students could get accustomed to seeing it in action, however outdated it may be.
The lab itself was chock-a-block with both Apples and Windows PCs, as well as scanners and printers available, and even headphones you could borrow from the desk attendant. You'd need to sign in and sign out. There were strict rules about silence and not leaving your station unattended. There was always space for more users and a generally relaxed atmosphere, where people could feel comfortable studying or doing homework.
I believe that there was also an A/V lab where students could get access to cameras and recording equipment, as well as software for that kind of thing.
The library, in addition to allocating lots of space for Windows PCs and Apples, would also loan out Chromebooks to any student, and I believe they had other things for loan, such as WiFi hotspots, for kids who couldn't afford to carry around their own Internet.
There were also Tutoring Centers, such as the Math one, where most of the desks featured a computer where you could log in to your collegiate account, and access your online course materials.
And the Testing Center was essentially a big computer lab, with cameras and in-person proctors monitoring it. It was partnered with Pearson and CompTIA, so I took more than one certification exam in there.
There is a fully-staffed IT Help Center on campus, so during office hours, you could count on a 1:1 in-person interaction to help you get logged in, debug your device's WiFi, or whatever.
Despite having a great computer setup in the comfort of my own home, and plenty of online courses on my schedule, I still appreciated the immersion of collegiate computer labs, and especially the relaxed coffeehouse access, where I could use Apple systems to work on my English homework and essays.
During the COVID-19 pandemic, all this went topsy-turvy, and a lot of these labs closed down, or took extreme health precautions, and of course, a lot more classes went online-only. But I was done with classes by that time.
Someone wrote a script to finger everyone in the entire CS department and tell when the lab was busy, by counting people logged in.
This work fine, except for on intro courses where some labs had lots of non-CS majors in them.
`Finger Stacy` would run every minute and typically be running for 15 minutes max... that is until I moved into the dorms and my machine was online all the time.
A few weeks go by and I get an email from the SDSU admin requesting that I stop fingering stacy as it was bothering the other Sysadmin. I remarked with a grin that all I was trying to do was in fact try to `name of the command` and they promptly deleted the script from the account.. It still makes me smile as I write this.
https://door-status.ucc.asn.au/ucc
Runs off a Raspberry Pi with a bodged-up version of https://github.com/ide/pico-door-sensor/tree/main
This is at least the third iteration; some previous iterations are documented here:
This way, we don’t need to mount anything on the door, we just have a microcontroller plugged into one of the machines.
Our previous solution was a webcam that pointed to the lights that did a similar thing (implemented by someone before my time) but then it stopped working due to some driver issues, and I didn’t want to spend time investigating them.
I know you mentioned patents pending, but is there anything you can share about your approach?
[1] https://www.alibaba.com/product-detail/IoT-Commercial-People...
One thing from and old cranky dev that I notice: it would seem the yml you post has redundancies: either have 4 endpoints, no payload or 4 different payloads, one endpoint (the endpoint itself can tell you what you need to do) However, from the express script it looks like you arrived at this in the final solution anyway. Not sure if I missed something though, is there a reason the API needs such a shape? Cheers!
One of my more fun HA project was scraping my snow removal service's tractor tracking API and passing the result for the closest tractor into HA so I can be notified (by voice with Alexa and/or push notification) when there's one nearby in case I need to move the car.
Which is to say, heathens who have yet to accept our lord and savior Duct into their hearts. (And its latter day saint WD-40)
Source: have done similar hobby projects for fun, which turned out to be illegal.
It is. Check your jurisdiction.
Who's talking about that?
Almost nowhere (or actually nowhere?) are you allowed to set up a surveillance device into a space that is not public and it is not owned by you.
Obv. IANAL and this is not legal advice.
if you did, where would you have set them up at anyway? Asking for a friend
Wrong. They're state property, you even wrote it there.
>Obv. IANAL
Obv.
or
"of or relating to a government"
If you're on someone else's property, they can of course set any number of rules, and trespass those who break those rules. But even there, recording people, if against the rules, is still not a crime. The crime is trespass, if this journalist we're speaking of sticks around after being trespassed off the property.
Meanwhile in reality: https://leginfo.legislature.ca.gov/faces/codes_displayText.x....