{"action":"created","issue":{"url":"https://api.github.com/repos/Lapin0t/py-swirld/issues/1","repository_url":"https://api.github.com/repos/Lapin0t/py-swirld","labels_url":"https://api.github.com/repos/Lapin0t/py-swirld/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/Lapin0t/py-swirld/issues/1/comments","events_url":"https://api.github.com/repos/Lapin0t/py-swirld/issues/1/events","html_url":"https://github.com/Lapin0t/py-swirld/issues/1","id":178912085,"number":1,"title":"ask_sync equivalent in ipfs branch","user":{"login":"buhrmi","id":51177,"avatar_url":"https://avatars.githubusercontent.com/u/51177?v=3","gravatar_id":"","url":"https://api.github.com/users/buhrmi","html_url":"https://github.com/buhrmi","followers_url":"https://api.github.com/users/buhrmi/followers","following_url":"https://api.github.com/users/buhrmi/following{/other_user}","gists_url":"https://api.github.com/users/buhrmi/gists{/gist_id}","starred_url":"https://api.github.com/users/buhrmi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/buhrmi/subscriptions","organizations_url":"https://api.github.com/users/buhrmi/orgs","repos_url":"https://api.github.com/users/buhrmi/repos","events_url":"https://api.github.com/users/buhrmi/events{/privacy}","received_events_url":"https://api.github.com/users/buhrmi/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2016-09-23T15:52:26Z","updated_at":"2016-09-25T15:03:13Z","closed_at":null,"body":"Hi,\r\n\r\nI'm quite intrigued by your implementation using IPFS. But I don't understand how another node on the Network is notified about new events when using IPFS. In the master branch it seems that the `ask_sync` method takes care of this. How would this work with IPFS? Maybe I just don't see it.\r\n\r\nStefan"},"comment":{"url":"https://api.github.com/repos/Lapin0t/py-swirld/issues/comments/249426643","html_url":"https://github.com/Lapin0t/py-swirld/issues/1#issuecomment-249426643","issue_url":"https://api.github.com/repos/Lapin0t/py-swirld/issues/1","id":249426643,"user":{"login":"Lapin0t","id":9576584,"avatar_url":"https://avatars.githubusercontent.com/u/9576584?v=3","gravatar_id":"","url":"https://api.github.com/users/Lapin0t","html_url":"https://github.com/Lapin0t","followers_url":"https://api.github.com/users/Lapin0t/followers","following_url":"https://api.github.com/users/Lapin0t/following{/other_user}","gists_url":"https://api.github.com/users/Lapin0t/gists{/gist_id}","starred_url":"https://api.github.com/users/Lapin0t/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Lapin0t/subscriptions","organizations_url":"https://api.github.com/users/Lapin0t/orgs","repos_url":"https://api.github.com/users/Lapin0t/repos","events_url":"https://api.github.com/users/Lapin0t/events{/privacy}","received_events_url":"https://api.github.com/users/Lapin0t/received_events","type":"User","site_admin":false},"created_at":"2016-09-25T15:03:13Z","updated_at":"2016-09-25T15:03:13Z","body":"Notified of what? The idea of swirld is to pick a random node, get his head event and all the events we don't know about and make a new head whose parents are our old head and the head of the remote node. The remote events we don't know about (including the head of the remote node) can be queried by using an rpc (`ask_sync`) or by using the ipns references (`get_head`) but it is exactely the same behavior. A node sends his local events only if someone asks for them, he never actively notifies the other nodes."}}
{"actor":{"display_login":"Lapin0t"}}