Getting Started
Table of Contents
<div class="mobile-wrap"> | |
<div class="mobile clearfix"> | |
<div class="header"> | |
<span class="ion-ios-navicon pull-left"><i></i></span> | |
<span class="title">Home</span> | |
<span class="ion-ios-search pull-right"></span> | |
<div class="search"> | |
<form method="post"> |
addEventListener("fetch", (event) => { | |
event.respondWith( | |
handleRequest(event.request).catch( | |
(err) => new Response(err.stack, { status: 500 }) | |
) | |
); | |
}); | |
async function handleRequest(request) { | |
const { pathname, searchParams, host } = new URL(request.url); |
{ | |
"$jason": { | |
"head": { | |
"templates": { | |
"body": { | |
"background": { | |
"type": "camera", | |
"options": { | |
"device": "back" | |
} |
Getting Started
Table of Contents
I'm so old I remember when arrays in JavaScript didn't have forEach()
or map()
, and a lot of libraries would implement their own functional looping constructs, which were better than regular loops because you got a new function scope (remember, we didn't have let
or const
either). We all had to adjust when native forEach()
landed because we were used to jQuery's each()
, which had the arguments in the wrong order.
I was reminded of this while doing some scraping last week using Cheerio to load and traverse an HTML page in Node. Cheerio implements a jQuery-like API, which is genuinely pleasant to use, but carries some of that legacy behavior (like each(index, item)
argument ordering) with it in ways that are jarring if you haven't used actual jQuery in a while. Fortunately, Cheerio also implements the iterator protocol on its collections, so if you just want the items for a given selector, you can use for ... of
loops and not have to think abo
SOCKSPort 9050 | |
ExcludeNodes {ru} | |
ExcludeExitNodes {ru},{kz},{by},{cn},{kg},{tj},{uz},{ir} | |
Log notice file /var/log/tor/notices.log |
This is a sample web app implemetation in Google Apps Script that receives a JSON payload and inserts it directly into a Google spreadsheet. It is a demo implementation for Automate app flow Google Spreadsheets Integration.
Using just one HTTP Request block in an Automate flow you can send data from your Automate flows directly into Google Spreadsheets! Pretty neat, isn't it?
https://docs.google.com/spreadsheets/d/1VZEp-ru9BH9AQSNHzRxnJZx1Nabviz6UiN9PIelOjA8
/* ------------------------------------------------------- / | |
TITLE: SQL Server Find and Replace Values in All | |
Tables and All Text Columns | |
SOURCE: https://www.mssqltips.com/sqlservertip/1555/sql-server-find-and-replace-values-in-all-tables-and-all-text-columns/ | |
/ ------------------------------------------------------- */ | |
USE MyDatabaseNameHere | |
BEGIN TRANSACTION |
SOCKSPort 9050 | |
ExcludeNodes {ru} | |
ExcludeExitNodes {ru},{kz},{by},{cn},{kg},{tj},{uz},{ir} | |
Log notice file /var/log/tor/notices.log |
addEventListener("fetch", event => { | |
event.respondWith(handleRequest(event.request)) | |
}) | |
//////////////////////////////////////////////////////////////////////////////////////////////////// | |
// ! DON'T LEAK THE SECRETS ! | |
// Use Workers KV if you can https://developers.cloudflare.com/workers/reference/storage/ | |
const telegram_token = "*****REDACTED*****"; | |
const telegram_url = "https://api.telegram.org/bot" + telegram_token + "/sendMessage"; |