10 Matching Annotations
- Nov 2022
-
bl.ocks.org bl.ocks.org
-
allows you to
t2
-
and when us
persistence test
-
- May 2022
-
android.stackexchange.com android.stackexchange.com
-
https://bl.ocks.org/Stvad/raw/440bdffa0f7d74f9a4835b01df717662/ snapshot of the first answer (was originally delete and then restored?)
-
- Apr 2022
-
bl.ocks.org bl.ocks.org
-
and directly use the websocket instead (I reverse engineered enough of the protocol to be able to connect +
yay
-
-
cute-spice-cardigan.glitch.me cute-spice-cardigan.glitch.me
-
Still have questions?
Embedded annotations!
-
-
wattenberger.com wattenberger.com
-
margins work similarly to our last example — they are based on the size of their parent. However, there is one weird thing here that is important to note:margin-top is based on our parent’s width, not height (and the same goes for margin-bottom). In other words, all margins are a percent of their parent's width.
Seems like a bug 😅
-
- Nov 2021
-
subconscious.substack.com subconscious.substack.com
-
Mixing up the order of capture-organize-synthesize causes friction. It forces us to make decisions before we’re ready. This friction manifests as blank page anxiety, creative block, lost ideas. That’s the feeling of the system fighting you.
Zettlekasten is in a way about solving this
-
- Oct 2021
-
-
This keeps Subtext simple. Rather than extending the syntax of Subtext to include a complex feature like tables, we might, for example, link to a .csv file, which then gets rendered as a table. This also means the data stays in its native file type, and can be used in other applications.
This is true and interesting, but it also prevents you from deeply linking/integrating data in those documents with your notes.
-
- Dec 2020
-
h.readthedocs.io h.readthedocs.io
-
Using the Hypothesis API¶
It'd be great if there were a guide for spinning-up a self-hosted version of the API/Backend
-
-
www.geoffreylitt.com www.geoffreylitt.com
-
Accessibility: Today, it requires a big jump to go from using browser extensions to creating them: you need to learn a fair amount of web development to get started, and you can’t easily develop extensions in the browser itself. What if there were a quick way to get started developing and sharing extensions in the browser?
I also had this thought recently - I think userscript's (via Greasemonkey &co) are kind of a stepping stone for this. You're still required to learn a bunch of things about web development, but the setup required to start doing things/sharing things is minimal
-