i was also lucky enough to visit athens years ago and see the mechanism in person at the national archaeological museum... it's an amazing exhibit, and if you're ever in that neck of the woods i cannot recommend it any more. :)
1,255 karma · joined January 23, 2017
i was also lucky enough to visit athens years ago and see the mechanism in person at the national archaeological museum... it's an amazing exhibit, and if you're ever in that neck of the woods i cannot recommend it any more. :)
one eight hundred cars for kids, for east coast kids to fly to israel on your dime!
also, praise be <diety> that these jingles will soon be off the air.
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!".
no. nothing is great. we are not good.
edit: here's the list of impacted universities (unsure if they all have their canvas instances offline, but i'd be surprised if not): http://91.215.85.103/pay_or_leak/instructure_affected_school...
now i'm considering deploying jenkins.
after seeing these comments, i just had to see for myself... and i couldn't even make it through the first section of the article.
> On HN we should try to get primary sources for this sort of thing.
+10000
feels like it's a race to the bottom here, and gitlab is starting to look even more appealing as the 9s disappear from github's uptime numbers.
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...
and yes: the supplied pc docs back then >>>>>>>> supplied pc docs today
```
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.
```
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. :)
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. ```
two other git log commands i find to be insanely useful are:
alias hlog='git log --date-order --graph --date=short --format="%C(green)%h%Creset %C(yellow)%an%Creset %C(blue bold)%ad%Creset %C(red bold)%d%Creset%s"'
and:
alias alog='git log --date-order --all --graph --date=short --format="%C(green)%h%Creset %C(yellow)%an%Creset %C(blue bold)%ad%Creset %C(red bold)%d%Creset%s"'
this is great when working in a repo w/a main "prod" branch that you don't commit to directly, but instead commit to "staging" or "dev". alog shows you the entire repo's history for all branches, and hlog is just the graph of the non-pushable branches (plus all feature branches).
i went a couple of months back, and absolutely fell in love w/her work... i highly recommend hitting this up!
i go at least 3-4 times a year for "something", with "something" being things like:
- a new bin for my inside recycling - an old street sign to use to plug the old sunroof on my 24 hours of lemons car - a door to use as a workbench - just to gawk at the massive selection of antique electronics
now i need to go check out the new museum! XD