Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 10:17

    vandot on v0.5.8

    (compare)

  • 10:17

    vandot on v0.5.8

    (compare)

  • Jan 15 10:21

    significance on master

    Deprecation notice (#2217) add… (compare)

  • Jan 15 10:21

    significance on master

    Deprecation notice (#2217) add… (compare)

  • Jan 15 10:21
    significance closed #2217
  • Jan 15 10:21
    significance closed #2217
  • Jan 14 12:05
    significance synchronize #2217
  • Jan 14 12:05
    significance synchronize #2217
  • Jan 14 12:05

    significance on deprecation-notice

    improve readme (compare)

  • Jan 14 12:05

    significance on deprecation-notice

    improve readme (compare)

  • Jan 14 11:30
    significance synchronize #2217
  • Jan 14 11:30
    significance synchronize #2217
  • Jan 14 11:30

    significance on deprecation-notice

    improve readme (compare)

  • Jan 14 11:30

    significance on deprecation-notice

    improve readme (compare)

  • Jan 14 11:22
    crtahlin commented #2218
  • Jan 14 11:22
    crtahlin commented #2218
  • Jan 14 11:12
    significance synchronize #2217
  • Jan 14 11:12
    significance synchronize #2217
  • Jan 14 11:12

    significance on deprecation-notice

    add deprecation notice to readme (compare)

  • Jan 14 11:12

    significance on deprecation-notice

    add deprecation notice to readme (compare)

swarm team
@ethswarm_gitlab
[mattermost] <jmozah> My next blog on Swarm is ready... I talk about DPA here..
[mattermost] <jmozah> I would be happy if someone from Swarm team can review for technical correctness
swarm team
@ethswarm_gitlab
[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 👍
swarm team
@ethswarm_gitlab
[mattermost] <jmozah> Is "swarm up --recursive" command is deprecated?
[mattermost] <jmozah> tarring a directory and then uploading looks very unconvenient
swarm team
@ethswarm_gitlab
[mattermost] <acud> I think its swarm —recursive up
swarm team
@ethswarm_gitlab
[mattermost] <agazso> I think this PR can be closed:
[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
swarm team
@ethswarm_gitlab
[mattermost] <acud> cool. thanks @agazso
swarm team
@ethswarm_gitlab
[mattermost] <eknir> Very informative. Thank you
swarm team
@ethswarm_gitlab
[mattermost] <agazso> I wrote a blogpost about the brainstorming and some ideas we had on the Swarm Hack Week
timotheus
@FantasticoFox
General notification: We moved away from Gitter this is therefore a legacy channel. Please use the msttermost behive for communication.
swarm team
@ethswarm_gitlab
[mattermost] <jmozah> Is there any other Swarm client implementation (other than go) that is in the working?
[mattermost] <jmozah> I know that there is a really old Swarm in ethereumJ...
Jacek Sieka
@arnetheduck
we (status) are planning one
Zahoor Mohamed
@jmozah
in Java?
Jacek Sieka
@arnetheduck
nim
swarm team
@ethswarm_gitlab
[mattermost] <jmozah> Is there any github repo that i can look in to?
[mattermost] <jmozah> WIll that be a light client or a full node?
Jacek Sieka
@arnetheduck
not yet, though it'll be based on stuff from nimbus: https://nimbus.status.im/ - initially a light/adaptive client, then we'll see
swarm team
@ethswarm_gitlab
[mattermost] <jmozah> Awesome
Rafael Matias
@skylenet
@/all swarm 0.4.3 has been released. you can read the changelog at https://github.com/ethersphere/swarm/blob/master/CHANGELOG.md
swarm team
@ethswarm_gitlab
[mattermost] <lash> We need a convention for pseudo descriptions of protocol data types in the swarm specifications that unambiguously map to RLP serializations. I've outlined a suggestion on how to approach this. Perhaps we can discuss?
Nick Savers
@nicksavers
Has anybody done an analysis of https://www.arweave.org/ yet?
swarm team
@ethswarm_gitlab
[mattermost] <aron> never heard of them.
[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
swarm team
@ethswarm_gitlab
[mattermost] <aron> @nicksavers - I will meet with the Arweave guys in Berlin: https://www.eventbrite.com/e/decentralised-storage-summit-tickets-62719912948
Nick Savers
@nicksavers
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.
KayKuteeKayEtherMining
@KaycoinsInc
Hiya everyone! Glad to be part of the group!
Swarm Beta is around the corner! ^^^
ldeffenb
@ldeffenb
1 week and counting...
Ryan Ghods
@ryanio
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
ldeffenb
@ldeffenb
@ryanio Just FYI, the new swarm client is called "bee". You might raise them faster at https://beehive.ethswarm.org/swarm/channels/town-square
Ryan Ghods
@ryanio
@ldeffenb ah thank you, do you mind cross posting my message over there? i don’t have a mattermost account
Rinke Hendriksen
@Eknir
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
Ryan Ghods
@ryanio
@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
Rinke Hendriksen
@Eknir
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!
f1l1b0x
@f1l1b0x
hi guys
seeing you want to stream with livepeer today do you have everything set and running?
happy to help