Skip to content

Instantly share code, notes, and snippets.

View Inclushe's full-sized avatar

Ethan John Walker Inclushe

View GitHub Profile
@busybox11
busybox11 / twitter-logo.user.js
Last active May 17, 2024 19:42
Bring back old twitter logo
// ==UserScript==
// @name Bring back bird logo - twitter.com
// @namespace twitter scripts
// @match *://*.twitter.com/*
// @match *://*.x.com/*
// @grant none
// @version 1.5
// @author busybox11
// @description 7/24/2023, 1:47:07 PM
// @updateURL https://gist.githubusercontent.com/busybox11/0fea71f136ead45efc470f01f23de94b/raw
@robinst
robinst / twitter-archive-following-followers.md
Last active April 5, 2025 13:27
Twitter: How to archive your following/followers data (usernames, etc)

Twitter allows users to download parts of their data, see How to download your Twitter archive.

But what's not included in that data dump is the usernames/handles of the people that you follow or are following you. All you get is account IDs which is just an internal number and so a bit useless when it comes to archival.

Here's a way to get that data (you need to know how to run stuff in the terminal):

  1. Go to your Twitter profile in a desktop browser (Firefox or Chrome)
  2. Right click on page → Inspect → Network tab
  3. Click on the Following link (e.g. https://twitter.com/{yourusername}/following)
@0xabad1dea
0xabad1dea / copilot-risk-assessment.md
Last active September 11, 2023 10:21
Risk Assessment of GitHub Copilot

Risk Assessment of GitHub Copilot

0xabad1dea, July 2021

this is a rough draft and may be updated with more examples

GitHub was kind enough to grant me swift access to the Copilot test phase despite me @'ing them several hundred times about ICE. I would like to examine it not in terms of productivity, but security. How risky is it to allow an AI to write some or all of your code?

Ultimately, a human being must take responsibility for every line of code that is committed. AI should not be used for "responsibility washing." However, Copilot is a tool, and workers need their tools to be reliable. A carpenter doesn't have to

@tatsumoto-ren
tatsumoto-ren / subs.md
Last active April 21, 2025 23:08
Japanese Subtitles
@mattdesl
mattdesl / prompt-1.txt
Last active August 5, 2020 02:02
prompts for GPT3 / AIDungeon to generate Pantone Color of the Year 2021
Since 2000, the Pantone Color Institute has declared a particular color "Color of the Year". Twice a year the company hosts, in a European capital, a secret meeting of representatives from various nations' color standards groups. After two days of presentations and debate, they choose a color for the following year; for example, the color for summer 2013 was chosen in London in the spring of 2012.
Below is a list of all the winning "Colors of the Year" and their corresponding hex codes, from the year 2000 to 2050.
2000
Cerulean
#9BB7D4
2001
Fuchsia Rose
@pbrocks
pbrocks / install-phpcs-with-homebrew.md
Last active June 3, 2024 14:27
Install phpcs with Homebrew

Install phpcs with Homebrew

To set up php linting, you’ll want to install this PHP CodeSniffer repo and configure with this WordPress Coding Standards repo: . There are a number of ways to do this, whether direct download, Composer, Homebrew, Pear, etc. The following is what works for me on MacOS using Homebrew:

In a terminal window on your Mac, start by updating your Homebrew.

brew doctor

Then install the Code Sniffer:

@bmaupin
bmaupin / free-database-hosting.md
Last active April 21, 2025 19:02
Free database hosting
@jimmywarting
jimmywarting / readme.md
Last active April 19, 2025 05:22
Cors proxies
Exposed headers
Service SSL status Response Type Allowed methods Allowed headers
@wojteklu
wojteklu / clean_code.md
Last active April 21, 2025 06:12
Summary of 'Clean code' by Robert C. Martin

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.


General rules

  1. Follow standard conventions.
  2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
  3. Boy scout rule. Leave the campground cleaner than you found it.
  4. Always find root cause. Always look for the root cause of a problem.

Design rules