| # The PICO-8 text printer for the ClockworkPi DevTerm! | |
| # | |
| # This Python script allows you to print text directly from the PICO-8 source | |
| # code editor. The script runs in the background and watches for you to execute | |
| # the "EXPORT FILE.LUA.PNG" command. It does some light processing of the | |
| # generated image file, then sends it to DevTerm's thermal printer. | |
| # | |
| # This is mostly just a joke/hack for the purposes of this tweet: | |
| # https://twitter.com/dan_sanderson/status/1434253649266364417?s=20 | |
| # |
WHOA THERE probably go look at this first: https://nytpu.com/gemlog/2021-04-15.gmi seriously it's so good
Setting up to Flash
Fresh Flash First Steps
The purpose of this tutorial is to walk through the required steps to upgrade NXT chip (or pocketchip) from debian jessie to debian buster.
If you would like to start your Chip from scratch, follow the steps in the Preparation section.
A linux host machine, recommended Ubuntu 18.04. However I managed to do it with 20.10 with some tweak.
| #!/usr/bin/env bash | |
| set -Eeuo pipefail | |
| trap cleanup SIGINT SIGTERM ERR EXIT | |
| script_dir=$(cd "$(dirname "${BASH_SOURCE[0]}")" &>/dev/null && pwd -P) | |
| usage() { | |
| cat <<EOF | |
| Usage: $(basename "${BASH_SOURCE[0]}") [-h] [-v] [-f] -p param_value arg1 [arg2...] |
Hi I'm Simone! This recipe was developed based on some tips I acquired over time from lots and lots of resources and tutorials like youtube videos, family and friends recipes. I'm just an amateur who likes making pizza :)
If you plan to perfectionate your pizza making skills, I suggest to come up with your own recipe and research online watching lots of tutorials and different techniques. For now the following recipe is the one that works for me!
(I'm not a professional pizzaiolo and I never had any sort of experience in a professional pizzeria restaurant)
| (function(root) { | |
| Object.assign(document.body.style, { | |
| 'transform': 'perspective(500px) rotateY(12deg) rotateX(9deg) rotateZ(-4deg) translate3d(56%, 26%, -516px)', | |
| 'transform-origin': '0 0', | |
| 'transform-style': 'preserve-3d' | |
| }) | |
| const node_style = { | |
| 'outline': '3px solid rgba(255,0,150,0.5)', | |
| 'transform-style': 'preserve-3d', |
| # Place file in | |
| # /etc/NetworkManager/conf.d/90-disable-randomization.conf | |
| [device-mac-randomization] | |
| # "yes" is the default for scanning in Fedora 25 | |
| wifi.scan-rand-mac-address=no | |
| [connection-mac-randomization] | |
| ethernet.cloned-mac-address=random | |
| wifi.cloned-mac-address=random |
I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.
I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.
Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.
