forked from OpenUserJS/OpenUserJS.org
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Applies to OpenUserJS#116
- Loading branch information
Martii
committed
Jun 6, 2014
1 parent
5478e27
commit 6599461
Showing
1 changed file
with
1 addition
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6599461
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sizzlemctwizzle,
This work for everyone including you? If anyone sends an email without the required information you have every right to dismiss a claim and just reply with a link to the DMCA... preferably on the OUJS site itself... which needs to have some room made for it somewhere soon along with the TOS and Privacy policy linkage/pages. It would be nice just to read the .md files into a template for those links so management can be handled easily with GH too... but still include the standard head/header/footer and default document stuff. (this applies for the work that @Zren is doing too please)
Also if any mitigation service or site emails or pms (assuming they get a hold of this info) another admin, moderator, or even a user, etc... they are to reply only with the specified url to the DMCA and nothing more... no signature, no explanations, etc. We might want to develop a "mass admin" mailing/pm'ing outlining steps to "vote" on a decision or you can just decide on your own... but this can be down the line.
6599461
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works for me.
Got it.
I'm pretty sure all the files in the repo, including this one are present on the production deployment. I could just read them from disk and pass them through the markdown renderer and dump the output into a template. But we need the links in the footer.
Yeah an on-site system to let admins make decisions on this stuff is probably what we what in the long run, but this should work for now.