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.

huytd

How to use:

./wordle.sh

Or try the unlimit mode:

cpursley

Postgres Full Text Search

Do you really need Elastic Search?

• https://www.postgresql.org/docs/current/pgtrgm.html
• https://scoutapm.com/blog/how-to-make-text-searches-in-postgresql-faster-with-trigram-similarity
• https://about.gitlab.com/blog/2016/03/18/fast-search-using-postgresql-trigram-indexes/
• https://mazeez.dev/posts/pg-trgm-similarity-search-and-fast-like
• https://alexklibisz.com/2022/02/18/optimizing-postgres-trigram-search.html
• https://www.freecodecamp.org/news/fuzzy-string-matching-with-postgresql/

dorianmariecom

/* global __DEV__ */
import React, { useState, useEffect, useRef } from "react"
import {
  facebookAppId,
  facebookDisplayName,
  iosOneSignalAppId,
  androidOneSignalAppId,
  sentryDsn,
} from "./app.json"
import { version } from "./package.json"

radiantly

// ==UserScript==
// @name        Prevent link mangling on Google
// @namespace   LordBusiness.LMG
// @match       https://www.google.com/search
// @grant       none
// @version     1.1
// @author      radiantly
// @description Prevent google from mangling the link when copying or clicking the link on Firefox
// ==/UserScript==

skandavivek

import requests
import os
import json
from bs4 import BeautifulSoup
import pandas as pd
from matplotlib import pyplot as plt
import numpy as np
import time

0xabad1dea

Risk Assessment of GitHub Copilot

0xabad1dea, July 2021

this is a rough draft and may be updated with more examples

GitHub was kind enough to grant me swift access to the Copilot test phase despite me @'ing them several hundred times about ICE. I would like to examine it not in terms of productivity, but security. How risky is it to allow an AI to write some or all of your code?

Ultimately, a human being must take responsibility for every line of code that is committed. AI should not be used for "responsibility washing." However, Copilot is a tool, and workers need their tools to be reliable. A carpenter doesn't have to

Harshmakadia

// 1. Go to https://analytics.twitter.com/ 

// 2. Keep scrolling till the end until all the stats data is loaded

// 3. Right click on the page click on last option "Inspect" a window should open select console from that

// 4. copy this entire function

function getVal (val) {
    val=val.replace(/\,/g,'');

wlib

MIT License

Copyright (c) 2021 Daniel Ethridge

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

bacarini

---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: n8n-deployment
  namespace: standard
  labels: &labels
    app: n8n
    component: deployment
spec: