I hereby claim:
- I am Japh on github.
- I am japh (https://keybase.io/japh) on keybase.
- I have a public key whose fingerprint is 8426 E15F CE1D CE53 2CD4 9E18 F9A8 6C01 062E ADEF
To claim this, I am signing this object:
| // Use Gists to store code you would like to remember later on | |
| console.log(window); // log the "window" object to the console |
I hereby claim:
To claim this, I am signing this object:
| Verifying that +japh is my openname (Bitcoin username). https://onename.com/japh |
| # Nginx config for proxying requests on port 80 to 5555, put in /etc/nginx/conf.d/ | |
| server { | |
| listen 80; | |
| listen 443 default_server ssl; | |
| server_name example.com; # You should change this to the IP address or domain for your server | |
| location / { | |
| proxy_set_header X-Real-IP $remote_addr; | |
| proxy_set_header Host $http_host; | |
| proxy_pass http://127.0.0.1:5555; | |
| } |
| #!/bin/bash | |
| socket=$HOME/.ssh/spinnaker-tunnel.ctl | |
| if [ ! \( -e ${socket} \) ]; then | |
| echo "Opening tunnel to Spinnaker..." | |
| ssh -f -N spinnaker-start && echo "Tunnel open." | |
| else | |
| echo "Closing tunnel to Spinnaker..." | |
| ssh -O "exit" spinnaker-stop && echo "Tunnel closed." |
All fully synced blockchain wallets are NEO nodes. There are many. However, NEO works on a different kind of consensus mechanism than currencies like Bitcoin (Proof-of-Work) or NAV (Proof-of-Stake), and uses something called dBFT (delegated Byzantine Fault Tolerance). So there are certain nodes in the network that are like “master” nodes called “Consensus Nodes”, and these need to be voted on by the entire network. Plenty of this information is in the NEO docs.
Currently the Consensus Nodes are run by the NEO Council, which was a deliberate decision while the ecosystem got moving, with plans to decentralise the operation of these nodes in Q1 of 2018. Ironically it was in October’s Monthly Report from the NEO Council that plans were announced to do this even earlier than originally planned.
Almost nothing
| 040d3b68f1151304110099e8abcebb332a1247fd5aa8919b42b804c5d686f422597763e78b8c35dd0bec5d1710135ecd2d5e2a5204ae1a3477b64b4b80e80f1791 |
| <!DOCTYPE HTML> | |
| <html> | |
| <head> | |
| <title>T11</title> | |
| <style> | |
| body { | |
| margin: 0; | |
| padding: 0; | |
| background-color: #000000; |
| schema_version: 1.0.0 | |
| name_for_model: contextMemory | |
| name_for_human: Context7 Memory Retriever | |
| description_for_model: | | |
| Use this tool to retrieve relevant context memories from a message history. | |
| Sends OpenAI-style messages to Context7 MCP and receives related memory strings. | |
| description_for_human: | | |
| Retrieves contextually relevant memories using the Upstash Context7 MCP API. | |
| Useful for adding personalized or memory-based retrieval into conversations. | |
| auth: |