Robert Claypool robert-claypool

❯ 02:09:42 PM …/keystone-capture on main 2m49s
❯ ./bin/kscapture start
[OK]   Runtime started
[OK]   ASR server: http://localhost:8080/inference (whisper-large-v3-turbo)
[OK]   Recording from default microphone
       Press Ctrl+C to stop.
^C
[OK]   Stopping...
[OK]   State: Ready

"Whenever I start thinking about CORS, my intuition about which site hosts the headers is incorrect, just as you described in your question. For me, it helps to think about the purpose of the same origin policy.

The purpose of the same origin policy is to protect you from malicious JavaScript on siteA.com accessing private information you've chosen to share only with siteB.com. Without the same origin policy, JavaScript written by the authors of siteA.com could make your browser make requests to siteB.com, using your authentication cookies for siteB.com. In this way, siteA.com could steal the secret information you share with siteB.com.

Sometimes you need to work cross domain, which is where CORS comes in. CORS relaxes the same origin policy for domainA.com, using the Access-Control-Allow-Origin header to list other domains (domainB.com) that are trusted

The Internet Assigned Numbers Authority (IANA) has reserved the following three blocks of the IP address space for private internets:

10.0.0.0     -  10.255.255.255  (10/8 prefix)
172.16.0.0   -  172.31.255.255  (172.16/12 prefix)
192.168.0.0  -  192.168.255.255 (192.168/16 prefix)

We will refer to the first block as "24-bit block", the second as

Keybase proof

I hereby claim:

I am robert-claypool on github.
I am robert_claypool (https://keybase.io/robert_claypool) on keybase.
I have a public key whose fingerprint is 3606 A66E CA1C 3107 DFED 32DF 6AF2 BF57 992F 19ED

To claim this, I am signing this object:

-- This requires https://www.postgresql.org/docs/8.3/static/pgcrypto.html
-- A `sync_stamp` is our current database time with HMAC sig.
-- The dot "." separates data and sig as with https://jwt.io/
-- Unlike JWT, the sig is not base64 encoded.
SELECT to_char(CURRENT_TIMESTAMP, 'YYYYMMDDHH24MISSUS')
    || '.'
    || hmac(to_char(CURRENT_TIMESTAMP, 'YYYYMMDDHH24MISSUS'), 'SUPER-DUPER-SECRET', 'md5')
    as sync_stamp;
-- 20180712215107309054.\xaf330cffa927bd496c153e09b559c71d

	Below is a single, merged blueprint that folds in the strongest parts of both engineers' proposals and the prior plan. It is written in the Graphile‑Starter style you are already using.

	---

	## Checklist

	* Separate adherence from the scorecard model; reuse patients/providers/organizations/data\_imports.
	* Model categories, statuses, opportunities, action types, and reason codes as lookup tables with text PKs and smart tags.
	* Add a global pharmacies reference; keep adherence facts org‑scoped for RLS.
	* Store PDC as integer basis‑points (0..10000). Expose percents via computed columns or views.

	import arcpy
	import os

	def create_network_dataset(gdb_path):
	"""
	Creates a network dataset in a file geodatabase based on an XML workspace document schema.

	Args:
	gdb_path (str): Path to the file geodatabase.
	"""

	{
	"name": "Blob Fail Workflow",
	"nodes": [
	{
	"parameters": {},
	"name": "Start",
	"type": "n8n-nodes-base.start",
	"typeVersion": 1,
	"position": [
	240,


	{
	"editor.fontSize": 12,
	"editor.rulers": [80],
	"vim.insertModeKeyBindings": [
	{
	"before": ["j", "j"],
	"after": ["<Esc>"]
	}
	],