| You are ChatGPT, a large language model based on the GPT-5 model and trained by OpenAI. | |
| Knowledge cutoff: 2024-06 | |
| Current date: 2025-08-08 | |
| Image input capabilities: Enabled | |
| Personality: v2 | |
| Do not reproduce song lyrics or any other copyrighted material, even if asked. | |
| You're an insightful, encouraging assistant who combines meticulous clarity with genuine enthusiasm and gentle humor. | |
| Supportive thoroughness: Patiently explain complex topics clearly and comprehensively. | |
| Lighthearted interactions: Maintain friendly tone with subtle humor and warmth. |
As quixel is being removed, all items are free to aquire. This script is to automate the process to add items to your account (As of writing, a total of 18874 items)
Note: This script only tested in the latest version of Chrome.
run.js)
With these steps I managed to get Pimox on my Raspberry Pi 4 and 5 in february 2024.
Install "RPi OS Lite 64-bit" with Raspberry Pi Imager. It's listed under "Raspberry Pi OS (Other)"
| #!/usr/bin/env -S bash -c "docker run -p 8080:8080 -it --rm \$(docker build --progress plain -f \$0 . 2>&1 | tee /dev/stderr | grep -oP 'sha256:[0-9a-f]*')" | |
| # syntax = docker/dockerfile:1.4.0 | |
| FROM node:20 | |
| WORKDIR /root | |
| RUN npm install sqlite3 |
| /* EDIT MODE */ | |
| .canvas-node .HyperMD-header.HyperMD-header-1 { | |
| text-align: center; | |
| } | |
| /* PREVIEW MODE */ | |
| .canvas-node .markdown-preview-view h1 { | |
| text-align: center; |
The Registry Modification API is a framework for adding future API which easily allows mutating or adding entries into both the built-in registries and the data-driven registries.
There are several definitions to cover first:
Built-in Registry: A registry that is unmodifiable by datapacks. They are created/loaded via static initializers
| # Script for converting a HF Diffusers saved pipeline to a Stable Diffusion checkpoint. | |
| # *Only* converts the UNet, VAE, and Text Encoder. | |
| # Does not convert optimizer state or any other thing. | |
| # Written by jachiam | |
| import argparse | |
| import os.path as osp | |
| import torch |
This gist intends on clearing up some of the misinformation surrounding signed chat/the reporting feature Mojang has added to Minecraft 1.19.1. Here you can find both technical information as well as a general explanation of how these work.
After joining a server, clients now send a profile key used for verifying a message's authenticity. This key and thus the whole signing process is optional, but by default, servers enforce secure profiles for clients to send chat messages. Whenever the player sends a chat message and has a key associated, the message will be signed using their own private key, which the server then verifies using the public key sent after join. Assuming signature, timestamp, and message contents line up, the message goes through.
On the other end, clients can also require all broadcasted player messages to be signed, disregarding the ones without sender verified signatures.
| import org.jetbrains.exposed.sql.Column | |
| import org.jetbrains.exposed.sql.ColumnType | |
| import org.jetbrains.exposed.sql.CustomStringFunction | |
| import org.jetbrains.exposed.sql.EqOp | |
| import org.jetbrains.exposed.sql.Expression | |
| import org.jetbrains.exposed.sql.ExpressionWithColumnType | |
| import org.jetbrains.exposed.sql.Table | |
| import org.jetbrains.exposed.sql.statements.api.PreparedStatementApi | |
| import org.jetbrains.exposed.sql.statements.jdbc.JdbcPreparedStatementImpl | |
| import org.jetbrains.exposed.sql.stringLiteral |
