# writeup Published articles for writeup. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Cloud provider postmortems: volume vs depth DevFeed: [Cloud provider postmortems: volume vs depth]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-08-05T00:00:00Z Content type: opinion Language: en Sources: [Sridhar Rajarao]() Topics: [Cloud](), [incident](), [SRE](), [site-reliability-engineering](), [engineering-culture]() Tags: [2017](), [2025](), [2026](), [aws](), [azure](), [cloud](), [dynamodb](), [engineering-culture](), [gcp](), [incident](), [incident-management](), [postmortems](), [s3](), [sre](), [transparency](), [writeup]() ### AI overview The article compares public postmortem practices among Google Cloud, Azure, and AWS. It argues that Google Cloud emphasizes high volume and speed, Azure emphasizes detailed transparency and customer accountability, and AWS publishes fewer writeups with greater depth and industry influence. ### Source excerpt GCP publishes 100+ postmortems a year. AWS publishes almost none. Azure has become the transparency leader. What each posture reveals about engineering culture, and what SREs should steal from all three. ## Results from the Advent of FPGA Challenge DevFeed: [Results from the Advent of FPGA Challenge]() Original publisher: [Read original article]() Author: Anish Singhani Published: 2026-02-11T00:00:00Z Content type: article Language: en Sources: [Jane Street]() Topics: [fpga](), [Advent of Code](), [Hardware](), [Verilog](), [Algorithms]() Tags: [advent-of-code](), [algorithms](), [competition](), [fpga](), [hardware](), [writeup]() ### AI overview Jane Street reports the results of its Advent of FPGA Challenge, a hardware-design competition run alongside Advent of Code. The article describes participation statistics, the hardware description languages used, and examples of notable submissions. ### Source excerpt At the end of last year, we decided to try something new: a challenge that would run alongside Advent of Code, where we asked the community to show us how they could design hardware to solve the same problems. We had no idea what level of participation to expect, but we received a huge number of submissions, many of which were incredibly creative! ## Advent of Code in C++ Template Metaprogramming DevFeed: [Advent of Code in C++ Template Metaprogramming]() Original publisher: [Read original article]() Author: Nelson Elhage Published: 2023-12-08T15:30:00Z Content type: tutorial Language: en Sources: [Nelson Elhage]() Topics: [Advent of Code](), [C++](), [Code](), [Compiler](), [polyfill]() Tags: [advent-of-code](), [c-plus-plus](), [code](), [compiler](), [polyfill](), [writeup]() ### AI overview An annotated walkthrough of solving the first Advent of Code problem using purely compile-time C++ template metaprogramming. It covers compile-time input handling, folds, helper types, and state tracking to calculate calibration values. ### Source excerpt This December, the imp of the perverse struck me, and I decided to see how many days of Advent of Code I could do purely in compile-time C++ metaprogramming. As of this writing, I've done two days, and I'm not sure I'll make it any further. However, that's one more day than I planned to do as of yesterday, which is in turn further than I thought I'd make it after my first attempt. ## Snyk Fetch the Flag CTF 2023 writeup: Off the SETUID DevFeed: [Snyk Fetch the Flag CTF 2023 writeup: Off the SETUID]() Original publisher: [Read original article]() Author: Carlos Polop; Yago Gutiérrez Published: 2023-11-30T10:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [snyk](), [ctf](), [Kernel](), [Processes](), [qemu](), [HTTP](), [PHP](), [C](), [Server](), [Network]() Tags: [awareness](), [blog](), [c](), [compiler](), [ctf](), [developer](), [external](), [http](), [kernel](), [network](), [php](), [process](), [qemu](), [security](), [server](), [snyk](), [writeup]() ### AI overview This Snyk Fetch the Flag CTF 2023 writeup explains how to solve the Off the SETUID challenge. It examines a minimal QEMU environment with a custom kernel, identifies PHP code injection in an HTTP server, and describes escalating privileges to read the flag from the root user's home directory. ### Source excerpt If you were at Snyk's 2023 Fetch the Flag and are looking for the answer to the Off the SETUID challenge, you've come to the right place. Let's walk through the solution together! ## Pwn2Own 2021 Canon ImageCLASS MF644Cdw writeup DevFeed: [Pwn2Own 2021 Canon ImageCLASS MF644Cdw writeup]() Original publisher: [Read original article]() Author: Nicolas "NK" Devillers & Jean-Romain "JRomainG" Garnier & Raphaël "\_trou\_" Rigo Published: 2022-06-11T15:00:00Z Content type: article Language: en Sources: [Diary of a reverse-engineer]() Topics: [Printer](), [Embedded Software Dev](), [Load Balancing](), [macOS]() Tags: [canon](), [cve-2022-24674](), [exploitation](), [firmware](), [imageclass](), [macos](), [memory-corruption](), [mf644cdw](), [printers](), [pwn2own](), [pwn2own-austin](), [research](), [writeup](), [zdi-22-516]() ### AI overview A technical writeup of research targeting the Canon ImageCLASS MF644Cdw printer for Pwn2Own Austin 2021. It describes analyzing the printer's firmware, obtaining firmware downloads, and investigating Canon's firmware URL structure and version availability. ### Source excerpt Introduction Pwn2Own Austin 2021 was announced in August 2021 and introduced new categories, including printers. Based on our previous experience with printers, we decided to go after one of the three models. Among those, the Canon ImageCLASS MF644Cdw seemed like the most interesting target: previous research was limited (mostly targeting ... ## Eth2 v1.0 specifications released with mainnet deposit contract details DevFeed: [Eth2 v1.0 specifications released with mainnet deposit contract details]() Original publisher: [Read original article]() Author: Danny Ryan Published: 2020-11-04T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Deployment](), [Command-line interface](), [Ethereum Name Service (ENS)](), [Unix]() Tags: [cli](), [consensus](), [deployment](), [domain](), [generate](), [hash](), [launch](), [research-development](), [unix](), [update](), [writeup]() ### AI overview The Ethereum Foundation announces the release of the eth2 v1.0 specifications and provides the mainnet deposit contract address. The update describes the planned genesis timing, validator deposit threshold, ENS resolution for the deposit contract, the mainnet Launch Pad, and the deposit CLI v1.0.0 commit hash. ### Source excerpt Contract deployment Genesis deposits Bootstrap consensus tl;dr v1.0 specs released 🚀... ## Exploiting a custom tetris game in CSAW Quals 2020 DevFeed: [Exploiting a custom tetris game in CSAW Quals 2020]() Original publisher: [Read original article]() Published: 2020-09-13T00:00:00Z Content type: tutorial Language: en Sources: [mahaloz.re]() Topics: [Code](), [arcade](), [Ghidra](), [Reconnaissance](), [Script]() Tags: [ctf](), [game](), [ghidra](), [pwn](), [reversing](), [solve](), [writeup]() ### AI overview This writeup explains how a custom Tetris game in CSAW Quals 2020 was analyzed and exploited. The challenge involved discovering cheat-piece placements, obtaining the binary, reverse-engineering its checks, and using an out-of-bounds write to obtain a partial write primitive and ultimately the flag. ### Source excerpt Pwning a custom Tetris game through an out-of-bounds write to memory through block manipulation and changes to the `.text` segment. ## The First F00D Exploit DevFeed: [The First F00D Exploit]() Original publisher: [Read original article]() Author: yifanlu Published: 2019-01-11T08:00:00Z Content type: article Language: en Sources: [Yifan Lu]() Topics: [Exploit](), [Hacking](), [vulnerability](), [Security](), [Encryption](), [Hardware](), [cpu]() Tags: [article](), [bigmac](), [boot](), [encryption](), [exploit](), [f00d](), [hacking](), [hardware](), [heap-overflow](), [henkaku](), [processor](), [security](), [vita](), [vulnerability](), [writeup]() ### AI overview This technical article documents work on the first F00D exploit for the PlayStation Vita, including a memory-corruption vulnerability in a service and the role of F00D's private memory and cryptographic hardware accelerator. ### Source excerpt This article was originally written 2019-01-11 and published on 2019-07-29 for the third anniversary of HENkaku, the first Vita jailbreak. It documents the work we did in early 2017, just days after the seminal "octopus" exploit. Although the work is dated and does not open any new doors, the technical contents might be interesting for a particular audience. The original intention was to post this after someone else independently discovers the same vulnerability. There were many overt hints on the HENkaku wiki that the 0x50002 service was buggy but I underestimated the interest (or skills) that people would have in hacking an exotic processor that ultimately does nothing for people who just want to run homebrews or play pirated games. ## Project PITA: Build a Mini Mass Deauther Using Bettercap and a Raspberry Pi Zero W DevFeed: [Project PITA: Build a Mini Mass Deauther Using Bettercap and a Raspberry Pi Zero W]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2018-07-28T17:01:56Z Content type: tutorial Language: en Sources: [evilsocket]() Topics: [Raspberry Pi](), [Linux](), [Network](), [configuration](), [ssh](), [Bluetooth](), [clients](), [file]() Tags: [bettercap](), [ble](), [bluetooth](), [btnap](), [cybersecurity](), [deauth](), [handshake-capture](), [kali](), [linux](), [monitor-mode](), [packet-injection](), [pi](), [portable-hacking](), [project](), [raspberry](), [raspberry-pi](), [rpi](), [rpi-zero-w](), [rpi0w](), [wifi](), [wireless-security](), [wpa2](), [writeup](), [zero]() ### AI overview A writeup showing how to build a pocket-sized WiFi deauthenticator with a Raspberry Pi Zero W, Kali Linux, Nexmon drivers, and bettercap. It covers WiFi scanning, deauthentication packets, WPA2 handshake capture, initial SSH and WiFi configuration, and Bluetooth access. ### Source excerpt A few days ago I started playing with some idea I had from a few weeks already, using a Raspberry Pi Zero W to make a mini WiFi deauthenticator: something in my pocket that periodically jumps on all the channels in the WiFi spectrum, collects information about the nearby access points and their connected clients and then sends a deauthentication packet to each one of them, resulting in some sort of WiFi jammer on the 802.11 level. As an interesting "side effect" of this jammer (the initial intent was purely for the lulz) is that the more it deauths, the higher the changes to also sniff WPA2 handshakes. Thanks to the awesome work of the Kali and Nexmon communities in packaging the nexmon drivers and utilities and to the recent changes we released in bettercap, this was very easy to setup and to script and given the interest the tweet had I thought to share this writeup :) This awesome case has been designed by @elkentaro and can be found on [his Thingverse page](https://www.thingiverse.com/thing:3018480). ## Why moving elements with translate() is better than pos:abs top/left DevFeed: [Why moving elements with translate() is better than pos:abs top/left]() Original publisher: [Read original article]() Author: Paul Irish Published: 2012-12-20T08:00:00Z Content type: article Language: en Sources: [Paul Irish]() Topics: [CSS](), [modern web development](), [developer tooling](), [Chrome](), [HTML5 and CSS3 tricks]() Tags: [chrome](), [css](), [examples](), [html5](), [laptop](), [layout](), [performance](), [pixel](), [update](), [writeup]() ### AI overview This article compares moving elements with CSS 2D transforms such as translate() against absolute positioning with top/left. Using Chrome DevTools evidence, it explains that transforms can move an element on a GPU-composited layer, reducing per-frame paint work and producing smoother animation, while noting that pixel snapping can sometimes make top/left appear visually preferable. ### Source excerpt Update (2016): The more canonical writeup of this technique is at High Performance Animations - HTML5 Rocks. TL;DR: Only transform & opacity; never top/left! In modern days we have two primary options for moving an element across the screen: using CSS 2D transforms and translate() using position:absolute and top/left Chris Coyier was asked why you should use translate. Go read his response which covers well why it's more logical to move elements for design purposes (with transform) independent of your element layout (with position). I wanted to answer this with Chrome and get some good evidence on what's going on. I ended up recording a video on the experience: It's a good watch and dives into Chrome DevTools' Timeline, compositing, paint cost, accelerated layers, and more... but if you want the abbreviated text version, read on: First thing, Chris made some simple demos to try things out: This sorta works, but there is such low complexity in this situation that it's all going to look pretty great. We need something closer to a complex website to properly evaluate the two (thx joshua for the macbook!): Now we're starting to get closer, but immediately I get distracted by something. Distraction: Pixel snapping If you run the demo above you might notice the top edge of the MacBook looks a little bit better in the top/left one. (And here I am writing a post about why translate is better! Preposterous!) So this is due to the absolute positioned macbook sticks to pixel positions, whereas the translate()'d one can interpolate at sub-pixel positions. One of the Chrome GPU engineers, James Robinson, called this the "dubstep effect", as these pixels appear to be getting pounded by bass. Here's a closeup of the effect... watch the top white edge of the macbook in each: On the left, you see stair-stepping down three pixels and back up again. This pixel snapping may result in a less distracting transition in this case, though this wouldn't be so noticeable if you were moving object ## Moving The Web Forward DevFeed: [Moving The Web Forward]() Original publisher: [Read original article]() Author: Paul Irish Published: 2011-12-04T03:33:00Z Content type: article Language: en Sources: [Paul Irish]() Topics: [Web](), [Web platform](), [GitHub](), [frontend development](), [Front end](), [IRC](), [jQuery](), [Boilerplate]() Tags: [community](), [contribute](), [developers](), [development](), [frontend](), [frontend-development](), [github](), [html5](), [open](), [platform](), [project](), [repo](), [resources](), [standards](), [team](), [web](), [web-platform](), [web-standards](), [writeup]() ### AI overview The article introduces Move the Web Forward, an initiative that helps people channel their interest into practical contributions to the web community and web platform. It describes the initiative's collaborative creation through design, frontend development, IRC, etherpad, and GitHub, and highlights examples of participants contributing to web standards, Firefox, BuddyPress, and documentation. ### Source excerpt This Wednesday, me and a ragtag team of like-minded developers launched Move the Web Forward, an initiative to direct people's passions into productive efforts that assist not only the web community but the entire web platform. People often feel the need to "give back", but when it comes to contributing it's a challenge to find the right place. This is something I've seen happen firsthand in the jQuery and HTML5 Boilerplate communities. The MWF effort was inspired by a tweet by WebKit extraordinaire Dimitri Glazkov. If you want to help out with Web standards, you could wear a blue beanie once a year. Or you could start hacking on WebKit/Gecko. -- Dimitri Glazkov (@dglazkov) December 29, 2010 Me and Divya started brainstorming on an etherpad. We rounded up some folks on Google+ and IRC and started collecting a lot of excellent resources. Soon after a design was in the making and we started working in an open repo on github... At this point, I want to call out Mat Marquis aka @wilto, in particular, for really taking early ownership of this project and spearheading the design and frontend development. His efforts really made the site communicate its content effectively. Naturally the site is on github if you'd like to contribute. We have a few issues open that we'll be improving the site with. (Also, let me just say for projects like this, a cron job to pull latest from Github makes for such a relaxing workflow.) Thanks to Divya, Mat, Aaron Forsander, Connor Montgomery, Stephanie Rewis (great writeup!), Nicolas Gallagher, Addy, and all these awesome folk. Truly a socially developed site; everyone collaborating on IRC, etherpad and github (with as many having commit rights as possible). Fun project to work on and I hope to see everyone find the right place for them to get more involved in actively making the web as awesome as you want it to be. 2011.12.02: #movingwebforward in action! Beyond all the people who signed up (with the avatars) on the site to commit to things.. ## Fun with the preprocessor: CONFIG\_IA32\_EMULATION hacks in Linux DevFeed: [Fun with the preprocessor: CONFIG\_IA32\_EMULATION hacks in Linux]() Original publisher: [Read original article]() Author: Nelson Elhage Published: 2010-03-28T20:07:43Z Content type: article Language: en Sources: [Nelson Elhage]() Topics: [Linux](), [Kernel](), [Process](), [Hardware]() Tags: [architecture](), [bug](), [code](), [compatibility](), [cve](), [hacks](), [kernel](), [linux](), [process](), [writeup]() ### AI overview A technical discussion of Linux's CONFIG_IA32_EMULATION support for running 32-bit processes on 64-bit systems, prompted by analysis of the CVE-2010-0307 denial-of-service vulnerability. ### Source excerpt About two months ago, Linux saw CVE-2010-0307, which was a trival denial-of-service attack that could crash essentially any 64-bit Linux machine with 32-bit compatibility enabled. LWN has an excellent writeup of the bug, which turns out to be a subtle error related to the details of the execve system call and with 32-bit compatibility mode. While dealing with this patch for Ksplice, I ended up reading an awful lot of the code in Linux that deals with handling 32-bit processes on 64-bit machines. ## Versioning dotfiles in git DevFeed: [Versioning dotfiles in git]() Original publisher: [Read original article]() Author: Nelson Elhage Published: 2010-02-14T20:03:15Z Content type: tutorial Language: en Sources: [Nelson Elhage]() Topics: [dotfiles](), [Git]() Tags: [git](), [sync](), [versioning](), [workflows](), [writeup]() ### AI overview A writeup of a workflow for versioning and synchronizing dotfiles between machines with Git. It describes per-machine branches, a shared master branch, symlinked checkouts, and synchronization in a separate working copy. ### Source excerpt I've been looking for a good solution for versioning and synchronizing my dotfiles between machines for some time. I experimented with keeping all of ~ in subversion for a while, but it never worked out well for me. I've finally settled on a solution that I like using git, and so this is a writeup of my workflows for working with my dotfiles in git, in the hopes that someone else might find it useful. ## FOSDEM Writeup DevFeed: [FOSDEM Writeup]() Original publisher: [Read original article]() Published: 2009-02-23T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [FOSDEM]() Tags: [fosdem](), [free](), [open-source](), [os](), [react](), [reactos](), [win32](), [winapi](), [writeup]() ### AI overview A project writeup recounts the authors' travel from Milan to Brussels and their experiences attending FOSDEM, including the Beer Event and dinner in the city. ### Source excerpt The following is a writeup by KJK::Hyperion detailing his experiences at FOSDEM. Since all the developers unilaterally agreed that it was a much more entertaining read, it now represents the project's writeup. Besides some minor spelling corrections, name corrections, and conclusion, it was all his, quirky grammar included. Enjoy. FRIDAY Left home at 3.30 AM. My pessimistic estimate is 10 hours total of travel from home (Milan, Italy) to hotel (Brussels, Belgium).