The company I work for was nice enough to provide me with an entry to PyCon AU 2018 conference. I’ve spent three days there (Aug 24-26).
Update for my grannies: people are nice, food is average, the weather was subpar but I’m having a good time.
Here are the talk that I’ve attended + some random notes.
PyCon AU organisers were nice enough to publish all videos on YouTube - you can find them here.
Canary tokens - when opened they trigger an alarm.
Few ideas where they can be placed:
~/.aws/credentials
) - detect if a machine was compromised~/.ssh/config
- detect if your machine was compromisedCanary tokens don’t provide security by themselves but they have very good signal to noise ratio.
First of all I like the history part on Brian’s website - I’m thinking about stealing the idea.
The talk itself - interesting problem I wasn’t aware of.
The main idea: splitting names (or other details) into N-grams and put them into bloom filter to anonymise the data but perserve the basic properties that allow for Record Linkage.
Libraries available on GitHub:
I highly recommend watching this one. Key takeaways:
Desirable control attributes:
Interesting but TBH I have not made any notes
Interesting but TBH I have not made any notes
A really cool project. I liked the extra usage as a marker for interruption acceptance.
pyhap + Raspberry Pi + AirCon + iPhone = MAGIC
I watched only the first 2 presentations before heading to The Panel. From what I’ve seen it’s Machine Learning all the way.
Interesting but TBH I have not made any notes
I wanted to listen to this talk since I worked remotely for few years.
“Culture eats methodology for breakfast”
Right tools are crucial. Synchronous communication is overrated and technology is not there yet anyway.
This one got me really interested. I’m going to try a timing attack in practice - stay tuned!
Few side-channel attacks mentioned in the talk:
Types are good. Types are pythonic.
Projects:
Duck typing? Protocols!
Type information for Standard Library? Typeshed!
Something to play with: https://github.com/google/deepdream
Visual Studio Code Python extension has breakpoints/stepping/debug console/etc.
It has real debug console (one can execute code in a running process). Internally it uses Python Tools for Visual Studio debug server.
Setup costs :(
Alternatives to VSC: pdb (plain old Python debugger), spyder (full blown Python IDE).
The Creative Process:
Big life perspective: make a plan (prepare for bad events)
Key takeways:
Functional Programming in Python live in Jupyter Notebook!
Inspired by Professor Frisby.
Source code available here.
Adventure is a really old (probably the first) text adventure game implemented in Fortran IV. Chris created a Fortran IV interpreter to run it and he hooked it up together behind Twillio API. At time of writing it was accessible via text message on +61 488 847 569 or +1 (669) 238-3683.
He also put it online in a Python interpreter in JavaScript (yes, Fortran IV in Python in JavaScript) - hilariously slow.
That’s all folks! See you next year…
tags: pycon - python