Skip to content
This repository has been archived by the owner on Dec 6, 2019. It is now read-only.

Spam Issue :( #649

Closed
moonglum opened this issue May 18, 2016 · 2 comments
Closed

Spam Issue :( #649

moonglum opened this issue May 18, 2016 · 2 comments

Comments

@moonglum
Copy link
Member

We had a big spam attack last weekend. I think the best solution would be to deactivate comments. They are rarely used and not worth the struggle.

moonglum added a commit that referenced this issue May 29, 2016
* Remove all visible traces of comments
* Remove all traces of the comment functionality
@muescha
Copy link
Contributor

muescha commented Oct 24, 2016

Alternativ könnte man externe Kommentarfunktion nutzen:

Möglichkeiten:

  • disqus
  • facebook

Die Kommentar Funktion war meist für den Fall nützlich, wenn man Änderungen kommunizieren möchte die zwar auf der Homepage des Events zu sehen waren, aber noch nicht auf hacken geändert wurde. Meistens fällt einem sowas am selben Tag auf.

moonglum added a commit that referenced this issue Nov 13, 2016
* Move Vagrant + puppet into a subfolder (prepare for #621)
* Re-Add Uberspace infrastructure Scripts (#635)
  * Deduplicate port + write .htaccess on demand.
* Switch to Ruby 2.2.4 (#650)
* Faster VMWare Fusion Box
* Bump VirtualBox-Box-size (refs ce4da7a)
* Fix Event Page: Use the correct partial (#651)
* Read REVISION and add it to the <header> + Warning
  (refs #621)
* #649: Remove comments (#652)
* Remove all visible traces of comments
* Remove all traces of the comment functionality
@moonglum
Copy link
Member Author

Removed the comments feature.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants