-
Notifications
You must be signed in to change notification settings - Fork 11
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
Define a Nostr strategy for Bisq #291
Comments
ObjectivesThe main purpose is to get traders/investors to use Bisq in their day to day trading activity. Target AudienceOur target audience will be the people interested in buying nokyc bitcoi, the ones that wants to buy bitcoin anonymously and the ones that takes security important as far as trading is concerned. ToneAs far as I’m concerned, I think it should basically be in a way to invite them to use Bisq over other centralized exchanges. ThemeThe theme will be centered around buying bitcoin anonymously with security been put in place. Nostr EngagementThis we can use some zapvertising strategies like:
FollowWe should follow accounts of decentralized exchanges with related motives and other interested individuals that post notes about bitcoin related topics ZapsThe received zaps is used to keep me connected to the internet (to purchase data) and to zap notes with relevant points (mostly talking about no kyc, decentralized exchanges and other relevant Bitcoin notes). The benefit of sending zaps to us is that it let people visit Bisq profile on Nostr which lets them read about it and it has helped in gaining followers on Nostr as well. Post to shareI guess we can be sharing post that’ll draw users attention to read (e.g bounties, available offers on Bisq) and maybe have notes asking questions about the obstacles they’re facing when trying to use Bisq. Bounties posts can be like “Share your best experience using Bisq in the comment section for a 5k zap” and many more. Call to actionI believe “call to actions” should be used from time to time as we are focused on telling people about Bisq, so using “Get Started” or “Learn More” should be used on our notes from time to time. Frequency of postI’m currently doing one post per day which must later sim up to a minimum of 20posts in a month. TimingI post randomly but mostly in the morning before 12 noon (Nigeria Time). Nostr SearchNostr have custom tags options to browse through topics that interest its users. We can focus on the nokyc, decentralized, stacksats, bitcoin, BTC and many more talking about our motive to engage in the notes tagged. |
Because of the way Nostr works shared accounts are not a good idea. Bisq also tries not to have any "official" social media channels. So I suggest that contributors posting on Nostr have different accounts. They can include Bisq name and logo in it, but should add their own identifier. For example: Bisq_jayboi, Bisq_flix, Bisq_solomon... That way each contributor assumes responsability for their posts. This strategy worked well in Bitcointalk forums in the past. When a contributor leaves (for whatever reason) they can also recommend other Bisq accounts to try to pass on the torch and keep the followers that they have accumulated in the community. |
Some guidelines on how to do Nostr posts. It has been growing steadily and I think that this will become an important channel for Bisq. Try to keep notes simple! Some ideas for content: -FOSS: what it is and why it's important |
It would be good to define a Nostr Strategy for Bisq. That way contributors can use Nostr in a way that has been agreed / contributed to by the DAO.
Examples of what a Nostr Strategy for Bisq might include are:
@Jayboi23 would you be happy to work on this. I think it can be something presented as a GitHub comment that breaks down the above.
Might be worth doing some research into how Bisq Twitter is used, and also looking into how other bitcoin companies are using Nostr as part of their social media strategy.
Creating an agreed upon Nostr strategy is something you could claim additional compensation for.
The text was updated successfully, but these errors were encountered: