This fork by rebane2001 is an improved version of the script!
| /**! | |
| * Fast CRC32 in JavaScript | |
| * 101arrowz (https://github.com/101arrowz) | |
| * License: MIT | |
| */ | |
| // If you use this code, please link this gist or attribute it somehow. | |
| // This code uses the Slice-by-16 algorithm to achieve performance | |
| // roughly 2x greater than all other JS CRC32 implementations (e.g. |
This is an effort to document what is known about Google's (Blogger's/Blogspot's) image URL parameters. Some of these options were taken from existing first or third party documentation (see the links at the end of this document), but the majority is based off my own investigations.
- On Blogger's image URL's:
2.bp.blogspot.com/-OF7u67HQE1M/VHc8S8qJTDI/AAAAAAAACxI/UD-11c63diQ/s1600/005.png - On just about any googleusercontent image URL:
https://lh3.googleusercontent.com/Jvmz11cLrvNIHG_LWjVO9B-UV2IN4Cfk1pycbhWZl6IriMgCAGCOFuBRtoHaiZ6xeVGqCugZcCql=w176-h176-n-o
Replace the bolded parts with the parameters.
Below are table of various projects that can completely exhaust n-bits of keyspace. In other words, counting completely and fully from 0 to 2ⁿ-1.
This Gist implies no discussion about how this is relevant to quantum computing using Grover's algorithm, meet-in-the-middle or birthday attacks, or anything of the like. It's strictly a Gist about raw speed, measuring the result in bits.
If you know of other noteworthy and verifiable brute force searching projects,
This script removes the input length limit which can trip up Plover users.
Simply install the script into TamperMonkey (Chrome) or GreaseMonkey (Firefox) and get racing.
The script was created by community member nimble
| /* | |
| * clang -O2 -s -lGL -ldl -shared fake_glvendor.c -fPIC -o fake_glvendor.so | |
| */ | |
| #define _GNU_SOURCE | |
| #include <stdlib.h> | |
| #include <stdio.h> | |
| #include <dlfcn.h> |
| class Node { | |
| constructor(key, value, next = null, prev = null) { | |
| this.key = key; | |
| this.value = value; | |
| this.next = next; | |
| this.prev = prev; | |
| } | |
| } | |
| class LRU { |
This is a compiled list of falsehoods programmers tend to believe about working with time.
Don't re-invent a date time library yourself. If you think you understand everything about time, you're probably doing it wrong.
- There are always 24 hours in a day.
- February is always 28 days long.
- Any 24-hour period will always begin and end in the same day (or week, or month).
| #!/usr/bin/env python | |
| # the contents of this file are in the public domain | |
| import os | |
| import random | |
| import sys | |
| def main(args): | |
| filename = args[0] |
| // Just before switching jobs: | |
| // Add one of these. | |
| // Preferably into the same commit where you do a large merge. | |
| // | |
| // This started as a tweet with a joke of "C++ pro-tip: #define private public", | |
| // and then it quickly escalated into more and more evil suggestions. | |
| // I've tried to capture interesting suggestions here. | |
| // | |
| // Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_, | |
| // @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant, |
