This is a living document. Everything in this document is made in good faith of being accurate, but like I just said; we don't yet know everything about what's going on.
Update: I've disabled comments as of 2025-01-26 to avoid everyone having notifications for something a year on if someone wants to suggest a correction. Folks are free to email to suggest corrections still, of course.
If you want to download an older version ive heard 205.15 works well, i reccomend ApkMirror
https://vd-plugins.github.io/proxy/maisymoe.github.io/strife/Experiments into the input and click InstallTabs V2 - redesign opt-out/in for all and select Control Bucket.Ive also heard enmity works well for IOS.
Hello! It's been a while since I've done any write-ups, but I thought I'd do one to (hopefully) bring a little clarity to a situation that's been causing a lot of confusion and misinformation.
I'm thinking I'll go through what the problem is and why it happens. So, I guess, let's dive in:
Some people are finding that upon updating to 17.0.0, their consoles are getting a blackscreen and refusing to boot further.
| .arm.big | |
| .open "patches/sections/0x5000000.bin","patches/patched_sections/0x5000000.bin",0x05000000 | |
| ; patch IOS_CheckDebugMode to always return 0 | |
| .org 0x0501fc98 | |
| .thumb | |
| mov r0, #0 | |
| mov r0, #0 |
Discord is now slowly rolling out the ability to send colored messages within code blocks. It uses the ANSI color codes, so if you've tried to print colored text in your terminal or console with Python or other languages then it will be easy for you.
To be able to send a colored text, you need to use the ansi language for your code block and provide a prefix of this format before writing your text:
\u001b[{format};{color}m
| # may or may not be inspired by plutoo's ctrrpc | |
| import errno | |
| import socket | |
| import os | |
| import sys | |
| import struct | |
| import codecs | |
| from time import sleep | |
| def buffer(size): |
Discord timestamps can be useful for specifying a date/time across multiple users time zones. They work with the Unix Timestamp format and can be posted by regular users as well as bots and applications.
The Epoch Unix Time Stamp Converter is a good way to quickly generate a timestamp. For the examples below I will be using the Time Stamp of 1543392060, which represents November 28th, 2018 at 09:01:00 hours for my local time zone (GMT+0100 Central European Standard Time).
| Style | Input | Output (12-hour clock) | Output (24-hour clock) |
|---|---|---|---|
| Default | <t:1543392060> |
November 28, 2018 9:01 AM | 28 November 2018 09:01 |
| 0-00.usa.cc | |
| 0-attorney.com | |
| 0-mail.com | |
| 00.msk.ru | |
| 000777.info | |
| 000invaliddomain.local | |
| 001.igg.biz | |
| 0033.pl | |
| 0039.cf | |
| 0039.ga |
It's come to my attention that some people have been spamming issue trackers with a link to this gist. While it's a good idea to inform people of the situation in principle, please do not do this. By all means spread the word in the communities that you are a part of, after verifying that they are not aware yet, but unsolicited spam is not helpful. It will just frustrate people.
A number of things have happened since the last update.