该 FAQ 并非意图一次性提供所有必要信息, 仅仅是提供必要的指路. 最后的杂项部分是宝藏区, 建议都翻翻看啦!
查看最新消息参阅 SD RESOURCE GOLDMINE 2 (English), 或者 sudoskys/StableDiffusionBook (中文)
建议优先阅读官方文档或者 SD RESOURCE GOLDMINE 或者 VOLDY RETARD GUIDE或者としあきdiffusion
| //CC2018 | |
| document.addEventListener('paste', function(evt) { | |
| //Import SVG copied to clipboard from Illustrator | |
| //remove last hidden character that will otherwise break the import | |
| if(document.activeElement.nodeName!="TEXTAREA"){ | |
| var str=evt.clipboardData.getData('text/plain').slice(0, -1); | |
| var svg=project.importSVG(str) | |
| svg.clipped=false; | |
| svg.children[0].remove() | |
| svg.parent.insertChildren(svg.index,svg.removeChildren()); |
这里的“流量”一般定义为中间人观测到的一组由（时间，方向，包大小）元数据组成的序列 [Cai2014]。其源头是应用层的读写操作，经过传输层协议的变换（分片、协议状态机、加密等），流量序列产生一定变化。但是这种变化非常有限，因为流量的发生过程本质是确定性的，随机因素较小，因此对于特定环境中的特定应用（浏览器访问 google.com）各种流量特征体现出相当大的一致性和独特性，这就使“从流量特征识别应用”的监督学习问题成为可能。虽然有若干不利因素使得确定性下降，例如多层次上软件多版本的排列组合爆炸、有状态的缓存、流水线和连接复用、用户随机行为，但是因为版本的幂律分布、应用层读写操作间的依赖关系、流量特征和检测算法的改进等原因，分类依然具有相当的可行性。
根据分类的对象产生了两个相近但是不同的研究领域。从流量特征中分类应用类型的被称为流量分类（traffic classification），从流量特征中分类所访问网站或者网页的被称为网站指纹（website fingerprinting）。以机器学习的方法而论前者是比后者更弱但本质相同的一个问题。
这两类攻击的威胁类型不同。流量分类威胁的是可用性，如果GFW检出流量是隧道应用然后进行封锁，则破坏了可用性。而网站指纹威胁的是匿名性和隐私，如果从隐秘流量中检出是谁在访问哪个网站，则破坏了匿名性，丝绸之路就是这样被FBI破获的。
A non-exhaustive list of WebGL and WebGPU frameworks and libraries. It is mostly for learning purposes as some of the libraries listed are wip/outdated/not maintained anymore.
| Name | Stars | Last Commit | Description |
|---|---|---|---|
| three.js | 
The early programmer struggles with the Javascript keyword this. But understanding your this context is easier than it seems.
This is all about where a function is invoked.
Often, early programmers worry about where the function was declared. Perhaps the function was declared in a specific file or a particular object. Surely this changes it's this!
Nope.
| #include "sphere.h" | |
| #include <vector> | |
| #include <iostream> | |
| #include <glm/gtc/matrix_inverse.hpp> | |
| #include <glm/gtc/type_ptr.hpp> | |
| #include <glm/gtx/string_cast.hpp> | |
| Sphere::Sphere() | |
| { |
Sometimes you want to have a subdirectory on the master branch be the root directory of a repository’s gh-pages branch. This is useful for things like sites developed with Yeoman, or if you have a Jekyll site contained in the master branch alongside the rest of your code.
For the sake of this example, let’s pretend the subfolder containing your site is named dist.
Remove the dist directory from the project’s .gitignore file (it’s ignored by default by Yeoman).
| 宋体 SimSun \5B8B\4F53 | |
| 黑体 SimHei \9ED1\4F53 | |
| 微软雅黑 Microsoft YaHei \5FAE\8F6F\96C5\9ED1 | |
| 微软正黑体 Microsoft JhengHei \5FAE\x8F6F\6B63\9ED1\4F53 | |
| 新宋体 NSimSun \65B0\5B8B\4F53 | |
| 新细明体 PMingLiU \65B0\7EC6\660E\4F53 | |
| 细明体 MingLiU \7EC6\660E\4F53 | |
| 标楷体 DFKai-SB \6807\6977\4F53 | |
| 仿宋 FangSong \4EFF\5B8B | |
| 楷体 KaiTi \6977\4F53 |
| I turned this gist into a "real" repository. It is here: http://github.com/pete/cats . | |
| Here, placed side-by-side for comparison, are GNU's implementation of | |
| cat, Plan 9's implementation, Busybox's implementation, and NetBSD's | |
| implementation, Seventh Edition Unix (1979), and 4.3BSD. | |
| For good measure (and because I suppose I am now committed to collecting | |
| cats) also included are Second Edition Unix (in assembly) and Inferno's | |
| implementation (in Limbo) for good measure. |
