ethersphere orange lounge is the swarm engine room- board: https://github.com/orgs/ethersphere/projects/1; doc: http://swarm-guide.readthedocs.io; PRs: https://github.com/ethersphere/go-ethereum; rountable topics: https://hackmd.io/oj9_cT2KQimMdIPe_W_ejQ#
[mattermost] <jmozah> I would be happy if someone from Swarm team can review for technical correctness
[mattermost] <jmozah> https://medium.com/@zahoor/swarm-distributed-pre-image-archive-dpa-b13f5c683f0a
[mattermost] <acud> The dangling empty manifest comes from the manifest writer that actually persists also every intermediate manifest created while updating entries( ie creating a manifest with 100 entries would result in 101 manifests afaik). This is due to the fact the manifest is recalculated and stored after every update operation. Known design issue that will be taken care of when manifests are rewritten 👍
[mattermost] <jmozah> tarring a directory and then uploading looks very unconvenient
[mattermost] <agazso> ethersphere/swarm#900
[mattermost] <agazso> Reasons: As far as I know, Status no longer works on it and the guy who worked on it no longer works at Status
[mattermost] <agazso> also it was a solution when Swarm was in the go-ethereum repo
[mattermost] <agazso> And there will be a new solution (somewhat based on this) as part of the Adaptive node epic
[mattermost] <agazso> https://felfele.org/blog/swarmhackweek2019/
[mattermost] <jmozah> I know that there is a really old Swarm in ethereumJ...
[mattermost] <jmozah> WIll that be a light client or a full node?
not yet, though it'll be based on stuff from nimbus: https://nimbus.status.im/ - initially a light/adaptive client, then we'll see
@/all swarm 0.4.3 has been released. you can read the changelog at https://github.com/ethersphere/swarm/blob/master/CHANGELOG.md
[mattermost] <aron> at first glance, their lightpaper is a bit light on details. Do they have a whitepaper somewhere?
[mattermost] <aron> specifically I'd like to know more about their proof-of-access protocol
[mattermost] <aron> @nicksavers - I will meet with the Arweave guys in Berlin: https://www.eventbrite.com/e/decentralised-storage-summit-tickets-62719912948
Alright. Yeah I looked into it. It was indeed vague and there is not quite a consensus mechanism there. Seem more like a tangle style transaction validation. And I couldn't figure out how they prevented DDoS attacks or actually give the incentives to store the and serve the data.
Swarm Beta is around the corner! ^^^
some of the new maintainers of web3.js would like to know how to proceed with swarm's implementation in web3.js, if anyone from the swarm team would be able to chime in here with some input that would be great ethereum/web3.js#3691
@ryanio Just FYI, the new swarm client is called "bee". You might raise them faster at https://beehive.ethswarm.org/swarm/channels/town-square
Hi @ryanio , thanks for reaching out. We would be glad to pick up this collaboration again, especially since there have been many changes since the implementation was done last time. What about a meeting early next week with the relevant people (from both sides), to map out how to proceed?
Please reach out to me on rinke@ethswarm.org for meeting details
@Eknir sounds great :) I’m not currently working on web3.js anymore but chainsafe is, led by Greg. I saw “acud” posted in the github issue I linked above so hopefully you guys can start some communication there. Let me know if you’d like an invite link to chainsafe discord since that is usually where they are active
Hi all, a last reminder for the Swarm live event, tomorrow at 1400 CET. If you didn't register yet, please do so now here. See you all tomorrow!
seeing you want to stream with livepeer today do you have everything set and running?
happy to help