Doug A DougAnderson444

Sending email with serverless functions

You can deploy this function on any of the serverless platforms - AWS Lambda, Google Cloud Functions, Azure Functions, Netlify, Cloudflare Workers, etc.

Create a new function and paste in the following code.
You will need to add nodemailer to your package.json (npm i nodemailer), and follow your platform's instructions on bundling dependencies.
Obtain Gmail API credentials for your account. You will need clientID, clientSecret, and refreshToken. Follow this YouTube tutorial
Expose these credentials as the follwing environment variables:

GMAIL_EMAIL_ADDRESS

Note: To keep this even smaller, we're using a small helper module called the hyperswarm replicator, which wraps a few Hyperswarm setup details.

BLS Signature for Busy People

bls12-381 is pairing-friendly Barreto-Lynn-Scott elliptic curve construction allowing to:

Construct zk-SNARKs at the ~120-bit security, as per Barbulescu-Duquesne 2017
Efficiently verify N aggregate signatures with 1 pairing and N ec additions: the Boneh-Lynn-Shacham signature scheme is orders of magnitude more efficient than Schnorr

BLS can mean 2 different things:

What is This?

It's a pretty neat thing I found!

Please see the Bamboo project for more info.

Lipmaa Iterative Function

def lipmaa_iterative(n)

Upcoming flags to enable link capturing and other PWA features. Enable these flags by copying and pasting the following, then searching for the below chrome://flags/

Enable full desktop integration:
chrome://flags/#enable-desktop-pwas

Capture URLs in their scope, such as twitter URLs for the Twitter PWA:
chrome://flags/#enable-desktop-pwas-link-capturing chrome://flags/#enable-desktop-pwas-stay-in-window

Get a pop-up that offers to allow the PWA to open certain URLs:

When you create a npm package, remember it might be used in a browser or a server, or even a command line utility… For each package you create, please pay attention at what it will be used for:

Is it going to be used as a dependency to a nodejs application that is not bundled? (e.g. command line utilities)
Is it going to be used as a dependency to a nodejs application that is bundled? (e.g. AWS Lambdas)
Is it going to be used as a dependency to a browser application (always bundled)?.

In cases 2) and 3) you want to allow for tree shaking.
In cases 1) and 2) you want to benefit from the "ES6"/"ES next" features supported natively by nodejs.
In case 3) you also want to benefit from the native support of "ES6" from your browser.

	#define _GNU_SOURCE
	#include <errno.h>
	#include <sched.h>
	#include <signal.h>
	#include <stdio.h>
	#include <stdlib.h>
	#include <sys/mount.h>
	#include <sys/stat.h>
	#include <sys/syscall.h>
	#include <sys/types.h>

	const zmq = require('zeromq')
	const config = require('./config')


	var sock = zmq.socket('sub')

	sock.connect('tcp://' + config.zmq_url)
	sock.subscribe('')

	sock.on('message', function(topic) {

	[target.wasm32-unknown-emscripten]
	rustflags = [
	"-Clink-args=-s EXPORTED_FUNCTIONS=['_draw'] -s ASSERTIONS=1",
	]