Skip to content

Instantly share code, notes, and snippets.

View skanna's full-sized avatar
♟️

Marco Scannavini skanna

♟️
  • Rome, Italy
View GitHub Profile
@DavidWells
DavidWells / javascript-proxy-as-rest-client.js
Last active May 12, 2024 14:24
Using a javascript proxy as low code REST client
/* Using a JavaScript proxy for a super low code REST client */
// via https://dev.to/dipsaus9/javascript-lets-create-aproxy-19hg
// also see https://towardsdatascience.com/why-to-use-javascript-proxy-5cdc69d943e3
// also see https://github.com/fastify/manifetch
// also see https://github.com/flash-oss/allserver
// and https://gist.github.com/v1vendi/75d5e5dad7a2d1ef3fcb48234e4528cb
const createApi = (url) => {
return new Proxy({}, {
get(target, key) {
@johncantrell97
johncantrell97 / satoshistreasure.md
Last active April 15, 2023 15:09
How I Obtained Satoshi's Treasure Keys 1, 2, and 3 in Minutes

Today (April 16th 2019 at noon) the first major clues to discover key #1 was set to be released in a few cities. A QR code with the words 'orbital' were found at these locations and looked like this: (https://imgur.com/a/6rNmz7T). If you read the QR code with your phone you will be directed to this url: https://satoshistreasure.xyz/k1

At this URL you are prompted to input a passphrase to decrypt the first shard. An obvious first guess was to try the word 'orbital' from the QR code. Not suprisingly this worked! This reveals a congratulations page and presents the first key shard:

ST-0001-a36e904f9431ff6b18079881a20af2b3403b86b4a6bace5f3a6a47e945b95cce937c415bedaad6c86bb86b59f0b1d137442537a8.

Now, we were supposed to wait until April 17th to get clues from the other cities for keys #2 and #3 but that wouldn't stop me from digging around with all the new information we had. All that time "playing" notpron (http://notpron.org/notpron/) years ago was going to help me here.

The first thing I noticed was

@eliOcs
eliOcs / gist:3514963
Created August 29, 2012 16:10
Missing parameter middleware for Restify (Node.js)
server.use((function () {
var
/**
* Checks if a request parameter has been defined.
*/
contains = function (parameter) {
return this.params[parameter] !== undefined;
},
/**
@mdesantis
mdesantis / .Xmodmap
Created November 26, 2011 17:58
Solving swapped keys ( <> key is wapped with \| key ) of the italian Apple Keyboard on Ubuntu (from the thread http://forum.ubuntu-it.org/index.php/topic,383892.msg3872344.html )
! Direttive per mappare correttamente la tastiera Apple italiana su Ubuntu,
! cioè, correggere lo scambio dei tasti maggiore/minore con quello di backslash/pipe
!
! 49: codice del tasto maggiore/minore ( <> ) (situato a destra del tasto L-SHIFT)
! 94: codice del tasto backslash/pipe ( \| ) (collocato a sinistra del tasto `uno/punto esclamativo` ( 1! ) )
!
!
! I comandi scritti sotto, eseguiti da terminale sono:
! xmodmap -e "keycode 49 = less greater guillemotleft guillemotright guillemotleft guillemotright" && \
! xmodmap -e "keycode 94 = backslash bar notsign brokenbar notsign brokenbar"