See how a minor change to your commit message style can make you a better programmer.
Format: <type>(<scope>): <subject>
<scope> is optional
| #element:before { | |
| content: ""; | |
| position: absolute; | |
| width: 0; | |
| height: 0; | |
| border-left: 16px solid transparent; | |
| border-right: 16px solid transparent; | |
| border-bottom: 16px solid #fff; | |
| top: -15px; | |
| left: 27px; |
| #include <stdio.h> | |
| #include <stddef.h> | |
| #include <stdlib.h> | |
| #pragma warning(disable:4996) | |
| /************************************************************************/ | |
| /* Zip file struct */ | |
| /* */ |
So a FOSS project might have signed releases with a GPG sig. How do you verify it on a Linux machine?
Example sigp/lighthouse, but same idea for any project.
Install gpg: sudo apt install gpg
Grab their PGP key ID from their download page and
gpg --keyserver pgp.mit.edu --recv THEIRKEYID and wait
As of August 2022, a 1TB SSD is getting tight to run an Ethereum node in. The recommendation now is for 2TB of space. I wanted to see what it takes to still fit into 1TB.
EIP-4844 will increase space need by another 200 GiB or so, which may make 1TB setups plain not feasible. This is a 2023 discussion however.
| watch "echo stats | nc 127.0.0.1 11211" | |
| accepting_conns The Memcached server is currently accepting new connections. | |
| auth_cmds Number of authentication commands processed by the server - if you use authentication within your installation. The default is IP (routing) level security which speeds up the actual Memcached usage by removing the authentication requirement. | |
| auth_errors Number of failed authentication tries of clients. | |
| bytes Number of bytes currently used for caching items, this server currently uses ~6 MB of it's maximum allowed (limit_maxbytes) 1 GB cache size. | |
| bytes_read Total number of bytes received from the network by this server. | |
| bytes_written Total number of bytes send to the network by this server. |
@see http://l-w-i.net/t/memcached/command_001.txt
$ memcached-tool localhost dump
First of all, please note that token expiration and revoking are two different things.
A JWT token that never expires is dangerous if the token is stolen then someone can always access the user's data.
Quoted from JWT RFC:
| addEventListener('fetch', event => { | |
| event.respondWith(fetchAndCheckOrigin(event.request)) | |
| }) | |
| async function fetchAndCheckOrigin(req) { | |
| try { | |
| startTime = new Date(); | |
| const body = await req.body; | |
| const ip = req.headers.get('cf-connecting-ip'); | |
| const es = req.headers.get('cf-ipcountry'); |
| package main | |
| import ( | |
| "flag" | |
| "io" | |
| "log" | |
| "net" | |
| "net/http" | |
| "strings" | |
| ) |