Discover gists

List of embed fixer for discord/telegram.

The order is not relevant.

Service	Description	Author	Forked from	Repo	Host	Broken since
VixBluesky	FixBluesky: Embed Bluesky links in Discord!	Lexedia	FixBluesky	Lexedia/VixBluesky	https://bskx.app	Not broken
FixBluesky	FixBluesky: Embed Bluesky links in Discord!	Rose	None	ThornbushHQ/FixBluesky	https://bsyy.app	Not broken
bskye	Fix Bluesky embeds on Discord	Eduardo Cabral	None	FerroEduardo/bskye	https://bskye.app	Not broken
vxBsky	None	Dylan	None	dylanpdx/vxBsky	https://vxbsky.app	None

List of embed fixer for discord/telegram.

The order is not relevant.

Service	Description	Author	Forked from	Repo	Host	Broken since
VixBluesky	FixBluesky: Embed Bluesky links in Discord!	Lexedia	FixBluesky	Lexedia/VixBluesky	https://bskx.app	Not broken
FixBluesky	FixBluesky: Embed Bluesky links in Discord!	Rose	None	ThornbushHQ/FixBluesky	https://bsyy.app	Not broken
bskye	Fix Bluesky embeds on Discord	Eduardo Cabral	None	FerroEduardo/bskye	https://bskye.app	Not broken
vxBsky	None	Dylan	None	dylanpdx/vxBsky	https://vxbsky.app	None

Electron apps

Slide deck frameworks supporting Markdown source

The Unofficial 37signals/DHH Rails Style Guide

About This Document

This style guide was generated by Claude Code through deep analysis of the Fizzy codebase - 37signals' open-source project management tool.

Why Fizzy matters: While 37signals has long advocated for "vanilla Rails" and opinionated software design, their production codebases (Basecamp, HEY, etc.) have historically been closed source. Fizzy changes that. For the first time, developers can study a real 37signals/DHH-style Rails application - not just blog posts and conference talks, but actual production code with all its patterns, trade-offs, and deliberate omissions.

How this was created: Claude Code analyzed the entire codebase - routes, controllers, models, concerns, views, JavaScript, CSS, tests, and configuration. The goal was to extract not just what patterns are used, but why - inferring philosophy from implementation choices.

Minimal D3D11 part 3

An elaboration on Minimal D3D11 pt2, adding shadowmapping and incorporating various improvements and alternative approaches to the rendering setup, such as manual vertex fetching, samplerless texture lookup, null shader depth map rendering and procedurally generated texture and instance data.

As before, this is intended to be an an "API familiarizer" - an uncluttered Direct3D 11 setup & basic rendering reference implementation, in the form of a complete, runnable Windows application contained in a single function and laid out in a linear, step-by-step fashion. No modern C++ / OOP / obscuring cruft, only ~190 LOC. View on YouTube

Minimal D3D11

Minimal D3D11 reference implementation: An uncluttered Direct3D 11 setup + basic rendering primer and API familiarizer. Complete, runnable Windows application contained in a single function and laid out in a linear, step-by-step fashion that should be easy to follow from the code alone. ~200 LOC. No modern C++, OOP or (other) obscuring cruft. View on YouTube

Other gists in this series:

Minimal D3D11 part 2

	#TODO #1: Change the path to the folder you want to convert all the files
	Get-ChildItem "C:\Users\Path\To\Folder\Full\Of\PDFs" -Filter *.pdf \|
	Foreach-Object {
	Write-Host "Decrypting $($_.FullName)..."
	# TODO #2: Change the path to your qpdf.exe executable.
	C:\Path\to\qpdf\bin\qpdf.exe --decrypt $_.FullName "$($_.FullName).decrypted"
	Remove-Item $_.FullName
	Rename-Item "$($_.FullName).decrypted" -NewName $_.Name
	}