Jia Sui jsfaint

WARNING: If you're reading this in 2021 or later, you're likely better served by reading:

(This gist was created in 2013 and targeted the legacy GOPATH mode.)

$ ssh -A vm
$ git config --global url."[email protected]:".insteadOf "https://github.com/"

On 7/29/2017, all hacked Vitas on 3.60 spoofing the latest firmware (3.65) were blocked from console activation. This is particularly odd because the PSN passphrase did not change in 3.65. Additionally with the release of ensō added to the confusion of what happened. Here is the result of a preliminary investigation of the situation.

Upon game activation, the Vita displays an dialog that shows the error number E-80558325. This error number is used in SceNpKdc, which is found in vs0:external/np_kdc.suprx. The error code itself is created when the activation response is received:

v5 = v45 | 0x80558300;

Here, v5 is the return code and v45 is the string error code from the server converted to a number. The request made to Sony's server looks like the following

INTRO

Concurrency is a domain I have wanted to explore for a long time because the locks and the race conditions have always intimidated me. I recall somebody suggesting concurrency patterns in golang because they said "you share the data and not the variables".

Amused by that, I searched for "concurrency in golang" and bumped into this awesome slide by Rob Pike: https://talks.golang.org/2012/waza.slide#1 which does a great job of explaining channels, concurrency patterns and a mini-architecture of load-balancer (also explains the above one-liner).

Let's dig in:

Goroutines

Take %UserProfile%\Desktop\desktop.ini for example.

Create a desktop.ini file with content below and saved in UTF-16 LE with BOM. Hopefully notepad.exe has such choice to use the right encoding.

[.ShellClassInfo]
LocalizedResourceName=@%SystemRoot%\system32\shell32.dll,-21769
IconResource=%SystemRoot%\system32\imageres.dll,-183

If someone asked me the question "what layout should I use for my Go code repository?", I'd start by asking back "what are you building: an executable, or a library?"

Single executable

Stage 1: single source file

Create a directory named however you want your final executable to be called (e.g. "mycommand"), change into that directory, and create the following files:


	0 = Success
	1 = Operation not permitted
	2 = No such file or directory
	3 = No such process
	4 = Interrupted system call
	5 = Input/output error
	6 = No such device or address
	7 = Argument list too long
	8 = Exec format error

	# coding=utf-8

	import urwid
	import requests
	import re
	from hashlib import md5
	import time
	from bs4 import BeautifulSoup, NavigableString
	import lxml.html

	//Build with: go build ./jsonpp.go

	package main

	import "encoding/json"
	import "fmt"
	import "io/ioutil"
	import "os"

	package main

	import (
	"context"
	"log"
	"net/http"
	"os"
	"os/signal"
	"time"
	)

	package main

	import "fmt"

	// WithPrefix

	type prefixOption struct{}

	func WithPrefix() interface {
	GetOption