by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 03:15
    zelig commented #2193
  • 03:15
    zelig commented #2193
  • May 27 16:03

    mortelli on global-pinning-test

    prod, storage: iterate logs and… (compare)

  • May 27 16:03

    mortelli on global-pinning-test

    prod, storage: iterate logs and… (compare)

  • May 27 14:29

    santicomp2014 on global-pinning-test

    prod: added log for getFeedCont… (compare)

  • May 27 14:29

    santicomp2014 on global-pinning-test

    prod: added log for getFeedCont… (compare)

  • May 26 21:28

    santicomp2014 on global-pinning-test

    prod,storage: force recoveryCal… (compare)

  • May 26 21:28

    santicomp2014 on global-pinning-test

    prod,storage: force recoveryCal… (compare)

  • May 26 20:44

    santicomp2014 on global-pinning-test

    api/http,network/retrieval,stor… (compare)

  • May 26 20:44

    santicomp2014 on global-pinning-test

    api/http,network/retrieval,stor… (compare)

  • May 26 20:06

    santicomp2014 on global-pinning-test

    chunk, feed, storage, feed: con… Merge branch 'global-pinning' i… main, swarm, http, prod, api, c… and 6 more (compare)

  • May 26 20:06

    santicomp2014 on global-pinning-test

    chunk, feed, storage, feed: con… Merge branch 'global-pinning' i… main, swarm, http, prod, api, c… and 6 more (compare)

  • May 26 20:03

    mortelli on local-pinning-test

    (compare)

  • May 26 20:03

    mortelli on local-pinning-test

    (compare)

  • May 26 19:52
    Eknir commented #2195
  • May 26 19:52
    Eknir commented #2195
  • May 26 19:30
    mortelli commented #2173
  • May 26 19:30
    mortelli commented #2173
  • May 26 19:30
    mortelli commented #2173
  • May 26 19:30
    mortelli commented #2173
swarm team
@ethswarm_gitlab
[mattermost] <jmozah> The issue with "GetAllReferences" is that it needs the original file as argument and it recalculates the chunks hashes..
[mattermost] <jmozah> Our scenario is.. browser has uploaded a file.. so we don't have the actual file
[mattermost] <jmozah> What i want instead is .... GIven a root hash.. print the chunk merkel tree
[mattermost] <jmozah> and aginst each chunk.. say if it is present locally or not..
[mattermost] <jmozah> @holisticode ^^
[mattermost] <holisticode> got it @jmozah, different use case
[mattermost] <holisticode> I suggest you open an issue for that, even if you or someone on your team may want to implement it
[mattermost] <jmozah> yeah.. will do that
swarm team
@ethswarm_gitlab
[mattermost] <holisticode> thanks!
swarm team
@ethswarm_gitlab
[mattermost] <jmozah> ethersphere/swarm#1501
swarm team
@ethswarm_gitlab
[mattermost] <cagehodit> I deleted everything. I'll try the next version.
swarm team
@ethswarm_gitlab
[mattermost] <jmozah> Why is there two "mw.AddEntry()" in this function. One in line 697 and another in line 716. They both seem to do add the same entry twice. https://github.com/ethersphere/swarm/blob/master/api/api.go#L697
[mattermost] <jmozah> ethersphere/swarm#1501
swarm team
@ethswarm_gitlab
[mattermost] <acud> one is for the actual entry and the second one is for the default entry
swarm team
@ethswarm_gitlab
[mattermost] <jmozah> You mean the top level entries[]? I don’t think so. The first one stores the actual file and creates a manifestEntry. The second one just creates a manifestEntry with the file hash.. the second one looks dubious to me. may be i’am missing something...
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.