Website
Github
Forum
Wiki
Dev Mailing List (Indolering?)
Pool Op Mailing List (Indolering?)
Bitmessage: Dev/Security List
Alerts Bitmessage List: Outdated https://forum.namecoin.info/viewtopic.php?f=19&t=1524
Announcements Board on the Forum: Outdated https://forum.namecoin.info/viewforum.php?f=19
Bitcointalk:
- Vinced's thread https://bitcointalk.org/index.php?topic=6017 (we have no control over OP)
- News Thread https://bitcointalk.org/index.php?topic=236340.0
Twitter: Outdated (Khal, phelix)
Facebook: (Sudoquai)
Reddit: (?)
Tumblr Blog: (Indolering)
Google+ ???
IMHO we should clean this up and then make it a sticky thread or put it on the wiki/website.
What channels do we really need / want to use?
How to group audiences? Users, Miners, Developers?
In some cases it might be beneficial to have information (e.g. binaries and hashes) on different servers.
Namecoin Communication Channels
-
- Posts: 57
- Joined: Fri Apr 25, 2014 4:40 am
Re: Namecoin Communication Channels
I'm willing to take on the twitter account, I'm on there all day long most days.
NMC: NFhmGAqzRpZbGs3uCPPo7DJKuscuL4Aap2
id/mightbemike
id/mightbemike
Re: Namecoin Communication Channels
IMHO it is important that we get this sorted out. Indo even started a similar thread:
https://forum.namecoin.info/viewtopic.p ... ead#unread
If nobody objects I will clean out the offtopic posts above.
Edit: Done. Please stay on topic! Create new threads for other topics.
https://forum.namecoin.info/viewtopic.p ... ead#unread
If nobody objects I will clean out the offtopic posts above.
Edit: Done. Please stay on topic! Create new threads for other topics.
-
- Posts: 801
- Joined: Sun Aug 18, 2013 8:26 pm
- os: mac
Re: Namecoin Communication Channels
I say screw the forum announcement threads, I never use them. The older mailing lists are not working and the servers are flagged as spammy.
I will share the Hootsuite password with core devs, enabling them to post to Facebook, Twitter, and Google at once. I've already given Facebook admin privileges to Jeremy Rand and editor privileges to various community members.
The majority of the work comes from cross-posting, which is actually fairly rare. As long as we have admins for each platform, then they should manage themselves. Eventually, we will have a NEP and API documentation, but I was planning on switching to Vanilla forums and using it's embedded functionality to try and capture discussion in one system.
For announcements, we could have special tags on posts to Tumblr and have them replicated across social media and mailing lists. Then we would only need to post in one place.
- Website/blog (pull headlines from tumblr blog which all core-devs have access to)
- Github
- Forum
- Wiki
- Dev Mailing List (core-devs)
- Pool Op Alerts Mailing List (core-devs)
- Bitmessage: Dev/Security List (move to Retroshare ASAP)
- Social (Twitter, facebook, google+) core-devs via shared Hootsuite account, community members through native multi-user functions.
I will share the Hootsuite password with core devs, enabling them to post to Facebook, Twitter, and Google at once. I've already given Facebook admin privileges to Jeremy Rand and editor privileges to various community members.
The majority of the work comes from cross-posting, which is actually fairly rare. As long as we have admins for each platform, then they should manage themselves. Eventually, we will have a NEP and API documentation, but I was planning on switching to Vanilla forums and using it's embedded functionality to try and capture discussion in one system.
For announcements, we could have special tags on posts to Tumblr and have them replicated across social media and mailing lists. Then we would only need to post in one place.
DNS is much more than a key->value datastore.
-
- Posts: 801
- Joined: Sun Aug 18, 2013 8:26 pm
- os: mac
Re: Namecoin Communication Channels
It looks like there is a releases RSS feed:
https://github.com/namecoin/namecoin/releases.atom
Can you include a "what's new" blurb in the release itself? If so, I could code up something that would autopost to the blog, social media accounts, and the alerts mailing list. Then devs wouldn't need to leave Github at all.
I bet you could find something for the forum too.....
https://github.com/namecoin/namecoin/releases.atom
Can you include a "what's new" blurb in the release itself? If so, I could code up something that would autopost to the blog, social media accounts, and the alerts mailing list. Then devs wouldn't need to leave Github at all.
I bet you could find something for the forum too.....
DNS is much more than a key->value datastore.