Daniel Norman 2color

Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.

My 3 developers team has just developed React.js application with 7668 lines of CSS (and just 2 !important). During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.

Here are main principles we use to write CSS for modern (IE11+) browsers:

SUIT CSS naming conventions + SUIT CSS design principles;
PostCSS + CSSNext. Future CSS syntax like variables, nesting, and autoprefixer are good enough;
Flexbox is awesome. No need for grid framework;
Normalize.css, base styles and variables are solid foundation for all components;

How to get on Rinkeby Testnet in less than 10 minutes

Following instructions from the excellent https://www.rinkeby.io/

Synchronizing a Full Node

A full node lets you access all state. There is a light node (state-on-demand) and wallet-only (no state) instructions as well,

Exporting your 2FA tokens from Authy to transfer them into another 2FA application

IMPORTANT - Update regarding deprecation of Authy desktop apps

Past August 2024, Authy stopped supported the desktop version of their apps:
See Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August for details.

And indeed, after a while, Authy changed something in their backend which now prevents the old desktop app from logging in. If you are already logged in, then you are in luck, and you can follow the instructions below to export your tokens.

If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.

Addressing feedback from this Gist.

Pagination. Looks like limited to paginate by id. I wanted to paginate by a date field and felt impossible

In the most recent Preview version, (cursor-)pagination can be done by any unique field or combination of fields. For example:

model Post {
  id        Int     @id @default(autoincrement())
  title     String

	#!/bin/bash
	# Cloud-config for CoreOS IPXE deployment on Vultr
	##################################################
	# This cloud-config bootstraps CoreOS on /dev/vda and provisions:
	# - private ip-address on eth1
	# - etcd on private network
	# - fleet on private network
	# - basic firewall (docker compatible)
	# - SSHd security hardening
	##################################################

	to check if the server works - https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice

	stun:
	stun.l.google.com:19302,
	stun1.l.google.com:19302,
	stun2.l.google.com:19302,
	stun3.l.google.com:19302,
	stun4.l.google.com:19302,
	stun.ekiga.net,
	stun.ideasip.com,

	1. Create an etcd token; store it in Vault or some other secure location
	2. Create file /etc/systemd/system/docker.service.d/custom.conf with contents:

	[Service]
	Environment="DOCKER_OPTS=-H=0.0.0.0:2376 -H unix:///var/run/docker.sock --cluster-advertise eth1:2376 --cluster-store etcd://127.0.0.1:2379"

	This needs to be done in cloud-init since CoreOS is super bare-bones and "doesn't" contain support for config mgmt out of the box.

	.DS_Store
	._.DS_Store
	**/.DS_Store
	**/._.DS_Store
	.vscode
	.idea
	Thumbs.db

	# used to need to run git config --global core.excludesfile ~/.gitignore_global to set this but apparently no longer needed https://x.com/bate5a55/status/1840594630972191118

	apiVersion: v1
	kind: PersistentVolumeClaim
	metadata:
	namespace: default
	name: pv-default-100g-disk01
	annotations:
	volume.beta.kubernetes.io/storage-class: default
	spec:
	accessModes:
	- ReadWriteOnce


	const http = require('http')
	const rpc = require('./rpc')

	/**
	* Pets service.
	*/

	class Pets {
	constructor(db = []) {