i work tech at a university that's impacted by this. while it doesn't impact me directly, many many other staff and instructors i know are heavily affected by this outage. the students are absolutely outraged, mostly because the university hasn't been providing updates as quickly as they'd like, but since the staff/admin are waiting on word from instructure -- and there hasn't been a lot from them, it just generally sucks for all of us.
this is really, really, REALLY bad. it's not great that names/emails/etc will potentially be leaked, but also private messages between students and instructors. and since many of the campus systems rely on canvas integration, things have pretty much ground to a halt a week before finals.
after they were breached on the 1st of this month, instructure had an announcement yesterday that "everything is great! we're good! hackers are gone! we've rotated our keys!".
i did the circleci --> github actions migration for my job 1.5 years ago, and things seemed great... at first. at the time, we'd been dealing w/circleci's semi-regular (but thankfully short) outages for over two years, and we were excited to move to a more stable system.
> Am I reading this right, possibly a $100k fine and up to 20 years in prison for a biological man posting a picture of themself dressing in clothing considered "female"?
yep, i believe you are. i wonder how they'll deal with men wearing scottish kilts? or women wearing pants?
this is insane and i can't see how this would even come close to passing in to law...
the pc as purchased in 1992 had a i486DX2-66... after a few years, that case received numerous upgrades -- moar ram, moar disk, various amd and cryix 5x86/6x86 cpus over time. trade shows in the 90s were just full innovation and cheap, performant hardware!
oh man, what a trip down memory lane. i started building PCs in college with 386/486s and last year rebuilt my silly custom loop watercooled workstation. :)
and yes: the supplied pc docs back then >>>>>>>> supplied pc docs today
...which makes is a non-starter for many academic settings:
```
Limitations
You may not provide the software to third parties as a hosted or managed
service, where the service provides users with access to any substantial set of
the features or functionality of the software.
about ~30 years experience. devops/architect now at a major university.
dropped out after almost 7 years w/4 degrees (math, cs, photography, archaeology). yes, i have adhd lol.
i've been programming/building computers since the early 80s, and worked at my unis computer lab help desk starting in the early 90s. after dropping out, got a lame sysadmin job and then somehow got a job at nasa ames in the late 90s (and moved to the bay area). after a short stint there, i was super lucky and hit the job marked right as the dot-com bubble 1.0 ramped up!
it was tough for the first few years as my lack of degree (and general jack-of-all-trades skillset) was definitely a barrier.
but with lots of luck, perseverance and track record of learning quick on the job, i was able to get a solid career rolling. i quit tech about 12 years ago, and have been working in higher ed tech since. now i get to sit in meetings and explain to CS/data science profs how the cloud actually works. :)
hard no for me WRT positron... i managed a university's jupyterhub deployments for a while and we had faculty CLAMORING for this vs. Rstudio.
the problem? the fact that you need a license to use. it's not OSS. you are not allowed to deploy this on a hosted/managed system:
```
Limitations
You may not provide the software to third parties as a hosted or managed
service, where the service provides users with access to any substantial set of
the features or functionality of the software.
You may not move, change, disable, or circumvent the license key functionality
in the software, and you may not remove or obscure any functionality in the
software that is protected by the license key.
You may not alter, remove, or obscure any licensing, copyright, or other notices
of the licensor in the software. Any use of the licensor's trademarks is subject
to applicable law.
```