L. David Baron dbaron

## security-privacy-review.txt
2.1 What information might this feature expose to Web sites or other parties, and for what purposes is that exposure necessary?

This exposes some information about user interactions (e.g., clicks or other activations), but I don't believe it exposes anything that isn't already exposed through DOM events and javascript.

2.2 Do features in your specification expose the minimum amount of information necessary to enable their intended uses?

I believe it's at least close to minimal, but see previous question (which makes this question less relevant).

2.3 How do the features in your specification deal with personal information, personally-identifiable information (PII), or information derived from them?

## gist:0c0eeda914ddc5f54d6fb126e7017d69
// see 'rustc -W help'
#![warn(missing_docs, unused_extern_crates, unused_results)]

//! An IRC bot that posts comments to github when W3C-style IRC minuting is
//! combined with "Github topic:" or "Github issue:" lines that give the
//! github issue to comment in.

#[macro_use]
extern crate log;
extern crate irc;

## sha256.html
<!DOCTYPE HTML>
<meta charset="UTF-8">
<title>sha256sum</title>
<script>

function buffer_to_hex(buffer)
{
  return Array.from(new Uint8Array(buffer)).map((e) => ("0" + Number(e).toString(16)).slice(-2)).join("");
}

## gist:3ef4577c6ff84bc0b997
### Keybase proof

I hereby claim:

  * I am dbaron on github.
  * I am dbaron (https://keybase.io/dbaron) on keybase.
  * I have a public key whose fingerprint is 9086 05EC 2288 051E FCD2  B071 EFE1 6125 0F84 FC21

To claim this, I am signing this object:
	2.1 What information might this feature expose to Web sites or other parties, and for what purposes is that exposure necessary?

	This exposes some information about user interactions (e.g., clicks or other activations), but I don't believe it exposes anything that isn't already exposed through DOM events and javascript.

	2.2 Do features in your specification expose the minimum amount of information necessary to enable their intended uses?

	I believe it's at least close to minimal, but see previous question (which makes this question less relevant).

	2.3 How do the features in your specification deal with personal information, personally-identifiable information (PII), or information derived from them?
	// see 'rustc -W help'
	#![warn(missing_docs, unused_extern_crates, unused_results)]

	//! An IRC bot that posts comments to github when W3C-style IRC minuting is
	//! combined with "Github topic:" or "Github issue:" lines that give the
	//! github issue to comment in.

	#[macro_use]
	extern crate log;
	extern crate irc;
	<!DOCTYPE HTML>
	<meta charset="UTF-8">
	<title>sha256sum</title>
	<script>

	function buffer_to_hex(buffer)
	{
	return Array.from(new Uint8Array(buffer)).map((e) => ("0" + Number(e).toString(16)).slice(-2)).join("");
	}
	### Keybase proof

	I hereby claim:

	* I am dbaron on github.
	* I am dbaron (https://keybase.io/dbaron) on keybase.
	* I have a public key whose fingerprint is 9086 05EC 2288 051E FCD2 B071 EFE1 6125 0F84 FC21

	To claim this, I am signing this object: