Closed wbt closed 3 years ago
This makes a pretty good argument for dropping bzz. Would love to see input from the swarm team... @ryanio do you know anyone there?
If we can't get a hold of them it might be worth doing a "last call" for a month or so before fully deprecating it.
cc: @frankiebee @spacesailor24
sorry I don't know anyone currently working on swarm but I will drop a message in their channel with a link to this issue.
hi there, swarm team member here.
swarm-js builds on top of the classic ethersphere/swarm
client which is no longer actively being maintained as we have been rewriting the whole project for the last nine months or so. The new client is being maintained at ethersphere/bee and there's an ongoing effort to build a javascript proxy around that in nodejs (still unannounced).
How can we further discuss this? we are reachable on mattermost.
Thanks!
Do you mind reaching out to our discord?
@GregTheGreek which discord would that be? I am not on the ethereum discord. The web3.js repo does not mention any discord channel, only gitter.
i'm getting an error invalid invite
Try this one https://discord.gg/cRc2Jh8
Update:
After discussions with the Swarm team we are removing bzz support #3746
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. If you believe this was a mistake, please comment.
Web3 depends on web3-bzz which depends on swarm-js, which depends on eth-lib which depends on servify. The latter three are by the same author, who clearly writes in the readmes for the first two that they are not being maintained. The latter has a versioning issue fixed over three years ago but which throws a warning when installing web3. We might consider forking or finding an alternative.
(npm 6.14.5; node 9.3.0; Windows 10)