SMUsamaShah

Browser Based

1. Web Wormhole https://webwormhole.io/ https://github.com/saljam/webwormhole
   NOTE: Probably the only browser tool that streams file directly. Should transfer file of any size (hundreds of GBs etc)
2. Localsend https://web.localsend.org/
3. FilePizza https://file.pizza/
4. PairDrop https://pairdrop.net/ https://github.com/schlagmichdoch/pairdrop
   1. ShareDrop sharedrop.io https://github.com/szimek/sharedrop (SOLD, not recommended, use PairDrop)
   2. SnapDrop snapdrop.net https://github.com/RobinLinus/snapdrop (SOLD, not recommended, use PairDrop)
5. ToffeeShare https://toffeeshare.com/

entropie

#!/usr/bin/env ruby

# this scripts acts as a wrapper for a little daemon that reads a fifo;
#
# If called without allready running it starts a background daemon and
# downloads the argument, then proceeds to watch the fifo for more.
#
# We esnure that the script is only running once and only one dl at a time.

FIFO =               "/home/ha/.ytfifo"

Widdershin

In the olden days, HTML was prepared by the server, and JavaScript was little more than a garnish, considered by some to have a soapy taste.

After a fashion, it was decided that sometimes our HTML is best rendered by JavaScript, running in a user's browser. While some would decry this new-found intimacy, the age of interactivity had begun.

But all was not right in the world. Somewhere along the way, we had slipped. Our pages went uncrawled by Bing, time to first meaningful paint grew faster than npm, and it became clear: something must be done.

And so it was decided that the applications first forged for the browser would also run on the server. We would render our HTML using the same logic on the server and the browser, and reap the advantages of both worlds. In a confusing series of events a name for this approach was agreed upon: Server-side rendering. What could go wrong?

In dark rooms, in hushed tones, we speak of colours.

mmazzarolo

/**
 * GlobalsDebugger
 *
 * Inspect the stack when a global variable is being set on the window object.
 * Given a global variable name, it proxies the variable name in the window
 * object adding some custom code that will be invoked whenever the variable
 * is set. The custom code will log the current stack trace and halt the code
 * execution to allow inspecting the stack and context in your browser DevTools.
 * You can use the "globalsToInspect" query-parameter to set a comma-separated
 * list of names of the variables you want to inspect.

DavidWells

/* 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) {

unrealwill

import tensorflow as tf #We need tensorflow 2.x
import numpy as np

#The hashlength in bits
hashLength = 256

def buildModel():
    #we can set the seed to simulate the fact that this network is known and doesn't change between runs
    #tf.random.set_seed(42)
    model = tf.keras.Sequential()

veggiedefender

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:

Treeki

#include <stdint.h>
#include <stdio.h>
#include <stdlib.h>

// munged from https://github.com/simontime/Resead

namespace sead
{
class Random
{

s875515

const replace = require('@rollup/plugin-replace');

const envKeys = () => {
    const envRaw = require('dotenv').config().parsed || {};

    return Object.keys(envRaw).reduce(
        (envValues, envValue) => ({ ...envValues, [`process.env.${envValue}`]: JSON.stringify(envRaw[envValue]) }),
        {}
    );
};