Nick Beattie nickbytes

CloudFlare Workers as Status API

In most case, the CloudFlare SLA is greater than our server. So, we can use it as a simple uptime checker.

Usage

Deploy index.js to your CloudFlare Workers, and bind KV which you save the status.
Add updater.rb to your server, and setup cron job to run it
Get node status on any static page with https://your-worker.workers.dev/?node[]=name to fetch node status

gif-from-tweet

There are so many great GIFs out there and I want to have copies of them. Twitter makes that harder than it should be by converting them to MP4 and not providing access to the source material. To make it easier, I made a bash pipeline that takes a tweet URL and a filename, extracts the MP4 from that tweet and uses ffmpeg to convert back to GIF.

Dependencies

ffmpeg
- macOS: brew install ffmpeg
- Ubuntu/Debian: apt install ffmpeg

How to migrate Django from SQLite to PostgreSQL

Dump existing data:

python3 manage.py dumpdata > datadump.json

Change settings.py to Postgres backend.

Make sure you can connect on PostgreSQL. Then:

How not to scale css

Several years ago I got curious about how css worked at scale. When I first started out, there weren’t nearly as many learning resources as there are now. CSS zen garden was amazing, at the time it showed how much you could change a design without altering the html.

In the beginning, that’s what people sold me as a feature. By writing css, you could make a change one place and have it propagate everywhere. In principle this sounds pretty good. I’m lazy so I like doing things one time. But eleven years later, my experience on both large and small teams is that this is the most terrifying thing about css.

https://twitter.com/thomasfuchs/status/493790680397803521

In the past few years a lot of very smart people have been thinking more about CSS and this has lead to some fascinating discussions around how to build ‘scalable’ ui and how that relates to CSS. When I first started to think about scalability I naturally started to read every blog post and watch every tech talk I could get

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't

	from selenium import webdriver

	def deactive_twitter(username, password):
	driver = webdriver.Chrome()
	driver.implicitly_wait(30)
	driver.get('https://twitter.com/login')

	username_field = driver.find_element_by_class_name('js-username-field')
	password_field = driver.find_element_by_class_name('js-password-field')

	const lookup = (namespace) => {
	// if you really want rails-style indirection, you'd
	// need an app container that could look up modules
	// by strings.
	}

	const Resources = ({ namespace }) => {
	const Layout = lookup(namespace, 'layout')
	return (
	<Route path={`/${namespace}`} render={() => (

	Alphabetical listing, generated with the following hoon:

	=p (turn (gulf 0x1 0xffff) \|=(a/@ `@p`(cat 4 ~lisnus a)))
	*%/web/planets-lisnus/txt (turn p \|=(a/@p (scot %p a)))

	---

	Notable planets:

	~bishes-bottem

	from rest_framework import serializers
	from evotee.models import Candidate


	class CandidateSerializer(serializers.ModelSerializer):
	selection = serializers.CharField(
	source='selection.code',
	read_only=True
	)
	photo = serializers.ImageField(

	<!DOCTYPE html>
	<html>
	<head>
	<meta content='text/html; charset=UTF-8' http-equiv='Content-Type' />
	<meta name="twitter:card" content="player" />
	<meta name="twitter:site" content="@wakeyio" />
	<meta name="twitter:title" content="Hemopure ~ Wakey Wakey #26" />
	<meta name="twitter:description" content="Hemopure is an artificial blood (HBOC) that’s saving lives in South Africa. It’s shelf stable and 100% compatible with all blood types." />
	<meta name="twitter:image" content="https://wakey.io/public/img/thumbs/26.png" />
	<meta name="twitter:player" content="https://wakey.io/embed/26" />