or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Syncing
xxxxxxxxxx
Ongoing Holochain Worldwide Student Developer Zoom
April 9th, 2020
Agenda
April 2nd, 2020
Agenda
Checkins
Topics
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:
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
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
Nicolas:
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
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.
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
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, 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.
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
steps to follow-up:
steps to follow-up:
steps to follow-up:
More information on personas:
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