Skip to content

Instantly share code, notes, and snippets.

@k16shikano
k16shikano / SKILL.md
Last active June 17, 2026 02:31
japanese-tech-writing/SKILL
name japanese-tech-writing
description 日本語の技術文書・書籍原稿の文章規範。整形(一文一行、引用ブロック、脚注、コラム記法)、段落と論証の構成(パラグラフライティング)、論証の厳密さ(ツッコミどころの除去)、読み手の負荷の管理、視点と語り、演出の抑制、LLM っぽい空句の禁止、冗長の排除を定める。日本語で技術書の章、草稿、記事、解説文を書くとき、または推敲・リライトするときに使用する。

日本語技術文書の文章規範

日本語で技術的な原稿(書籍の章、記事、解説文)を書く・推敲するときは、以下の規範に従う。

整形

@aamiaa
aamiaa / CompleteDiscordQuest.md
Last active June 17, 2026 02:20
Complete Recent Discord Quest

Caution

As of April 7th 2026, Discord has expressed their intent to crack down on automating quest completion.

Some users have received the following system message:

image

There isn't much I can do to make the script undetected, so use it at your own risk, as you most likely WILL get flagged by doing so.

Complete Recent Discord Quest

@LessUp
LessUp / glm-coding-plan-rush-helper.user.js
Last active June 17, 2026 02:23
⚡ GLM Coding Rush — 智谱编程助手一键抢购脚本 | Auto-Purchase Userscript for GLM Coding | 自动解锁售罄 · 高速重试 · 定时触发 · 支付保护 · 中英双语面板 | Auto-unlock sold-out · High-speed retry · Scheduled trigger · Payment guard · Bilingual panel | Tampermonkey/Violentmonkey | 点击 Raw 安装 · Click Raw to install
// ==UserScript==
// @name GLM Coding Rush - 智谱编程助手抢购脚本
// @namespace https://gist.github.com/LessUp
// @version 1.1.0
// @description 智谱 GLM Coding 一键抢购脚本 — 自动解锁售罄按钮 / 高速重试引擎 / bizId 双重校验 / 错误弹窗自动恢复 / 支付弹窗保护 / 秒级定时触发 / 可拖拽浮动面板
// @author LessUp
// @match *://www.bigmodel.cn/*
// @match https://bigmodel.cn/glm-coding*
// @run-at document-start
// @grant none
@jedavidson
jedavidson / 2521_exercises.md
Last active June 17, 2026 02:17
A curated list of some good revision and exam preparation programming problems for UNSW's COMP2521. Personal opinion.

These exercises are some I did while studying for COMP2521, as well as some others which I've found afterwards which I think will be relevant. I've collected these problems mostly from LeetCode and HackerRank, which are excellent sites for practicing your coding abilities. Accounts on both sites will be necessary to do the problems listed.

The difficulty ranking is obviously my opinion, but generally speaking here is what they mean:

  • Easy: Problems that you should be able to do without too much difficulty.
  • Intermediate: Problems that are a bit harder, but should be doable with a little bit of thought and intuition.
  • Challenges: Problems that I think are difficult and/or interesting, if you're up for it. There are almost all harder than what's within the scope of 2521.

If you're able to solve the easy and intermediate problems without much difficulty, you're probably very well prepared for any programming questions you'll receive in the ex

@skull-squadron
skull-squadron / captive-portal-detection-and-internet-presence.md
Created May 16, 2023 20:30
Captive portal detection and internet presence URLs by vendor
@samsch
samsch / stop-using-jwts.md
Last active June 17, 2026 02:21
Stop using JWTs

Stop using JWTs!

TLDR: JWTs should not be used for keeping your user logged in. They are not designed for this purpose, they are not secure, and there is a much better tool which is designed for it: regular cookie sessions.

If you've got a bit of time to watch a presentation on it, I highly recommend this talk: https://www.youtube.com/watch?v=pYeekwv3vC4 (Note that other topics are largely skimmed over, such as CSRF protection. You should learn about other topics from other sources. Also note that "valid" usecases for JWTs at the end of the video can also be easily handled by other, better, and more secure tools. Specifically, PASETO.)

A related topic: Don't use localStorage (or sessionStorage) for authentication credentials, including JWT tokens: https://www.rdegges.com/2018/please-stop-using-local-storage/

The reason to avoid JWTs comes down to a couple different points:

  • The JWT specification is specifically designed only for very short-live tokens (~5 minute or less). Sessions