gszathmari

Welcome attendees? Privacy peep?

So you’ve signed up to CryptoAUSTRALIA’s Raspberry Pi (RPi) Pi-hole workshop.

To get the most out of the workshop, there are some items you should bring along.  You’ll be in of of two categories:
  1. Raspberry Pi owners bringing along a RPi to configure
  2. Not bringing a Raspberry Pi, but want to get the most out of the workshop. You may own a RPi or not bringing it along (because it’s powering your kegerator: https://philsprojects.wordpress.com/2014/03/10/smart-kegerator/ )


Raspberry Pi owner bringing their RPi

rouzbeh84

Guide Page

To start using this site you need to have a GitHub account to sign in. Once signed in it will create your profiles information based on your GitHub account and return you to your brand new profile page. Click the profile editor button to enter in if you want to be a student, partner or teacher. You should also enter in what skills you have and what skills you are looking to learn on this page.

Once you have your profile how you like it, head on over to the search page to look for what you want to use on your next project and what kind of partner you are looking for. After hitting the search button we will find the very best matches for you to begin your pair programming journey!

---

What is Pair Programming?

alexhanna

1. Code and Data for the Social Sciences: A Practitioner’s Guide, Gentzkow and Shapiro.
2. Good enough practices in scientific computing, Wilson et al.
3. Best Practices for Scientific Computing, Wilson et al.
4. Principled Data Processing, Patrick Ball.
5. The Plain Person’s Guide to Plain Text Social Science, Healy.
6. Avoiding technical debt in social science research, Toor.

• For background on Technical Debt: Wikipedia; D. Sculley et al., [Machine Learning: The High-Interest Credit Card of Technical Debt](https://ai.google/resear

quinnnorton

A Beginner's Guide to Media Whistleblowing

You're a tech novice, leaking to a reporter for the first time. Computers are confusing. Encryption is a very long and very tiring word. The people who know how to do this all talk like holier-than-thou jackasses. (Spoiler: we pretty much are.) Here's a quick, hopefully beginner-friendly guide to safer leaking.

1. Don't use your phone. There are some marginally safe ways to use phones, but you're not going to manage them. Just put it down, and never try to do anything terrible or heroic with a cell phone. The same is true of email.

2. Don't do anything from your work, your house or your regular haunts. There's various ways of tracing things back, and you don't want to have to worry about them.

3. Use someone else's WiFi. A cafe or a library, or better yet, the laundromat or cafe next to the one with the WiFi you're using. This takes a little investigation, but it's not hard. Get a few passwords as a customer and think about where you can sit unobtrusi

quinnnorton

Source Protection in 2017: A Starter Guide

Like sex, there's no such thing as safe leaking. But there is safer leaking, and ways to encourage your sources to be safer.

The next few months (like the last few weeks) will see a lot of people who want to talk about their life and their work with a media audience; people who never wanted to talk before. If they come to us, and by us I mean journalists, we need to be ready and equipped to protect them, whether what they tell us becomes journalism or not. We also need time. We need to be in a position to check stories, cross check references, and talk to experts to make sure the leaks we receive are true and right and placed in the appropriate context. We get all this from protecting our sources from discovery by governments, corporations, or individuals.

First off, initial contact is the hardest step to keep secure and private. But it is doable. Journalists, you should use social media profiles, bylines, and web pages protected by https to tell potenti

quinnnorton

The Problem with Slack

Don't ever say anything on Slack you don't want read aloud in front of a 72 year old Alabama judge in federal court.

Collaboration software is great, but it's also great for getting penis pictures into public court records. People are comfortable on Slack, which is what makes it so effective, and so very dangerous, especially for news teams. We are shit-talking motherfuckers, with the occasional penis jokes (I mean who doesn't love a good penis joke). There's the one kind of trouble being overheard at a bar, and then there's persistent logging of everything we say on remote servers. This isn't an esoteric, theoretical threat. This is how Gawker died, after their Campfire chats were subpoenaed and entered into court records. Fusion wrote about this at the time: http://fusion.net/story/278532/gawker-hulk-hogan-sex-tape-trial-chat-transcripts/ in an article where they also talked about using Slack. Because, presumably, bad things only happen to other journalists. Bonus dipshit point

bbqsrc

• Australian Taxation Office (ATO) identity fraud and debts 107-02010020
• Investigating the source and cause of the debt 107-02020020
• Locating debts from the Activity Search (AYS) screen 107-02030010
• Debt recovery information for non Debt Management Officers 107-02050010
• Reports and systems information for Centrelink debt management 107-02060000
• Overview of the Debt Management and Information System (DMIS) 107-02060010
• [Debt Management and Information System (DMIS) screens 107-02060020](http://operational.huma