21
Doggos [M] 21 points ago +21 / -0

Not a DDoS in this case. A hosting provider's system incorrectly detected traffic coming from our reverse proxy (which is all the traffic) as a DDoS attack and blocked the traffic, because they're stupid.

60% of visitors were impacted. Resolved for now.

5
Doggos [M] 5 points ago +5 / -0

Yep, we were just deploying a small update.

11
Doggos [M] 11 points ago +11 / -0

Fixed earlier today, although the update is not deployed: https://communities.win/p/GbtZ07xz/fix-for-comment-score-breakdown-/

We were aware of the issue before putting it live, however it was necessary in order to deploy this update: https://communities.win/p/GbtUSp0C/comment-rendering-loop-1180/

37
Doggos [M] 37 points ago +39 / -2

Volunteers, entirely funded by longtime moderators.

2
Doggos [M] 2 points ago +2 / -0

Sure, certainly some, but we've seen consistent growth this whole time.

Our daily active users has, I believe, actually close to tripled from after the dust had settled after we first committed to Win in late February.

1016
Doggos [M] 1016 points ago +1016 / -0

And no, we still don't want your money.


Again: moderators of existing communities who believe that they're no longer welcome on their current platforms, we have a huge backlog that we're working through, but do contact us if you haven't already: [email protected]

3
Doggos 3 points ago +3 / -0

Epik for domains.

BuyVM and OVH for hosting. Win doesn't use these hosts.

Ultimately, the host doesn't matter as long as your host doesn't know they're hosting you. Get behind Cloudflare (or another CDN) as well as your own reverse proxy, such as HAProxy.

4
Doggos [M] 4 points ago +4 / -0 (edited)

Very odd. I have replicated this issue.

Looking into it.

update: fixed 07/25/20

43
Doggos [M] 43 points ago +43 / -0

Settings were changed, and services that hadn't been rebooted in 4 months were rebooted, as part of the downtime on the 20th. This caused a process scheduled to run on the hour to fail, which is when the sites went down.

60
Doggos [M] 60 points ago +60 / -0

It wasn't intentional - if we ever have to take the site down, it's during the middle of the night.

1041
Doggos 1041 points ago +1047 / -6

You can dislike QAnon as much as you like, but this is nothing more than QAnon being used as a scapegoat for yet more censorship of Trump supporters. Even in the best case, where Twitter has the most sincere of intentions, the AI knows no difference. The overlap is too large.

They also said that they will:

  1. No longer serve content and accounts associated with QAnon in Trends and recommendations
  2. Work to ensure we're not highlighting this activity in search and conversations
  3. Block URLs associated with QAnon from being shared on Twitter

You can bet that by trends, they mean anything pro-Trump. By URLs, anything in support of Trump - probably also The Donald, despite the fact that we are not a QAnon forum.

30
Doggos [M] 30 points ago +30 / -0

They reverted the censorship; we're back on.

It wouldn't impact us nearly as much as it would media outlets. We've had around 500K clicks from Google in the past 3 months, compared to 123,000,000 pageviews last month.

Around half of our Google clicks were on variants of "the donald win", the other half on random keywords such as "hells angels mongols seattle antifa" (which received 150K impressions, 5K clicks)

17
Doggos [M] 17 points ago +17 / -0

compromised my account password.

Approximately a third of users were unable to login.

Just clarify that there were no security issues.

4
Doggos [M] 4 points ago +4 / -0

Approximately a third of users had this issue.

6
Doggos [M] 6 points ago +8 / -2 (edited)

Two times in two weeks, I've accidentally stickied a comment that's a reply to another comment. Noticed by the quantity of upvotes.

Unstickied. Always awkward.

18
Doggos [M] 18 points ago +19 / -1

Considered it a little, such as for if we ever had a general politics community. To work correctly, that'd need a new sorting logic which surfaces content that either is split right down the middle, or leans to one side heavily.

It's possible that we'd add a new sort type alongside hot/new/rising/top for this.

41
Doggos [M] 41 points ago +44 / -3

Unlikely to happen, I think that'd dissuade people from participating. It's just generally too fundamental of a change... although I like the idea on the surface.

What we could do is give some non-identifying stats such as average account age, average karma, etc - then it'd at least be possible to spot posts that were upvoted or downvoted by a bunch of inactive bot accounts?

794
Doggos [M] 794 points ago +804 / -10

I was considering make a post about it here, rather than just on communities.win (all changes are posted there, while the important few are reposted here), but this is a good substitute.

A post linked here earlier today made a good point when speaking about the downfall of that other social media site:

We now have an entirely new way to view upvote/downvote scores. A user on Reddit used to be able to see their score. But now, everything is fuzzed. For example, if you made a semi-controversial comment before, but many people agreed, you may have a score like (47/45), leaving you with a -2 next to the comment. Now you just get a -2 and nobody knows if anyone agreed with you.

And for that reason, I made this change.

7
Doggos [M] 7 points ago +7 / -0

For sure. I remember when that was taken away.

I am a little hesistant to add that for posts, since we also currently limit posts to a minimum score of zero, and showing the up/down count isn't compatible with that.

For comments, we definitely should show the raw up/down count.

13
Doggos [M] 13 points ago +13 / -0

Reposting explanation of mine from other threads: keeping it vague to not disclose any of our hosts, but somewhere down the line, the DDoS protection of one of the hosts decided that our reverse proxy traffic was a DDoS attack (it was not), and temporarily blocked it, meaning no traffic was hitting our web servers. It's still blocked now, but I've switched the site over to bypass that.

The other Win sites are separated from The Donald in some ways for now (they're fully on a cloud service, testing them out with a Kubernetes cluster before having The Donald make that jump also - which is currently mostly dedicated) so they were not impacted.


Now specifically with regards to Cloudflare - enabling their "Under Attack" mode is typically the first thing that we do when we see that the site is either down or running slow. Hence that's what happened here, after which I began looking into what the problem actually was. In reality, this had nothing to do with a DDoS attack.

They do protect us against a lot of attacks that you never notice, and that you never have the captchas for. Normally when you get captchas, it's specifically because we requested that temporarily, all traffic gets captcha'd. We also have filters to captcha some users based on ASN, country, etc all the time. They rarely show captchas on their own accord.

We've looked at (and will continue to look at) BitMitigate as a longterm alternative. Main thing we need from them is ability to filter by ASN and country.

7
Doggos [M] 7 points ago +7 / -0

Reposting my explanation from other thread: keeping it vague to not disclose any of our hosts, but somewhere down the line, the DDoS protection of one of the hosts decided that our reverse proxy traffic was a DDoS attack (it was not), and temporarily blocked it, meaning no traffic was hitting our web servers. It's still blocked now, but I've switched the site over to bypass that.

The other Win sites are separated from The Donald in some ways for now (they're fully on a cloud service, testing them out with a Kubernetes cluster before having The Donald make that jump also - which is currently mostly dedicated) so they were not impacted.

view more: Next ›