Explanations are only given for commands not present in the original DuckyScript, for everything else refer to DuckyScript documentation.
These mean exactly what one would expect and should need no further explanation.
CTRL, CONTROL, SHIFT, ALT, GUI, WINDOWSCTRL-ALT, CTRL-SHIFT, ALT-SHIFT, ALT-GUI, GUI-SHIFT| from IPython.display import HTML, Image | |
| from google.colab.output import eval_js | |
| from base64 import b64decode | |
| canvas_html = """ | |
| <canvas width=%d height=%d></canvas> | |
| <button>Finish</button> | |
| <script> | |
| var canvas = document.querySelector('canvas') | |
| var ctx = canvas.getContext('2d') |
| #!/bin/bash | |
| #Beta 4 to Final Public Release (Must be run in Recovery Mode) | |
| csrutil disable | |
| #Beta 1-3 | |
| sudo nvram boot-args="rootless=0";sudo reboot |
We have absolutely no idea what we're doing in tech. Please explain the utmost basic things to us.
We only do web design. Our whole reason of being in tech is to make things pretty. Consider us the doilies of the industry.
We're not laughing about your joke, so we clearly need you explain it to us. In great detail.
We're only in tech to find a husband, boyfriend or generally to get laid.
View the submissions and vote!
HH and HH Design have teamed up to host the first Hackathon Hackers Design Competition!
The cover photo for Hackathon Hackers is OLD. Like ancient. Like it’s the same one uploaded the day this group was created. It’s time for an update.
The creativity of the hacker community knows no bounds. We’re hoping you can come up with cover photo concepts that capture the unique ethos of student hackathons. So take some time out of your holiday break, spin up your favorite image editor, and try your hand at branding HH.
| // Just before switching jobs: | |
| // Add one of these. | |
| // Preferably into the same commit where you do a large merge. | |
| // | |
| // This started as a tweet with a joke of "C++ pro-tip: #define private public", | |
| // and then it quickly escalated into more and more evil suggestions. | |
| // I've tried to capture interesting suggestions here. | |
| // | |
| // Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_, | |
| // @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant, |
| So you've cloned somebody's repo from github, but now you want to fork it and contribute back. Never fear! | |
| Technically, when you fork "origin" should be your fork and "upstream" should be the project you forked; however, if you're willing to break this convention then it's easy. | |
| * Off the top of my head * | |
| 1. Fork their repo on Github | |
| 2. In your local, add a new remote to your fork; then fetch it, and push your changes up to it | |
| git remote add my-fork git@github...my-fork.git |
