DavidBuchanan314

Using the fs-net libtransistor fork

This guide assumes you are already familliar with setting up RetroArch with libtransistor.

Clone the fs-net branch from https://github.com/davidbuchanan314/libtransistor:

git clone https://github.com/davidbuchanan314/libtransistor --recursive -b fs-net

Build libtransistor as usual.

dajo

/**
 * Convert a list on Quizlet into CSV-formatted text.
 * Usage:
 *   i) Copy and paste into your browser's console.
 *   ii) Run it!
 */
(() => {
  const terms = document.getElementsByClassName('term');
  const csv = [];

snorrelo

# Custom logging handler for python for sending log messages via Pushover.
# https://pushover.net/
# 
# Extends HTTPHandler https://docs.python.org/3.6/library/logging.handlers.html#httphandler

import logging.handlers


class PushoverHTTPHandler(logging.handlers.HTTPHandler):
    _APP_TOKEN = None

klmitchell2

#!/jb/bin/bash

CYCRIPT_PORT=1337

function help {
    echo "Syntax: $0 [-p PID | -P appname] [-l /path/to/yourdylib | -L feature]"
    echo
    echo For example:
    echo "   $0 -P Reddit.app -l /path/to/evil.dylib   # Injects evil.dylib into the Reddit app"
    echo "     or"

koad

//  Discord all events!
//  A quick and dirty fleshing out of the discord.js event listeners  (not tested at all!)
//     listed here -> https://discord.js.org/#/docs/main/stable/class/Client
//  Learn from this, do not just copy it mofo!
//
//  Saved to -> https://gist.github.com/koad/316b265a91d933fd1b62dddfcc3ff584
//  Last Updated -> Halloween 2022


            /*      

d3vilbug

#!/usr/bin/env python3

from __future__ import print_function
import frida
import sys
import json
import time

def on_message(message, payload):
	if(message['type'] == 'send'):

esamson

wget https://download.calibre-ebook.com/linux-installer.sh

sh linux-installer.sh install_dir=~/.local/opt isolated=True

xtream1101

Backup/archive a repo

1. Clone the repo

git clone --mirror https://github.com/vuejs/vue

2. cd into the cloned repo
3. Create a bundle file in the parent directory

git bundle create ../vuejs_vue.bundle --all

0penBrain

curl -I -k "https://api.github.com/repos/:owner/:repo/commits?per_page=1" | sed -n '/^[Ll]ink:/ s/.*"next".*page=\([0-9]*\).*"last".*/\1/p'

### And that's all !
# I saw many fighting with finding first commit SHA or similar fancy thing.
# Here we just rely on the GH API, asking commits at 1 per page and parsing the last page number in the header of the reply (whose body only holds the last commit !)
# So this is robust and bandwidth efficient. :)

# If one want the commit count of a specific SHA, just use :
curl -I -k "https://api.github.com/repos/:owner/:repo/commits?per_page=1&sha=:sha" | sed -n '/^[Ll]ink:/ s/.*"next".*page=\([0-9]*\).*"last".*/\1/p'

Matchstic

Paid Tweak Guidelines (Work-in-Progress)

Asking for payment is equivalent to stating "I have made something truly worth paying for". For example, it is groundbreaking or an incredibly useful addition to iOS. In most cases, consider not asking for payment and look towards open-sourcing your work. The 'soul' of making tweaks is to build something for the fun of it, not to run a business.

If you decide to release a paid tweak, it is not a matter of adding a price to your work and putting it on a default repository. You need to ensure the price is justified, and that the tweak matches customer expectations. After that, you also need to provide support and updates when necessary. To be clear: accepting payments means you become liable for handling a lot more than just writing code.

The following guidelines should be used to check that you are within customer expectations. Please note that individual repositories may also add their own expectations if you decide to release through them (e.g. [Packix](https:/