lizthegrey

default['sshd']['sshd_config']['AuthenticationMethods'] = 'publickey,keyboard-interactive:pam'
default['sshd']['sshd_config']['ChallengeResponseAuthentication'] = 'yes'
default['sshd']['sshd_config']['PasswordAuthentication'] = 'no'

nzvtrk

/* Basic example of saving cookie using axios in node.js and session's recreation after expiration.
 * We have to getting/saving cookie manually because WithCredential axios param use XHR and doesn't work in node.js
 * Also, this example supports parallel request and send only one create session request.
 * */

const BASE_URL = "https://google.com";

// Init instance of axios which works with BASE_URL
const axiosInstance = axios.create({ baseURL: BASE_URL });

ryzokuken

const hash = require('easy-crypto/hash');

class MerkleTreeNodeGeneric {
    compare(node) {
        return this.hash === node.hash;
    }
}

class MerkleTreeChildNode extends MerkleTreeNodeGeneric {
    constructor(data) {

sbrichardson

/*
Make sure you are wearing the hr monitor, as it typically
goes to sleep when inactive, not allowing you to connect to it.

Instructions
=============
1. Using Google Chrome, open the dev console and paste the below code.
2. A panel near the address bar will open, searching for nearby bluetooth (ble)
   heart rate devices. Don't click away from the panel or Chrome will cancel the search.

bvaughn

This API was removed in React 17

---

Interaction tracing with React

React recently introduced an experimental profiler API. After discussing this API with several teams at Facebook, one common piece of feedback was that the performance information would be more useful if it could be associated with the events that caused the application to render (e.g. button click, XHR response). Tracing these events (or "interactions") would enable more powerful tooling to be built around the timing information, capable of answering questions like "What caused this really slow commit?" or "How long does it typically take for this interaction to update the DOM?".

With version 16.4.3, React added experimental support for this tracing by way of a new NPM package, scheduler. However the public API for this package is not yet finalized and will likely change with upcoming minor releases, so it should be used with caution.

funkjunky

export const webFileToResumableDescriptor = (file, uploadId) => async function(chunkSize) {
    uploadId = uploadId || file.name;
    return {
        bytesCount: file.size,
        uploadId: uploadId,
        filename: file.name,
        generator: async function*() {
            let chunkIndex = 0;

            // While starting byte is less than the file size, continue.

markerikson

const createMySocketMiddleware = (url) => {
    return storeAPI => {
        let socket = createMyWebsocket(url);

        socket.on("message", (message) => {
            storeAPI.dispatch({
                type : "SOCKET_MESSAGE_RECEIVED",
                payload : message
            });
        });

claustres

import { TooManyRequests } from 'feathers-errors'
import { RateLimiter } from 'limiter'
import makeDebug from 'debug'
const debug = makeDebug('debug')

export function rateLimit (options) {
  const limiter = new RateLimiter(options.tokensPerInterval, options.interval)

  return function (hook) {
    if (hook.type !== 'before') {

claustres

module.exports = {
  host: process.env.HOSTNAME || 'localhost',
  port: 8081,
  // Global API limiter
  apiLimiter: {
    http: {
      windowMs: 60*1000, // 1 minutes window
      delayAfter: 30, // begin slowing down responses after the 30th request
      delayMs: 1000, // slow down subsequent responses by 1 seconds per request 
      max: 60 // start blocking after 60 requests

claustres

import { RateLimiter as SocketLimiter } from 'limiter'
import HttpLimiter from 'express-rate-limit'
import { TooManyRequests } from 'feathers-errors'
import makeDebug from 'debug'
...
const debug = makeDebug('debug')

function setupSockets (app) {
  const apiLimiter = app.get('apiLimiter')
  const authConfig = app.get('authentication')