Skip to content

Collaboration issues #1

@tallero

Description

@tallero

Given this project has been stalling for quite a number of years, it seems to have just been resurrected, it's still far from working, its design seems quite complicated, why not contributing to the already existing and working Ethereum Virtual Machine File System?

If the two projects have different scopes and this one doesn't intend to implement a classical file system with directories, links, files, a FUSE backend, as well as web browsing and cross-chain publishing, like the evmfs has already partially done, would the developers of this one like link to it to disambiguate and foster collaboration and reach?

I'll be glad to do the same on the other one. You know, because it seems like some form of bullying, considering this one appears on all search engine related queries and says it's supported by the foundation (so maybe its development gets funds, while I'm literally starving right now), while the evmfs doesn't appear at all while having had already over a dozen stable releases over the course of an year andi it's already used by many very very useful and breakthrough applications (such as the Ur, the Life and DogeOS user repository and application store, the Ethereum Virtual Machine OpenPGP key server, the Ethereum Virtual Machine contracts' source index, the decentralized uncensorable Twitter, etc.).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions