ept

Notes from Coed:Ethics conference, London, 13 July 2018

Cori Crider - "When data kills" / Weaponised AI

• Imam Salem bin Ali Jaber preached in Yemen against Islamic extremism; guest at a wedding of relative; hit by a US Hellfire missile fired from a drone. Relative Faisal made contact with Cori, went to Washington DC. No explanation ever made by government (although compensation was paid).
• Decision-making process behind the attack not known exactly. But there is significant evidence that such attacks serve to further radicalise people; attack results in ~3x more new recruits than extremists killed by attack.
• Most drone attacks are not on named individuals, but rather "signature strikes" — a euphemism for killing people the military doesn't even know, but who match a certain behavioural pattern (perhaps based on metadata — Hayden: "we kill people based on metadata"
• Skynet (known through Snowden relevations): use machine learning to try to find courier

arshiamufti

Online Accounts

1. Move all your login credentials to a password manager. Do a security audit. Update any weak passwords, change any duplicate passwords. If you've saved any passwords in the browser, delete them (and maybe even change your passwords for those accounts for good measure).
2. If you're using biometric login (fingerprints, voice unlock) for any important accounts (such as online bank accounts), don't.
3. Use keybase to authenticate yourself. They have really good setup instructions.
   • You'll need to generate a public key. You can have Keybase do this for you, but it's better to generate one yourself on your machine and upload it to Keybase. The public key can now be used by anyone if they want to securely communicate with you!
4. Set up 2-factor authentication for all your important accounts. I've done this for (so far) Google, Facebook, Twitter, Digital Ocean, and Github. It's best to use an authenticator app (like Authy or Google Authenticator) instead of SMS.

• Also download recovery

andrestc

About this

This list has the goal of helping developers interested in contributing to the Go language but are unsure of where to start. This was not generated manually so some functions and methods here may not require examples (maybe because they are too simple, e.g .String()) and some of these may only make sense in a package level example (which are not considered for this list yet). Use your best judgment and check the documentation before you open up a CL to add an example.

You should also search in gerrit for open CLs that are already adding examples.

I will try to keep this list as up to date as possible. If you find any mistakes, please comment below and I will try to fix it.

cep21

package main

import (
	"fmt"
	"io"
	"net/http"
	"net/http/httptest"
	"net/http/httptrace"
	"os"
)

sdorra

/*
 * Genarate rsa keys.
 */

package main

import (
	"crypto/rand"
	"crypto/rsa"
	"crypto/x509"

andineck

database, messaging, distributed system, kafka

siburu

package main

import (
	"fmt"
	"log"
	"syscall"
)

const filePath = "data.dat"

mbbx6spp

Gerrit vs Github: for code review and codebase management

Sure, Github wins on the UI. Hands down. But, despite my initial annoyance with Gerrit when I first started using it almost a year ago, I am now a convert. Fully. Let me tell you why.

Note: This is an opinionated (on purpose) piece. I assume your preferences are like mine on certain ideas, such as:

• Fast-forward submits to the target branch are better than allowing merge commits to the target branch. The reason I personally prefer this is that, even if a non-conflicting merge to the target branch is possible, the fact that the review/pull request is not up to date with the latest on the target branch means feature branch test suite runs in the CI pipeline reporting on the review/PR may not be accurate. Another minor point is that forced merge commits are annoying as fuck (opinion) and clutter up Git log histories unnecessarily and I prefer clean histories.
• Atomic/related changes all in one commit is something worth striving for. Having your dev

kchida

- What do Etcd, Consul, and Zookeeper do?
  - Service Registration:
    - Host, port number, and sometimes authentication credentials, protocols, versions
      numbers, and/or environment details.
  - Service Discovery:
    - Ability for client application to query the central registry to learn of service location.
  - Consistent and durable general-purpose K/V store across distributed system.
    - Some solutions support this better than others.
    - Based on Paxos or some derivative (i.e. Raft) algorithm to quickly converge to a consistent state.
    - Centralized locking can be based on this K/V store.

cee-dub

package main

import (
	"fmt"
	"log"
	"net/http"
	"time"
)

// SSE writes Server-Sent Events to an HTTP client.