Aaand we have Keybase support on sigint.sx! Exciting stuff. I particularly like that Keybase are implementing a more generalised attestation flow than just integrating with yet another environment. https://keybase.io/docs/proof_integration_guide
It is proven! I am dave on Keybase: https://keybase.io/dave/sigchain#bb3e676b4ff50a182e689def0775341debe1589f055b1976f68215f8fd93fb240f
My top 3 picks for Eurovision, most likely first -
Latvia deserve a top spot, though not the win
Norway is super duper gay and I approve wholeheartedly
and I want some of what Portugal has been smoking.
@anna ah, nm, I've just seen you on the Keybase integration PR. I suspect that means it's just a matter of Keybase whims and they added contributors' instances as initial cases?
@anna What's the process of whitelisting an instance for Keybase? I've got sigint.sx on 2.8.0 but there's 0 documentation I can find.
Can you spare a few minutes?
I'm looking for information about terms - appropriate and otherwise - used to refer to various groups.
They will be used to build a resource explaining the "right" way to refer to members of those groups.
my favourite conspiracy theory
The speed of light is a hard limit for information propagation in order to mask the compute resource limitations of the simulation we live in.
The Planck length is the simulation's limit of atomicity.
Entanglement is a hack; two particles, each a pointer to the same memory.
There are many simulations, run in order to harvest the best media & art they produce for consumption by a hyper-advanced culture.
They're simulated too. It's simulations all the way down.
a cautionary tale of infosec just desserts
if you are going to be nontechnical, and if you are going to let your ego take the wheel by building a resort-wide wifi rollout, and if you are going to scab as much money as possible by charging silly money and using the cheapest possible gear, and if that cheapest possible gear means using a rinky dink little RB750 as the edge firewall and walled garden - if you are going to do all of that - then at least make sure you patch for CVE-2018-14847 yeah?