231

To assist mobile users, this is a complete list of Win communities.

At this time, don't trust sites that claim to be affiliated, but are not listed here.

Version 1.1.9.0 (08/03/2020) adds a new test feature which allows moderators to provide context for posts.

In fast moving communities, it's sometimes hard to keep up with the meaning behind memes and other content.

We've added a new button for moderators where they can set a link which explains the topic.

For example, if the front page has memes about bears, that could be confusing if you haven't visited the community earlier in the day. It'd perhaps be useful for a "(context)" link beside the post author's username, which links you to the original post which explains the bear situation.

As a demonstration, I have set an example context for this post - which you can find beside my username.

Version 1.1.8.2 (08/02/2020) fixes an issue with the dynamically updating comment score breakdown.

1.1.7.2 began dynamically updating the comment score breakdown.

This incorrectly visually adjusts the comment score breakdown for all child comments, as well as the intended target comment.

Update by Trinadin.

Version 1.1.8.0 (08/01/2020) fixes a significant issue that we came across today.

When you create a comment, a database entry is inserted and an incremental ID is assigned. That entry is then immediately edited based on the ID for the purposes of comment nesting.

In the event that this fails - which it didn't even once in the first almost four million comments, the comment will be interpreted as both the parent and the child of every other comment.

This means that when you load a post, the comment section will be in a loop - it will render the same comments endlessly.

Since this is rendered on the server side, it's a significant issue which impacts the network's stability. As a result, this fix has been deployed across all Win sites immediately.

Version 1.1.8.1 (08/01/2020) fixes an issue in the previous update which broke moderator mail.

Moderator mail was unavailable for around an hour. Users could still send mail, but moderators were temporarily unable to access the inbox.

Version 1.1.7.2 (07/31/2020) dynamically updates comment vote breakdowns.

In a recent update, we made public the raw number of upvotes and downvotes that a comment has.

Unlike the score, the upvote and downvote breakdown didn't dynamically change when voting. In this update, when you vote, the breakdown will immediately change.

Update by Trinadin.

Version 1.1.7.1 (07/31/2020) now returns you to the page through which you logged in.

For example, if you login in via the sidebar when viewing a post, you will now be returned to that post after being logged in.

Previously, you would have always been redirected to the front page.

Version 1.1.7.0 (07/29/2020) jumps ahead two fairly substantial releases of our framework (Spring).

This update will be released slowly to ensure that nothing breaks.

Version 1.1.6.4 (07/27/2020) adds formatting options when creating posts and comments.

Previously, formatting options were only available when creating and editing comments, but not when creating posts and messages.

In 1.1.6.4, you can use the formatting buttons as well as the Preview Mode when creating posts and private messages.

Version 1.1.6.3 (07/27/2020) makes a slight improvement to the way that moderators can manage their community report options.

Version 1.1.6.1 (07/27/2020) changes how we store IP addresses.

As outlined in our Privacy Policy, we store the latest IP address for each logged in user. This is overwritten every time that it changes.

As part of our effort to minimize the data that we hold on users, we're now hashing (and peppering) the IP addresses that we store.

This follows a change two months ago where we hashed (bcrypt) email addresses.

The reason that we store any IP addresses is so that we can detect networks of malicious accounts, which means that we need the hash of two identical IPs to be the same. We can't realistically salt the IP addresses, because then the values for two identical IPs would not match. We will reconsider this in the future.

Version 1.1.6.2 (07/27/2020) adjusts how we handle early cache eviction.

Previously, we'd have to evict far too much cached content whenever we needed to evict a cache early, which meant that we rarely did it.

We're now evicting only the exact content that needs evicting.

This means that in a future update we can implement a lot more on-demand cache eviction, which will help the site feel more responsive.

An example of this is when editing a post. Currently after editing, it'll immediately show as edited, but if you refresh the page, it'll likely show the cached, pre-edit version of the post for up to 60 seconds. In this situation, it'd be best to evict that cache on-demand so that those edits are reflected immediately.

Version 1.1.6.0 (07/26/2020) adds support for community icons.

Community moderators can now upload an image (PNG or JPG) on the community settings page.

This will converted into a variety of sizes for favicons and metadata, which will therefore be used in areas such as social media snippets, browser tab bars, and home screen icons.

Thanks in part to wethepepe.

Version 1.1.5.0 (07/25/2020) adds beta support for wiki pages.

Moderators can now create wiki pages within their community.

This is a link to an example wiki page.

Version 1.1.5.1 (07/25/2020) again updates the hot feed logic.

An error in the previous update at the start of the month meant that it didn't work as intended in all circumstances.

Version 1.1.4.1 (07/25/2020) fixes an issue with signups.

For two days following the server issues which impacted a Win site on the 21st July, signup wasn't possible through that Win site, but remained open on all other Win sites.

This is now fixed.

Version 1.1.4.0 (07/21/2020) adds support for rule based filtering ("AutoModerator").

At current, it takes action on 'remove' and 'approve' signals.

Update by chewsoap.

Version 1.1.3.1 (07/21/2020) temporarily disabled RSS feeds.

Version 1.1.2.15 (07/18/2020) fixes an issue where some pages would inadvertently scroll horizontally.

An upload last week broke some pages - this fixes that.

Update by Trinadin.

Version 1.1.3.0 (07/18/2020) moves thumbnail images from the "img" subdomain to "media".

This means that user uploaded images and post thumbnails reside in the same location. The goal is simplification and, more importantly, stability improvements.

While this version is now live on all Win sites, the version number in the sidebar may not accurately reflect this.

Version 1.1.2.14 (07/18/2020) fixes an issue where user uploaded images weren't being deleted.

Ordinarily, we delete images two hours after being uploaded if they are not posted in that timeframe.

A previous update adjusted the paths of user uploaded images, which inadvertently broke the cleanup process.

15

Version 1.1.2.13 (07/13/2020) exposes new information about comment scores.

Next to each comment, you can now see a breakdown of how that comment's score is calculated - its quantity of upvotes and downvotes.

Moderators could opt to disable this via their community's stylesheet with the ".breakdown" class.

10

Version 1.1.2.12 (07/13/2020) renames what were previously called "wins" to "score".

Previously, the total sum of your upvotes was referred to as "wins".

Now, it is referred to as "score" - your "post score", and "comment score". Profiles have been updated to reflect this change.

Version 1.1.2.11 (07/12/2020) adds back some restrictions on messaging for high risk accounts.

Due to the nature of this update, the specifics can't be disclosed. However, this update does not restrict anyone's ability to send legitimate private messages - it only intends to hinder spam bots.

Version 1.1.2.10 (07/11/2020) fixes an issue when sorting profiles on mobile.

Previously, sorting by "worst" on profiles on mobile would unintentionally sort by "top".

10

Version 1.1.2.6 (07/11/2020) removes the social media icons from the header in all communities except The Donald.

Despite being in all other communities, it wasn't visible by default, as the base Win CSS hid it, but it was still there in the background.

Eventually, it will also be removed in The Donald, and added back via the sidebar and community CSS.

As Win transitions into a platform for many communities, we are removing code that's specific to a single community.

view more: Next ›