Mark Smith (
mark) wrote in
dw_maintenance2016-12-26 04:20 am
![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Nginx has been banished!
Hey all,
Sorry for the 'Welcome to nginx!' issues we've been seeing for a bit now. It was a server configuration issue that hit us when a webserver rebooted.
Basically when the machine rebooted, nginx (software that can act as a web server) started up and then when Apache (the software Dreamwidth code uses for a web server) tried to start, it failed because nginx had already started and registered on the ports (the way web server software gets your requests).
Again, sorry for the site issues. Everything should be back to happy-times now, so let us know if you see any issues!
Sorry for the 'Welcome to nginx!' issues we've been seeing for a bit now. It was a server configuration issue that hit us when a webserver rebooted.
Basically when the machine rebooted, nginx (software that can act as a web server) started up and then when Apache (the software Dreamwidth code uses for a web server) tried to start, it failed because nginx had already started and registered on the ports (the way web server software gets your requests).
Again, sorry for the site issues. Everything should be back to happy-times now, so let us know if you see any issues!
no subject
no subject
Dreamwidth doesn't currently have the ability to directly import tweets; some people have various things on their own servers to make it work for them.
The most recent user discussion about the feature was from 2011: http://dw-suggestions.dreamwidth.org/528546.html
It seemed back in 2012 that it would be against the rules for Dreamwidth to archive tweets on users' behalf, and that's when the suggestion got rejected.
I don't think there's been any recent discussion on making it possible; I will defer to
Thoughts upon having looked at the current rules
II.B looks ... interesting ... as well. https://dev.twitter.com/overview/terms/policy#id13
II.C on the profile is more than Dreamwidth does for other connected services, but perhaps it could be in each journal entry: https://dev.twitter.com/overview/terms/policy#id14
https://about.twitter.com/en-gb/company/display-requirements seems relevant, and I'm not sure that Dreamwidth wants to enable retweet-from-Dreamwidth. I also don't know whether Dreamwidth wants to start having a conversation with Twitter about implementation.