| :root { | |
| --font-main: "Inter", system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"; | |
| --font-lufga: "Inter", system-ui, "Segoe UI", Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"; | |
| } | |
| .theme_dark, .theme_moon_dark, .theme_moon_dark_conditional { | |
| --app-bg: #181715; | |
| --page-text: #F2E6D7; | |
| --primary: #F2E6D7; | |
| // ==UserScript== | |
| // @name Medium Paywall Bypass | |
| // @namespace Violentmonkey Scripts | |
| // @run-at document-start | |
| // @match *://*.medium.com/* | |
| // @match *://medium.com/* | |
| // @match *://*/* | |
| // @grant none | |
| // @version 2.3 | |
| // @inject-into content |
| apiVersion: storage.k8s.io/v1 | |
| kind: StorageClass | |
| metadata: | |
| name: gce-pd-retained | |
| reclaimPolicy: Retain | |
| provisioner: kubernetes.io/gce-pd | |
| parameters: | |
| type: pd-standard | |
| replication-type: none |
| // | |
| // ContentView.swift | |
| // Airdrop Demo | |
| // | |
| // Created by Daniel Kuntz on 7/30/23. | |
| // | |
| import SwiftUI | |
| struct ContentView: View { |
| // | |
| // CDView.swift | |
| // CD | |
| // | |
| // Created by Daniel Kuntz on 7/3/23. | |
| // | |
| import SwiftUI | |
| struct ShapeWithHole: Shape { |
Hi Christian,
I hope all is well!
I’m reaching out because we noticed a spike in Apollo's request rate on December 2nd. It was from approximately 14:17 to 14:23 UTC to /messages/inbox that went up by around 35% before returning to baseline. We are hoping you could help us understand what might have happened.
The source IPs were in AWS us-west-2: redacted, redacted, and redacted and had the Apollo UA server:apollo-backend:v1.0 (by /u/iamthatis) contact me@christianselig.com
| [ | |
| "marples", | |
| "darksi", | |
| "eth", | |
| "namecheap", | |
| "riseup", | |
| "webtorrent", | |
| "keybase", | |
| "m-d", | |
| "brave" |
ICANN TLDs will become available for auction at block 210240, around January 31 to February 2, 2024. As there's interest in preventing ICANN TLD trading on chain, we need to either completely disable claims and permanently seal reservations (soft-fork), or extend the claim period for these reserved names (hard-fork). Names on the reserved list fall into several categories: ROOT (ICANN TLDs),
| :root { | |
| --sand1: hsl(50, 20%, 99%); | |
| --sand2: hsl(60, 7.7%, 97.5%); | |
| --sand3: hsl(59, 6.5%, 95.1%); | |
| --sand4: hsl(58, 6.1%, 92.9%); | |
| --sand5: hsl(57, 6%, 90.7%); | |
| --sand6: hsl(56, 5.9%, 88.4%); | |
| --sand7: hsl(55, 5.9%, 85.2%); | |
| --sand8: hsl(51, 6%, 77.1%); | |
| --sand9: hsl(50, 2%, 55.7%); |
Apologies for the snarky title, but there has been a huge amount of discussion around so called "Prompt Engineering" these past few months on all kinds of platforms. Much of it is coming from individuals who are peddling around an awful lot of "Prompting" and very little "Engineering".
Most of these discussions are little more than users finding that writing more creative and complicated prompts can help them solve a task that a more simple prompt was unable to help with. I claim this is not Prompt Engineering. This is not to say that crafting good prompts is not a difficult task, but it does not involve doing any kind of sophisticated modifications to general "template" of a prompt.
Others, who I think do deserve to call themselves "Prompt Engineers" (and an awful lot more than that), have been writing about and utilizing the rich new eco-system