willurd

Each of these commands will run an ad hoc http static server in your current (or specified) directory, available at http://localhost:8000. Use this power wisely.

Discussion on reddit.

Python 2.x

$ python -m SimpleHTTPServer 8000

mobilemind

# delete local tag '12345'
git tag -d 12345
# delete remote tag '12345' (eg, GitHub version too)
git push origin :refs/tags/12345
# alternative approach
git push --delete origin tagName
git tag -d tagName

jonathanstark

#
# Verify captcha
$post_data = http_build_query(
    array(
        'secret' => CAPTCHA_SECRET,
        'response' => $_POST['g-recaptcha-response'],
        'remoteip' => $_SERVER['REMOTE_ADDR']
    )
);
$opts = array('http' =>

xerpi

Step 1: Compiling or Downloading the toolchain

Step 1.a: If you choose to download a pre-compiled toolchain (only for Linux x86-64)

• Go to https://toolchains.bootlin.com
• Select arch: armv6-eabihf
• Select libc: glibc
• Download bleeding-edge
• Uncompress it (for example to /opt)
• Add the bin/directory of the toolchain to $PATH
• In my case: export PATH=$PATH:/opt/armv6-eabihf--glibc--bleeding-edge-2020.08-1

gboudreau

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.

williewillus

This primer is licensed under CC0, do whatever you want.

BUT do note that this can be updated, so leave a link here so readers can see the updated information themselves.

1.13 and 1.14 are lumped together in this doc, you're on your own if you just want to go to 1.13 and not 1.14, for some reason.

1.15 stuff: https://gist.github.com/williewillus/30d7e3f775fe93c503bddf054ef3f93e

Things in Advance

• ResourceLocation now throw on non-snake-case names instead of silently lowercasing for you, so you probably should go and change all those string constants now. More precisely, domains must only contain alphanumeric lowercase, underscore (_), dash (-), or dot (.). Paths have the same restrictions, but can also contain forward slashes (/).

7coil

const fs = require('fs');
const path = require('path');
const crypto = require('crypto');

const compare = (a, b) => parseInt(a.replace(/\D/g, ''), 10) - parseInt(b.replace(/\D/g, ''), 10);

const data = fs.readdirSync('./frames')
  .sort(compare)
  .map((file, index) => {
    const hash = crypto.createHash('md5').update(fs.readFileSync(`./frames/${file}`)).digest('hex');

quat1024

TL;DR

If you want to load some resources or data in Fabric 1.14 or 1.15, do this:

ResourceManagerHelper.get(ResourceType.ASSETS).registerReloadListener(new SimpleResourceReloadListener<MyResource>() {
  @Override
  public Identifier getFabricId() {
    return new Identifier("some_identifier", "that_describes_this_task");
  }

quat1024

What

When compiling mods in recent versions of IntelliJ, weird things start happening:

• With ForgeGradle 2 (1.12-), none of the assets show up in-game (language keys, models, textures etc)
• Broken hotswapping.
• Potentially other Bad, Terrible Things that are yet to be discovered.

How

quat1024

Update guides and new features

• Overview of Resource Reloading in 1.14.4/Fabric
• Updating to Fabric 1.17 notes
• Updating to Fabric 1.18 notes
• Fabric 1.16 Datagens (this was before Fabric API added stuff)
• how 2 angry lex.md (1.12.2 Forge coremodding)

Tooling problems

• Fix stuff being broke in IntelliJ (old ForgeGradles)