Difference between revisions of "Twitter"
(→Official Accounts) |
|||
| Line 7: | Line 7: | ||
The founders learned through experience at LiveJournal that if the process to update an offsite status page is too much of a pain (in whatever way) it won't happen, making the status page basically useless. Why Twitter? It's got decent uptime, it's free, it's a heavily used platform, and it's not necessary to have an account or specific mobile app to look at the updates. | The founders learned through experience at LiveJournal that if the process to update an offsite status page is too much of a pain (in whatever way) it won't happen, making the status page basically useless. Why Twitter? It's got decent uptime, it's free, it's a heavily used platform, and it's not necessary to have an account or specific mobile app to look at the updates. | ||
| − | = | + | =Support via Twitter= |
| − | Some Dreamwidth users have historically provided unofficial technical support and customer service on Twitter. | + | Some Dreamwidth users have historically provided unofficial technical support and customer service on Twitter. Use discretion when contributing; don't be That Person barging into a conversation to be 'splainey. |
| + | |||
| + | The official account, or Denise through her personal account, may respond to @-mentions. However, there is no guarantee of customer service on Twitter; use [http://www.dreamwidth.org/support Support] instead. | ||
[http://twitter.com/#!/search/%23dreamwidth #dreamwidth hashtag] | [http://twitter.com/#!/search/%23dreamwidth #dreamwidth hashtag] | ||
| + | |||
| + | Any Support crew using [[Slack]] can join the #twitter channel, which alerts about public mentions of the @dreamwidth account. | ||
=Twitter Integration= | =Twitter Integration= | ||
Latest revision as of 22:28, 8 December 2017
Official Accounts
Dreamwidth has two official Twitter accounts.
- @dreamwidth. - Posts whenever there is some sort of downtime or risk of downtime (such as code pushes). Mainly operated by Denise.
- @dw_alerts - Is a direct feed of Nagios, the server monitoring bot that lives in IRC and pages Mark all the time. Useful for sysadmins.
The founders learned through experience at LiveJournal that if the process to update an offsite status page is too much of a pain (in whatever way) it won't happen, making the status page basically useless. Why Twitter? It's got decent uptime, it's free, it's a heavily used platform, and it's not necessary to have an account or specific mobile app to look at the updates.
Support via Twitter
Some Dreamwidth users have historically provided unofficial technical support and customer service on Twitter. Use discretion when contributing; don't be That Person barging into a conversation to be 'splainey.
The official account, or Denise through her personal account, may respond to @-mentions. However, there is no guarantee of customer service on Twitter; use Support instead.
Any Support crew using Slack can join the #twitter channel, which alerts about public mentions of the @dreamwidth account.
Twitter Integration
- At this point in time, Twitter users cannot sign in to Dreamwidth with OAuth.
- One can arrange for a service to import one's tweets. There is no official service endorsed by Dreamwidth that does this, but there are a number of services users have used to some satisfaction. Some users use self-hosted custom scripts.
- Twitter-import services post to one's journal using one of the following authentication methods:
- One's password
- A hash of one's password
- Post-by-email (most secure)
- Paid users may set up subscription filters that exclude certain tags of specific users from default display on the reading page -- such as a user who imports Twitter, and has a tag that they use for all such imported entries.
