prologic

Learn Go in ~5mins

This is inspired by A half-hour to learn Rust and Zig in 30 minutes.

Basics

Your first Go program as a classical "Hello World" is pretty simple:

First we create a workspace for our project:

yorickdowne

Medalla non-finality mid October

What is happening with the Medalla eth2 testnet currently, Oct 17th 2020? Here's an ELI5. (Not exactly 5. Maybe 10. You get the idea.)

1. A bunch of validators turned off (maybe zinken, maybe bored, who knows)
2. We entered non-finality. This means we don't have enough validators online to agree to what the state of the network is. We need 2/3rds.
3. Some sync bugs reared their heads, in Prysm and Nimbus. We lost more validators to the bugs, not everyone has updated since
4. Non-finality increases memory and CPU requirements, we likely lost more validators because their nodes couldn't handle it
5. Either people come back in and we regain finality or
6. They don't and offline validators lose eth faster and faster, until we regain finality. Some may be ejected if their balance falls too low.

jaekwon

 (capital) One is the *meta-Cosmos
. the *meta-Cosmos includes our Cosmos, our universe, all past/present/future.
. one is a local construct of the Cosmos.
. there are many truths all enmeshed with each other.
. the whole Truth cannot be seen.
. each one has their unique truth.
. only they (the "one"s in the statement above) can say their truths.
. only the One (or They) can say the Truth.
. every one should be encouraged to speak their truth.
. it's ok to claim that something is True, if you really believe it.

aunyks

pragma solidity ^0.4.19;
contract ERC721 {
   string constant private tokenName = "My ERC721 Token";
   string constant private tokenSymbol = "MET";
   uint256 constant private totalTokens = 1000000;
   mapping(address => uint) private balances;
   mapping(uint256 => address) private tokenOwners;
   mapping(uint256 => bool) private tokenExists;
   mapping(address => mapping (address => uint256)) private allowed;
   mapping(address => mapping(uint256 => uint256)) private ownerTokens;

jdh30

sudo apt-get update
sudo apt-get install opam elpa-tuareg make m4 gcc zip aspcud emacs libssl-dev ncurses-dev pkg-config libffi-dev bubblewrap linux-tools-common linux-tools-aws
opam init
eval $(opam env --switch=default)
opam install ocamlfind core async async_ssl cohttp yojson ppx_deriving ocp-indent merlin cohttp-async ocamlformat utop

DavidWells

Aligning images

This is a guide for aligning images.

See the full Advanced Markdown doc for more tips and tricks

left alignment

jeffThompson

Scarecrow in the hillock
Paddy field --
How unaware!  How useful!

Passing through the world
Indeed this is just
Sogi's rain shelter.

A wild sea-
In the distance over Sado

Chaser324

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j