Wasmer and Trademarks
wasmer.io
Wasmer and Trademarks
1–10 of 81 posts
Re: Wasmer and Trademarks
#2No post body was provided.
Re: Wasmer and Trademarks
#3For anyone curious about Bytecode Alliance: https://github.com/wasmerio/wasmer/issues/956
Re: Wasmer and Trademarks
#4For anyone curious about Bytecode Alliance: https://github.com/wasmerio/wasmer/issues/956
> Unless the BA members have future-reading abilities (which perhaps they have, who knows!), that narrative is hard to hold @showyourfaces.
I think it was similar but far more mundane. I think they got bad vibes from Wasmer.
Re: Wasmer and Trademarks
#5Amazing levels of transparency in this statement, which feels like a breath of fresh air to read in terms of clarity and openness. Will have to check out Wasmer :)
Re: Wasmer and Trademarks
#6> If we had had bad intentions at that moment we could have still pursued the trademark at that time. Instead, we left the process to expire, leading to this official response from USPTO in September of the same year: https://uspto.report/TM/88703780 “Status: Abandoned because the applicant failed to respond”.
The actual rejection: https://uspto.report/TM/88703784/OOA20200227112123#2
> The attached evidence from Webassembly and Wikipedia shows that WASM is a programming language. Here, applicant provides various software, which presumably involves the use of the aforementioned programming language.
> In total, the above evidence results in the determination that in relation to the goods and/or services applicant provides, the context therefor, and to someone who knows what the goods and/or services are, WASM conveys an immediate idea about a feature or characteristic of applicant’s goods and/or services, namely, that they consist of software involving the programming language WASM. Accordingly, the proposed mark, WASM is merely descriptive and registration is properly refused on the Principal Register under Section 2(e)(1).
> Although applicant’s mark has been refused registration, applicant may respond to the refusal by submitting evidence and arguments in support of registration. If applicant responds to the refusal, applicant must also respond to the requirements set forth below.
Re: Wasmer and Trademarks
#7> Wasmer, by necessity, design, and passion lives and breathes Wasm and open source.
> As is dictated by our commitment to open source and the precedent of social alignment set by WebAssembly...
> Although all these events still do not portray Wasmer in the best light, I hope they can at least assuage the understandable concerns of our community that we had acted in a way so fundamentally contrary to the values of open source and WebAssembly in particular.
Wasmer recently recently released a closed source wasm package manager. Something doesn't seem right. Anyone feel something is off here?
Re: Wasmer and Trademarks
#8> Wasmer, by necessity, design, and passion lives and breathes Wasm and open source. > As is dictated by our commitment to open source and the precedent of social alignment set by WebAssembly... > Although all these events still do not portray Wasmer in the best light, I hope they can at least assuage the understandable concerns of our community that we had acted in a way so fundamentally contrary to the values of op…
The WAPM backend is closed-source for now.
However, the API layer based on GraphQL and the CLI are completely open for anyone to use: https://registry.wapm.io/graphql https://github.com/wasmerio/wapm-cli
If anyone wants to replicate the WebAssembly Package Manager locally please send me an email to syrus@wasmer.io so we can start a discussion around a potential open-source path for it :)
EDIT: removed "for security reasons among other things" as it might imply WAPM is not secure, and that's definitely not the case
Re: Wasmer and Trademarks
#9> Wasmer, by necessity, design, and passion lives and breathes Wasm and open source. > As is dictated by our commitment to open source and the precedent of social alignment set by WebAssembly... > Although all these events still do not portray Wasmer in the best light, I hope they can at least assuage the understandable concerns of our community that we had acted in a way so fundamentally contrary to the values of op…
The WAPM backend is closed-source for now. However, the API layer based on GraphQL and the CLI are completely open for anyone to use: https://registry.wapm.io/graphql https://github.com/wasmerio/wapm-cli If anyone wants to replicate the WebAssembly Package Manager locally please send me an email to syrus@wasmer.io so we can start a discussion around a potential open-source path for it :) EDIT: removed "for security r…
Closed source for security reasons?
Do you mean it would not be secure if people were able to see the source?
Re: Wasmer and Trademarks
#10> Wasmer, by necessity, design, and passion lives and breathes Wasm and open source. > As is dictated by our commitment to open source and the precedent of social alignment set by WebAssembly... > Although all these events still do not portray Wasmer in the best light, I hope they can at least assuage the understandable concerns of our community that we had acted in a way so fundamentally contrary to the values of op…
There is nothing[0] suspicious[1] about[2] Wasmer.
[0] https://news.ycombinator.com/item?id=28772863
[1] https://www.reddit.com/r/programming/comments/o1838v/the_web...