# Ongoing Holochain Worldwide Student Developer Zoom

## April 9th, 2020

### Agenda

- has everyone seen the Holochain playground that Guillem has made? https://forum.holochain.org/t/introducing-the-holochain-playground/2652/18
- discuss merging this call with the Hackalong https://forum.holochain.org/t/introducing-the-holochain-virtual-hackalong/2574
- UPD: it's been decided to merge this call into the Hackalong

## April 2nd, 2020

### Agenda

- Nastasia: clarify if we can actually rely on links vec storing latest link in the end of the vector (that's the assumption used to write PR for Leap)
- Jim: clarify how the backups are supposed to be handled with Holoports

## Checkins

## Topics
- Sid: are these call still relevant given we have the HackAlongs?

## March 26th, 2020
*Present in the call (self check-in here):
Nastasia, Nicolas, Jim, OGU, Phy, Carolyn, Sid

### Implicit vs explicit links

Key question to decide which to use:
- how often it's going to be updated
- updating explicit link would create new holochain entry for link
- implicit link update can be done with the entry update and won't require additional operation
- how hard it is to update

#### Explicit

pros:
- handled by holochain

cons:
- creates another holochain entry to store the link data (so adds overhead on storage)

### Implicit

storing an address of another entry as part of one entry's contents

pros:
- consumes less resources

cons:
- updates and everything else has to be handled manually by an app developer (as opposed to this being already handled by the Holochain)

### Holoports
- Jim - how safe is it to get a service (say image storage) from a single holo provider / Holoport ?
- What happens if the Holoport goes down
- if there's a single holoport used by small community, how to make this community's data more resilient

### Check-ins
### Topics
### Action points

-------------

## March 19th, 2020
*Present in the call (self check-in here): Carolyn, Jim, Hedayat, Sid, Nicolas, Dylan, Alex, Guillem, Rose, Martin, Phy*

### Agenda
- Check-ins / Updates
- Challenges / blockers

### Check-ins
**Nicolas**:
- an SSB/Holochain conversation will happen on: 19 March, 20.00 CET at this link https://zoom.us/j/348374030
- wrote down some [thoughs about the future of personas](https://forum.holochain.org/t/draft-beyond-identity-management-rethinking-the-purpose-of-personas/2484) looking for reactions on the concepts before I dig some of the technical aspects
**Sid** have been working closely with pospi on reputation modules for Sacred Capital that can be reused in other hApps.
**Alex** Started a relationship app, studying more concepts
**Guillem** Virtual Hackalong coming up.

### Topics

- (Sid) Relation between identities and reputation might be worth exploring
- (Dylan Massel) Acorn to integrate the Personas/identity manager
- (Guillem) A place (among many) for some reusable holochain compnents: https://github.com/holochain-open-dev
- (Uwe) How can we find ways to put people in teams that last accross calls?
- (Carolyn) We can use the Holo Zoom community plan for organising topic conversations
- (Sid) Trying to push Holochain in Asia with Bear, looking for contacts in these areas.

### Action points
Nicolas to contact Sid (re. identities vs. reputation links and expanding Holochain in Asia/Taiwan)

-------------

## 12th March 2020

### call agenda

Event: conversation SSB/Holochain planned March 19th.

**Pospi**: I started working on some group related functionality which I think will turn into a fully featured group agent implementation fairly quickly https://github.com/holochain-open-dev/agent-registration

Nastasia to present the changes of her pull request in Leap (see [PR on Github](https://github.com/holochain-devcamp/learning-pathways/pull/5).

There's not much there yet though, it's mostly there to proof a setup where it links to Guillem's "social triangulation" zome in order to build a permissioned group DNA.

**Phil** https://blooniverse.com/Content/Dev/Media/Blooms/

#### Questions:
* (from Hedayat) Should we think further than repeating old patterns of communications to Holochain. E.g. for a chatting hApp, are there other considerations we should take to define the user interface? Maybe some mechanism to synchronise two users when they are both connected, etc...
* Status of LeaP?
Still thinking about the proposed solution in Nastasia's PR.

* How to work on/approach such a complex app like Holo-REA

* Ember Adapter?

## 5th March 2020

### call agenda

* Jim makes a demo of his chat app that he wants to integrate with Holohain
* Nastasia(f00bar42) makes a brief walk-through for the code she has for this [LeaP issue](https://github.com/holochain-devcamp/learning-pathways/issues/4)
* Nicolas to mention SSB/Holochain conversation hosted by Viktor https://doodle.com/poll/yrw6ng3pscmkkkqy

### Regarding Nastasia's persentation

Holochain is a CRDT(Conflict-free replicated data type) = a data management system that should deal with entries in an idempotent way.
Global order of events should not matter to get a result.
The way thigs were done in the devcamp is erroneous (see issue #4 link above). E.g. network synchronisation could change the order of events.
Nastasia presented a model about how to deal with updating entries in Leap.

The scheme of how Course entry would be split into 2 different entries (CourseAnchor and CourseData):

Previous related notes from Guillem: https://hackmd.io/pw46p7sQT426ECMhPUChcQ?both
Guillem talking about Content addressable stores and how things work in Holochain.
Larger discussion follows about ways to identify things in decentralised technologies.

### Jim's demo
He'd like some feedback and advice on how to convert the current design to Holochain.
Still want to keep Odoo as part of the tech stack, which means it has to be "wired" to holochain through Holo.
Main concern to maintain privacy of users.

Unrelated mention from Jim: [secret shares](https://pypi.org/project/secretshare/), a way to recover data by having few portions of the overall segmentation of a file.

thread on forum related to that:
https://forum.holochain.org/t/where-are-private-keys-and-data-stored-if-youre-using-holo-host/1081/7

will only work once Holo goes online, but very useful for the context on the key management:
https://github.com/Holo-Host/chaperone-key-manager

### technical issues discussed

* building REST-like protocols with Holochain. Guillem mentioned a forum thread about that, this is still an open question.
* https://forum.holochain.org/t/standardised-common-zome-traits/1642/12
* https://forum.holochain.org/t/mixin-zome-and-utility-libraries-for-restful-apis-and-uri-resolvers/2071

* Holochain file storage is very slow now, as Guillem mentioned, it's code is located here:
https://github.com/eyss/holochain_file_storage

-------------

## 27th Feb 2020

### next week agenda

Jim would make a demo of the chat app that he wants to integrate with the Holochain

### technical issues discussed

* unclear how to do management of multiple DHTs from frontend
steps to follow-up:
- check Holo-REA code because they already implement this scheme
* personas are not in the production ready state and this is a blocker for people who want to build apps relying on authentication
steps to follow-up:
- get in touch with a core team member
- possibly make a forum post about the issue
* personas discovery & presence: it's unclear how to implement mechanism of discovering different people present in the network
steps to follow-up:
- unclear (please correct me here)
* how to do staging deployment for a holochain app? (this isn't possible yet as Guillem said)

More information on personas:
- project description & ideas & architecture: https://hackmd.io/pcDkiCJoQH-z6s_VS4LNRg
- one of git repos: https://github.com/Holo-Host/holo-communities-dna

### agreements reached

#### time

It's been communicated that UTC 12:00 is ok for the people who made it to the call so this time slot is here to stay for now

#### PoC workflow

Since we'll be learning about different Holochain functionality, we'll be making PoC projects to start with something. These PoCs would be best done as pull requests for the LeaP app because everyone is already familiar with it's structure. These PoCs could be submitted as pull requests into the main LeaP repository and then the author could make a walk through about the ideas implemented.

### Leap refactoring

Hedayat & Guillem said that there's currently a bug in the way we update entries in LeaP app and this needs to be refactored.

UPD: there's now an issue about this: https://github.com/holochain-devcamp/learning-pathways/issues/4
TODO: more details here are needed
TODO: this announcement should happen in a broader context, not only in relation to regular studying calls