From the abstract, it sounds more like a toolkit for "Interactive / Hypermedia" papers. The paper itself is still dead.
I was hoping more for "Living" as in "active, uncertain, will grow over time".
A toolkit for expressing the research from beginning to the end - the state of the world as you understand it, highlighting the key uncertainties and experiments, and mechanisms for viewing the history.
As a motivating example for the type of "living research paper" that I'm thinking of, think of long-running software design decisions a la the implementation of `async/await` in rust.
It's an alphabetic writing system where the letters largely correspond to sounds, in contrast to logographic writing system where the symbol corresponds to the entire word (like Chinese or Japan).
Yes, there are special rules and outliers that you need to learn in English, but it seems absurd to not classify it as phonetic because it's not purely phonetic. This is doubly so when discussing phonetic vs whole-word learning systems, as is the topic with "Sold a Story".
If you don't mind sharing, what grade-level, decade, location were you taught this?
The key part about the pizza example is the demonstration of mathematical thinking completely disparate from what I experienced at a Catholic high-school in Chicago during the 2000s.
Despite seeing myself almost precisely described in that video and the original article, and despite having been diagnosed with ADHD as a college student...
It's hard for me to believe that there exists persons that won't / don't identify with that description, and thus the cause of my executive dysfunction isn't ADHD, but just a failure to cultivate habits of discipline.
Having suffered through learning highly configurable software tools independently enough times, I agree completely with "digesting one or few commands" at a time works better for me too.
Spitballing:
We could probably make a general solution for organically producing "learning guide" if power users 1) share their custom configurations and share the frequencies of commands they use.
Start with the general configuration, knowing nothing about the commands the tool offers. The learning guide is just a queue of "here's the most common config edit that you don't have" and "here's the most common command that you don't know about."
We are already share configs with eachother via the dotfiles pattern. We somewhat share command patterns via coding streams. Seems doable.
(In general, making it easier to learn new tech and for devs to share / refresh the learning material for a new tech seem underdeveloped.)
What the argument misses / why FTT is different than Terra
1) Alameda Research owns FTX, one of the largest and arguably most important crypto exchanges.
2) FTX offers fee discounts to FTT-stakers and additional discounts if you pay in FTT. [0]
3) Trading volume on FTX thus creates an organic demand cycle for FTT. The large firms will buy, stake, and then continuously refresh their supply.
4) The vast majority of the volume at FTT will be in margined accounts at FTX. I am uncertain if the volume analysis would capture FTT movements in (3).
Now, there's clearly financial alchemy going (giving away real economic value to boost an asset that you can then get leverage on) but that'd be better for Matt Levine or someone to flesh out.
> (1) I can have multiple domains for the same device, say gitea.mytsnetwork.com and netxcloud.mytsnetwork.com can go to the same device
I tried setting up caddy on a machine and then using caddy to reverse-proxy requests to each service i.e. `grafana.my-machine.tail-hex.ts.net` and `controller.my-machine.tail-hex.ts`
Obviously, `caddy` has no problem with the reverse proxy bit, but I did fail at being able to point multiple routes or subnet routes at the same machine via tailscle / magic-dns.
I'm sharing because it feels like something I should be able to do, and feel dumb not being able to figure it out.