Jomar Milan MacaylaMarvelous81

Tar Usage / Cheat Sheet

Compress a file or directory

e.g: tar -czvf name-of-archive.tar.gz /path/to/directory-or-file

-c: Create an archive.
-z: Compress the archive with gzip.
-v: makes tar talk a lot. Verbose output shows you all the files being archived and much.
-f: Allows you to specify the filename of the archive.

I just got this working so I figured I'd share what I found, since there's hardly any information about this anywhere online except an RFC, the GPG mailing list and one tutorial from the GnuPG blog.

You can use automatic key discovery with WKD (Web key directory) to make it easy for users to import your key, in GPG since version 2.1.12. Since this feature is fairly new, it isn't yet available in the current LTS release of Ubuntu (16.04; xenial), however it is available in Debian stable (stretch).

I couldn't add a DNS CERT or DANE / OPENPGPKEY record through my email service (which also hosts my nameservers). I tried making the PKA record - a foo._pka.example.com TXT record but GPG doesn't seem to recognize it and fails; I'm still investigating why.

So the last option for self-hosted auto-discovery was WKD.

First thing I had to do was add an email address to my key. My primary UID is just my name so the key represents my identity rather

HTML Tags You Can Use on GitHub

Wherever HTML is rendered on GitHub (gists, README files in repos, comments on issues and pull requests, ...) you can use any of the HTML elements that GitHub Flavored Markdown (GFM) provides syntactic sugar for. You can either use the syntactic sugar that GFM (or other GitHub-supported markup language you're using) provides or, since Markdown can contain raw HTML, you can enter the HTML tags manually.

But GitHub also allows you to use a few HTML elements beyond what Markdown provides by entering the tags manually, and some of them are styled with CSS. Most raw HTML tags get stripped before rendering the HTML. Those tags that can be generated by GFM syntactic sugar, plus a few more, are whitelisted. These aren't documented anywhere that I can find. Here's what I've discovered so far:

`<details>` and `<summary>`

A `<detai

Understanding Nix Inputs

Every Nix derivation produces a Nix store output that has 3 things:

Executables
Libraries
Data

Executables are always exported using the PATH environment variable. This is pretty much automatic.

For direct image URL, the image quality is much lower than the original upload (the resolution and size of the original upload can be found in the right sidebar). This is not the case few years ago when the original image was accessible through right click, but on 2017, Wix acquired DeviantArt, and has been migrating the images to their own image hosting system from the original DeviantArt system. They linked most of the direct images to a stripped-down version of the original images; hence the bad image quality. Below are the three different formats of direct image URLs I found:

URL with /v1/fill inside: this means that the image went through Wix's encoding system and is modified to a specific size and quality. In this case, you remove ?token= and its values, add /intermediary in front of /f/ in the URL, and change the image settings right after /v1/fill/ to w_5100,h_5100,bl,q_100. The definitions of the values can be found in [Wix's Image Service](https://support.wi

Adding Dependencies

Introduction

Adding Dependencies allows you to access hooks, tools and apis provided by other mods. Depending on other's code allows you to spend lesser time on writing your code, and more time on refining it. A commonly used dependency in fabric is Fabric API.

Adding the repository

Open your build.gradle file and add the required maven repositories

repositories {
    maven {
 name = "Example"

	using System;
	using System.Collections.Generic;
	using System.Linq;
	using System.Text;
	using System.Threading.Tasks;
	using System.Threading;
	using System.Collections;

	namespace workerthread
	{

	var App = React.createClass({
	render: function() {
	// notice that we have the "Button" and "Heart" components
	return <Button>I <Heart /> React</Button>
	}
	});

	var Button = React.createClass({
	render: function() {
	// notice that this.props.children gave us the value of both the "Button" and the "Heart" component

	// To subscribe to an event, pass this JSON text to the client through the WebSocket:

	{
	"body": {
	"eventName": "NameOfEvent" // Replace with an event name listed below
	},
	"header": {
	"requestId": "xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxxxxxxx", // UUID
	"messagePurpose": "subscribe",
	"version": 1, // Protocol version (currently 1 as-of 1.0.2)

	Right now I can do this in Markdeep source:

	------------------
	Just a test paragraph, move along...

	<div class="note">
	Just a note. Don't mind me.
	</div>

	<div class="warn">