yosoyubik

You might want to check out Urbit: urbit.org. The whitepaper[1] is a bit outdated but in section 12 "Inadequate summary of related work" you can see some of its influences:

"Many historical OSes and interpreters have approached the SSI[2] ideal, but fail on persistence, determinism, or both. In the OS department, the classic single-level store is the IBM AS/400 [18]. NewtonOS [19] was a shipping product with language-level persistence. Many image oriented interpreters (e.g., Lisps [20] and Smalltalks) are also SSI-ish, but usually not transactional or deterministic. And of course, many databases are transactional and deterministic, but their lifecycle function is not a general-purpose interpreter."

- [1] https://media.urbit.org/whitepaper.pdf

- [2] "Solid-State Interpreter"

> Last Updated: September 24, 2018

This is very outdated and Tlon no longer operates/runs urbit.org but, in any case, the ToS says this: "The Site is owned and operated by Tlon", so the reference was to the website "urbit.org", not the Urbit project.

Urbit has always been open source—currently under the MIT license [1]—and same as Ethereum it's also guided by a non-profit foundation, the Urbit Foundation [2] established in 2021.

[1] https://github.com/urbit/urbit/blob/develop/LICENSE.txt [2] https://urbit.org/overview/people-history

Here's an old guide: https://blog.remilia.org/urbit-with-port/

This article [1] has some good points about it.

- [1] https://medium.com/dcspark/why-urbit-410d32961031

> Could somebody help with an ELI5 please?

"Essentially it just uses Ethereum as an event log and all the computation happens inside your Urbit instead of on-chain." [1]

A more up to date version of the document shared in the google group can be found in this video [2]

- [1] https://groups.google.com/a/urbit.org/g/dev/c/p6rP_WsxLS0/m/...

- [2] https://youtu.be/CKuHXrdkIw0

I'm going to defer to pcmonk's comments since they are 100% correct. Thanks btw! :)

Also, nemo1618's app is both a very nice flashcard app and one of the best ways to learn and get started developing apps for Urbit.

Thanks! :)

Thanks! I'm happy that you liked it :)

Thanks! That's something I'd like to improve.

Saving here means generating a (svg/png) file (each stroke is automatically saved on the backend). There is a chunking of the canvas on the frontend when the image is too big, so that adds a bit of time (multiple http requests... etc) This in a super alpha state, so plenty of room for performance improvements on my end, but I believe that this is probably pushing the limits of what Urbit can handle in terms of networking and file system a little bit for the current status.

It seems that Denmark is going to start using Chloroquine. See https://www.dr.dk/nyheder/indland/danske-forskere-vil-teste-...

(translated: https://www.translatetheweb.com/?from=&to=en&dl=en&ref=trb&a... )

From the discussion [1]: "A duct is akin to a first-class call stack".

For a more detailed explanation, you can look up the type definition [2] in Arvo (Urbit's Kernel) and here [3] you can find an example of how the stack looks when setting up a timer.

[1] https://urbit.org/blog/precepts-discussion/

[2] https://urbit.org/docs/tutorials/arvo/arvo/#duct

[3] https://urbit.org/docs/tutorials/arvo/move-trace/

Discussion: https://urbit.org/blog/precepts-discussion/

This is terrible. Was it Rysensteen Gymnasium?

Edited: Just found the article (Malling Skole i Østjylland)

https://www.dr.dk/nyheder/indland/skole-sender-klasse-i-kara...

Link to the slides: https://i3dsymposium.github.io/2019/keynotes/I3D2019_keynote...

Here some pictures[1][2] at devcon5.

- [1] https://twitter.com/lrettig/status/1181771915557367808

- [2] https://twitter.com/santisiri/status/1181771115749728256

There seems to be some controversy over the book that's mentioned in the video (Engelbart Hypothesis)

http://www.dougengelbart.org/library/books-unauthorized.html

"This book is unauthorized. Douglas Engelbart was not an author on this book. Eileen Clegg and Valerie Landau were the sole authors of this book. Listing Doug Engelbart as lead author was one of many problems with this book"