KoryNunn

Had 15 github followers in 2019? You can get about $4kAUD of crypto for minimal effort.

Explain this scam

That's legitimately a good default position to hold, however, in this case, the free money is a function of time, and not only charity.

In February 2020, in order to promote Handshake (HNS) to developers, an airdrop was offered to any Github user with more than 15 followers. The Airdrop would give you 4246HNS, at the time worth around at $0.08USD per coin, for a total of $339.68USD, pretty generous!

Today, 4246HNS is worth around $4000 dollarydoos, and there are plenty of github users who haven't claimed theirs.

mattn

blacklist/whitelist master/slave に関する情報集め

blacklist/whitelist、master/slave という単語は相応しくないという意見に OSS がどの様に対応すべきかを自身で考える為の情報集めです。見つけ次第、逐次更新していきます。

僕(mattn) 自身は black lives matter に同意をしています。blacklist/whitelist、master/slave という単語を廃止する事が、歴史的背景を持たない文化圏では特定の意味を持たなかった為、個人的には若干思う所はありますが、廃止自身に反対するつもりはありません。

昔から、主副を表す物には master/slave という単語が使われてきました。ハードディスクの IDE、仮想端末(pty)、色々あります。またネットワークの IP フィルタリングに関しては blacklist/whitelist と表記した物が今でも沢山あります。

我々日本人が意識せずに使っていた blacklist/whitelist、master/slave という単語が、人々にどの様に影響しうるのか、今後 OSS としてどの様に関わっていけば良いかを理解する上で、自分なりの情報集めをしたいと思っています。

sarkis

data "aws_route53_zone" "example_com" {
  name = "example.com."
  private_zone = false
}

resource "aws_acm_certificate" "example_com" {
  domain_name               = "example.com"
  subject_alternative_names = ["www.example.com"]
  validation_method         = "DNS"

micahhausler

# Go to https://developer.github.com/v4/explorer/ and enter the graphql query with the query veriable:
# {"queryString": "your-githubuser-name"}

cat results.json | 
  jq '.data.user.repositories.edges[] | { Count: .node.collaborators.totalCount, Repo: .node.name} | select(.Count > 2)'

playground.rs

extern crate libc;

use std::io::{ Read, BufRead, Write, stdout, stdin };
use std::fs::File;
use std::env;

struct Interpreter {
    stack: Vec<i8>,
    stack_ptr: usize
}

badboy

FROM ubuntu:16.04
MAINTAINER Jan-Erik Rediger

RUN apt-get update && \
    apt-get install -y --no-install-recommends \
        curl ca-certificates vim-tiny nano gcc libc6-dev python && \
    rm -rf /var/lib/apt/lists/* && \
    mkdir -p /root/data/rust && \
    mkdir -p /root/data/emsdk

jbolila

FROM postgres:latest
MAINTAINER Joao Bolila

ENV LC_ALL=C.UTF-8

RUN apt-get update
RUN apt-get -y install vim silversearcher-ag jq

RUN apt-get -y install build-essential git libsqlite3-dev libpq-dev
RUN cd /tmp ; git clone git://github.com/rkitover/vimpager ; cd vimpager ; make install-deb

playground.rs

fn main() {
    use std::str;
    use std::path::Path;
    
    println!("{:?}", "/tmp/bar/foo.txt".as_bytes());
    //let buf = "/tmp/bar/foo.txt".as_bytes();
    let buf = "C:/temp/foo/bar/foo.txt".as_bytes();
    let buf_string = str::from_utf8(buf).unwrap();
    
    //let path = Path::new("/tmp/foo/bar.txt");

playground.rs

fn main() {
    let floats = vec![1.0, 2.0, 3.0];
    let s: &[f64] = &floats[..];
    
    let string = s.into_iter().map(ToString::to_string).collect::<Vec<_>>().join(",");
    
    println!("{}", string);
}

ericclemmons

Using <details> in GitHub

Suppose you're opening an issue and there's a lot noisey logs that may be useful.

Rather than wrecking readability, wrap it in a <details> tag!

<details>
 Summary Goes Here