---
# System prepended metadata

title: thoughts

---


# thoughts

# ankeet
## things about agregore i didn’t realize until i actually got to making an app

- it’s hard to let other people edit your instance
- it’s easy to let other people copy your instance (i think we could put a “fork” button onto pages or into the browser?)
- since editing and pushing can be done right in the browser, making things automatically save/push themselves is less complicated than i expected


## things to play with 
- using different features of different protocol handlers
- interacting with all of them in one app
- qr codes!!! also ipns? or other well-known-name stuff


# judy
## experience
- quickly realized no separation between content and presentation: 
    - [very different from traditional web dev] you don’t save user generated 
- stage data is classes
    - not traditional javascript OOP at all, object structure is implicit in classes
- very quickly hated typing in dev tools, immediately started wholesale editing in a text editor
- workflow:
    - edited in vscode
    - loaded index.html in firefox just for javascript
    - then to see if saving in agregore worked, copied index.html into agregore devtools, edited HTML, shoved new pasted code in there, then typed await save();, reloaded page, tested stuff there.
        - aka used dev tools when there was a bug or an append tiny change
        - would have to remember to copy the edits into the source of truth file in the text editor
        - this means there’s separate sources of truth - one for code, and one for data. not SUPER hard but still frictional
    - really it’s bootstrapping the app, and then playing with it in agregore. an end user might not need to modify the code so it wouldn’t matter

## things to play with
- curious how earthstar will work. will i have to have a page on hyper that’s hosting my earthstar app?
    - still need something to “host” the live app, earthstar would be the underlying data store?
- would be cool if agregore oculd manage your replicas and identity.json
- doesn’t make sense for there to be an earthstar:// since it’s not a hosting protocol, it’s a protocol for saving data
- earthstar has an explicit app/content separation, and app/content separation can’t be done rn in the agregore workflow
    - how would you get upstream data to downstream users without app/content separation
    - right now this is only good for completed apps that arent getting updates
    - one of the benefits of centralization is the ability to keep updating app and other people are forced to use the most updated version
- you could have a button that updates it sort of like apps with very visible update buttons
    - presentation is separate from content
    - how would u deal with the app changing the expected structure of the data

 