Bug 35235 - Xamarin Forum Just Got Spam Bombed
Summary: Xamarin Forum Just Got Spam Bombed
Status: RESOLVED UPSTREAM
Alias: None
Product: Documentation
Classification: Xamarin
Component: Xamarin University Content ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Joseph Hill
URL:
Depends on:
Blocks:
 
Reported: 2015-10-24 05:33 UTC by David Strickland
Modified: 2015-10-25 17:23 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED UPSTREAM

Description David Strickland 2015-10-24 05:33:17 UTC
Not sure this is the place for it but it was my best guess for catagory. The Xamarin General Discussion Forms just got Spam Bombed by an escort service. Thought maybe a Bug report might get to someone that can fix it considering its a weekend.
Comment 1 David Strickland 2015-10-25 16:27:06 UTC
Looks like its all been cleared up. For this week anyway.
Comment 2 Joseph Hill 2015-10-25 17:23:07 UTC
The forums host has been made aware of the issue (again).  We also investigating some additional spam control techniques with expect will have an impact.

Regardless, going to resolve this as there is not an appropriate way to track this vendor relationship in here.