-
Notifications
You must be signed in to change notification settings - Fork 309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC] Maskbook Twitter payload specification #373
Comments
I do like #InMaskWeBook but this meme is not good.. We might use #Maskbook_com or #Maskbookcom |
Got some great feed back from Cole
Still, using URL is sensitive . maybe we can do
|
Also what if we just use #Maskbook ? I dont have any strong preference -- so lets consider just use #Maskbook and go ahead |
Checkout https://twitter.com/suji_yan/status/1194603986726162432 I guess we can do URLs as well
|
The time is passed - recommend lets put the URL back:
Is prob the best for now @neruthes for inmaskwebook -- too much meme... |
We may replicate the way employed by Blizzard for Lenassa and Zer'atai. |
This RFC should go into finalization when #397 needs. |
I need this to be delivered b4 #397 and by this Friday. The only thing we need is |
Your advice should have been satisfied in the Conclusion section. |
Metadata
Abstract
Dependencies
Glossary
Principles
Format
Base
Alternatives
The Choice: ☯️
While #Maskbook is the hashtag we ultimately want to advocate for, #InMaskWeBook is an irresistibly nice meme. We will use both, randomly selecting one upon posting.
Notes
The text was updated successfully, but these errors were encountered: