Keith Hörling khoerling

## plink-plonk.js
/*
Copy this into the console of any web page that is interactive and doesn't
do hard reloads. You will hear your DOM changes as different pitches of
audio.

I have found this interesting for debugging, but also fun to hear web pages
render like UIs do in movies.
*/

const audioCtx = new (window.AudioContext || window.webkitAudioContext)()

## upgrade.md

      
              1 file
            
          
              24 forks
            
          
              33 comments
            
          
              176 stars
            
          
                chrismccord
                / upgrade.md
            
            
              Last active
              April 7, 2023 12:03
            
              
                Phoenix 1.2.x to 1.3.0 Upgrade Instructions
              
          
    If you want a run-down of the 1.3 changes and the design decisions behidn those changes, check out the LonestarElixir Phoenix 1.3 keynote: https://www.youtube.com/watch?v=tMO28ar0lW8
To use the new phx.new project generator, you can install the archive with the following command:
$ mix archive.install https://github.com/phoenixframework/archives/raw/master/phx_new.ez

Bump your phoenix dep

Phoenix v1.3.0 is a backwards compatible release with v1.2.x. To upgrade your existing 1.2.x project, simply bump your phoenix dependency in mix.exs:

  
## Smurf.c
Well, I suppose its `safe' to release this, it seems everyone and their dog has
it and apparantly (and to my surprise) it still works.

The `smurf' attack is quite simple.  It has a list of broadcast addresses which
it stores into an array, and sends a spoofed icmp echo request to each of those
addresses in series and starts again.  The result is a devistating attack upon
the spoofed ip with, depending on the amount of broadcast addresses used,
many, many computers responding to the echo request.

Before I continue may I first say that this code was a mistake.  When it was

## motion.html
<!doctype html>
<html>
  <head>
    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="chrome=1">
    <title>Drifting Things</title>
    <style>

    body {
      text-align: center;
	/*
	Copy this into the console of any web page that is interactive and doesn't
	do hard reloads. You will hear your DOM changes as different pitches of
	audio.

	I have found this interesting for debugging, but also fun to hear web pages
	render like UIs do in movies.
	*/

	const audioCtx = new (window.AudioContext \|\| window.webkitAudioContext)()
	Well, I suppose its `safe' to release this, it seems everyone and their dog has
	it and apparantly (and to my surprise) it still works.

	The `smurf' attack is quite simple. It has a list of broadcast addresses which
	it stores into an array, and sends a spoofed icmp echo request to each of those
	addresses in series and starts again. The result is a devistating attack upon
	the spoofed ip with, depending on the amount of broadcast addresses used,
	many, many computers responding to the echo request.

	Before I continue may I first say that this code was a mistake. When it was
	<!doctype html>
	<html>
	<head>
	<meta charset="utf-8">
	<meta http-equiv="X-UA-Compatible" content="chrome=1">
	<title>Drifting Things</title>
	<style>

	body {
	text-align: center;