[[Knowledge Management]], [[Reproducible [[Social [[Science]]]]]], and [[Academic Workflow]]s – 100 Tweets for @threadapalooza 2020, let's go
#roamcult #𐃏
1/100

Pandoc is a magical piece of software, and if you're not using it for your academic writing you're missing out. Compile (basically) any document format to (basically) any other document format.
2/100
While Pandoc is fantastic, it's a bit like ffmpeg: extremely powerful, but without GUI apps too few people will use it. ffmpeg has a ton of GUI apps that basically just wrap the CLI, Pandoc doesn't have enough of them.
3/100
Citekeys + CSL files + Pandoc can easily cut ~10+ hours from your writing workflow. Citekeys come from LaTeX-Land, you can use them through Pandoc with anything. And CSL files make it super easy to switch citation styles.
4/100
Since many journals have their own version of popular formats, every journal should be required to publish a CSL file, LaTeX and Word Pandoc template ready for submission. I don't want to think about the collective hours wasted formatting stuff for submission.
5/100
Why Pandoc you ask? The one true document format are text files. Lindy effect - they've been around from the beginning, they will be around until the end. Everything else can be created from them – so write your stuff in text files, then use Pandoc.
6/100
"That contradicts your devotion to @RoamResearch!" Yeah, no. If Roam had shitty plain-text export like Evernote, sure. But I can get stuff easily as Markdown (plain text), so I lose nothing and gain a world of features. Use Roam, export to Markdown, publish w/ Pandoc.
7/100
Citekeys are powerful because they are unique ids for whole papers. And unlike DOIs they are _memorable_. citekey:doi = domain:ip
Think in terms of Roam, papers should have unique IDs for paragraphs, so I can do einstein1905movement/ASDJKSL to link to a specific paragraph
8/100
PDFs are a horrible format and should die in a fire. I don't know enough about document formats, but I know there are better ones out there that give the illusion of "uneditable" and that PDFs suck. But Lindy strikes again: we're stuck with them, I fear.
9/100
Talking about "permanence", I feel there's a lot of tension to be resolved around the question of "what do we actually know right now in this particular subfield"? The more we move to pre-prints and "public peer review", the less legible fields become, bc volume increases.
10/100
At least in the social sciences, there is way to much emphasis on "contributing to theory". I've received and seen others receive too much feedback along the lines of "this doesn't contribute much to theory". We need to falsify more, not introduce endless mods to theory.
11/100
Fun paper on that from International Relations
https://t.co/nZEKyxKGdq
12/100

More from Software

As the year wrap's up, let's run through some of the worst public security mistakes and delays in fixes by AWS in 2020. A thread.

First, that time when an AWS employee posted confidential AWS customer information including including AWS access keys for those customer accounts to


Discovery by @SpenGietz that you can disable CloudTrail without triggering GuardDuty by using cloudtrail:PutEventSelectors to filter all events.


Amazon launched their bug bounty, but specifically excluded AWS, which has no bug bounty.


Repeated, over and over again examples of AWS having no change control over their Managed IAM policies, including the mistaken release of CheesepuffsServiceRolePolicy, AWSServiceRoleForThorInternalDevPolicy, AWSCodeArtifactReadOnlyAccess.json, AmazonCirrusGammaRoleForInstaller.

You May Also Like

Recently, the @CNIL issued a decision regarding the GDPR compliance of an unknown French adtech company named "Vectaury". It may seem like small fry, but the decision has potential wide-ranging impacts for Google, the IAB framework, and today's adtech. It's thread time! 👇

It's all in French, but if you're up for it you can read:
• Their blog post (lacks the most interesting details):
https://t.co/PHkDcOT1hy
• Their high-level legal decision: https://t.co/hwpiEvjodt
• The full notification: https://t.co/QQB7rfynha

I've read it so you needn't!

Vectaury was collecting geolocation data in order to create profiles (eg. people who often go to this or that type of shop) so as to power ad targeting. They operate through embedded SDKs and ad bidding, making them invisible to users.

The @CNIL notes that profiling based off of geolocation presents particular risks since it reveals people's movements and habits. As risky, the processing requires consent — this will be the heart of their assessment.

Interesting point: they justify the decision in part because of how many people COULD be targeted in this way (rather than how many have — though they note that too). Because it's on a phone, and many have phones, it is considered large-scale processing no matter what.