Episode Details

AJ is a software engineer interested in Urbit and data composability. 

Twitter: https://twitter.com/ajlamarc

https://www.ajlamarc.com/

Keep an eye out on Holium, and making it easier to code in Javascript for Urbit

Notes

1. What is data composability?

   1. Multiple applications sharing data and make the interfaces work together

   2. OpenAIs that both Twitter and Facebook had and then were shut down

   3. Data is the main product that these applications have

   4. You can separate the data and the code

   5. Personal AI

2. How did we get to such a fragmented application landscape?

3. Legacy internet vs New Internet?

4. What is AJ working on?

   1. TomeDB

   2. Javascript package

   3. Associated gall agent

   4. NoSQL database

   5. The front end side is the interesting part

5. What are gall agents?

   1. Standardized backend of Urbit

   2. Rules for moving data between different servers and accounts

6. What are you looking for in a backend?

7. Why are you reinventing the wheel when building a new urbit backend?

8. What is the promise of urbit?

9. What is the main draw of urbit?

10. What does it mean to be permissionless?

11. Urbit brings the best out of the past

12. How much data is stored when you host your urbit on the cloud vs your own database?

13. What are the technical limitations that an Uribit can store?

    1. 4-8 GBs can be stored and its stored in RAM

14. How long until we have video streaming on Urbit?

15. What is your take on where AI and Urbit mingle?

16. How do you have an AI work for you rather than a big corporation?

17. Urbit is creating a virtual world where you get only what you want and little of what you want

18. The s