| """ | |
| The 2024 Transformer (the Noam Transformer): | |
| - RMSNorm | |
| - GQA or some combination | |
| - Sliding window attention | |
| - Swiglu | |
| - RoPE (Rotary Positional Embedding) | |
| LLM Arches: | |
| hidden | MLP mult. | n_layers | rope_theta | GQA Group Size | GLU Act. | ops |
Note
This does not works in browser for quests which require you to play a game! Use the desktop app to complete those.
How to use this script:
Console tab
...and why it matters.
You might have seen my HiveCorruptor plugin on Poggit. To be clear, I don't have a vendetta against The Hive or anything like that, the plugin was more so a comedic demonstration of how the blob cache can be exploited to crash clients. The next thing you're probably thinking is "how the hell does this work?" - and this is what this article will go over.
Some notes and tools for reverse engineering / deobfuscating / unminifying obfuscated web app code.
HuggingFace Page for model download: https://huggingface.co/hakurei/waifu-diffusion-v1-3
Note: This is all almost full YouTube ID informations. Original owner goes to AgentOak, modified version by Martin Eesmaa.
See the credits and also special thanks in below.
Before this gist has been forked, AgentOak made original gist on November 13 2019 and it was last updated on May 5 2021.
From now on, this forked gist is maintained by Martin Eesmaa since 17 September 2022.
Last updated: 07 February 2026
以下分析基于 Magisk 76ddfeb93a8b3612cd68988323f422e996751e16
由于 Magisk 更新太快了，决定弃坑，自己去看源码罢！
Zygisk 加载是通过替换 app_process ，修改 LD_PRELOAD ，再执行原 app_process 实现的。
| # I absolutely hated crypto-js for this. non-standard configurations, weird algorithms, ... | |
| # well obviously you can encrypt it with a better configuration which people will not | |
| # go crazy figuring out its implementation, but in this case I wasn't encrypting the data. | |
| import base64 | |
| from Crypto.Hash import MD5 | |
| from Crypto.Util.Padding import unpad | |
| from Crypto.Cipher import AES | |
| # generated using: CryptoJS.AES.encrypt('test 123456 plaintext', 'some password').toString() |
| <?xml version="1.0"?><!DOCTYPE fontconfig SYSTEM "fonts.dtd"> | |
| <fontconfig> | |
| <dir>~/.fonts</dir> | |
| <!-- | |
| Documented at | |
| http://linux.die.net/man/5/fonts-conf | |
| To check font mapping run the command at terminal | |
| $ fc-match 'helvetica Neue' | |
The Client Blob Cache is a new Bedrock optimization - it allows blocks and biomes to be cached on Clients to avoid resending identical chunks over and over. Chunks and biomes make up the vast majority of network traffic in a lot of common cases (eg. login, teleport or dimension switches) but at the same time, they rarely change. Allowing the Client to reuse chunks it has seen in the past can save a ton of traffic and latency!
The Client Cache is a Content Addressed Storage (a bit like git) that stores Blobs and retrieves them based on their full hashes (BlobIds). This means that the cache doesn't actually know about Chunks - in the future, we might start using it for more types of data, like skins or data driven entities.
A nice thing we get from the CAS approach is that the cache is persistent: returning players will be able to reuse content that was sent them in previous sessions or even previous sessions in different servers as long as tha
