https://typora.io/ https://github.com/nhnent/tui.editor https://ui.toast.com/tui-editor/
python third_party/blink/tools/run_blink_wptserve.py -t Linux
./out/Linux/chrome --enable-blink-features=MojoJS,MojoJSTest
checking for flakyness:
third_party/blink/tools/run_web_tests.py -t Linux external/wpt/idle/interceptor.https.html --repeat-each=100
cmake .. -DBUILD_TESTS=OFF -DBUILD_PYTHON=ON -DPYBIND11_PYTHON_VERSION=2.7 -DPYTHON_INSTALL_DIR=/Users/goto/Library/Python/2.7/lib/python/site-packages/ -DPYTHON_EXECUTABLE=/usr/local/bin/python
Signing-in and authenticating
https://indieauth.com/auth?me=http%3A%2F%2Fcode.sgo.to&client_id=http%3A%2F%2Fcode.sgo.to&state=456&scope=read%20follow%20mute%20block%20create&redirect_uri=http%3A%2F%2Fcode.sgo.to
Redirected to
https://poly.google.com/view/9-b6-yqrwEe
reasons why we need view source
declarativeness:
how do i reproduce this? i can download the model, but how do i get that lighting? that sky? how do i even learn these words? how do i position the camera? how would i even learn about the existance of a camera?
holographic projections. how do i learn about that?
The routing problem
in content-centric networks is making (efficiently and resiliently) a connection between content names
and hosts.
The overall idea of the user-oriented name system
is to address a subset of the problem where the content is addressed by author
first and filename
second (but in a manner that still de-couples content from hosts).
UNS, much like DNS, works as a hierarchical resolution algorithm. It talks to root-level ANS servers to find trackers given an author name
.
Trackers, much like bittorrent, enable hosts to register their ability/desire to serve content for a specific content name, which is then later used to answer user queries of where to find content.
UNS servers exchange data between themselves with a gossip protocol, propagating the routing tables (mapping usernames to trackers) to each other, eventually converging.