Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Comments on Abilities update is here!

Post

Abilities update is here!

+21
−0

U P D A T E:

It looks like some changes have gone missing after the rollout; we're working on adding them back right now. See this answer for more information.

We have deployed the new abilities system! Please let us know if you find any problems - while we've tested the system as much as we can, some teething problems are inevitable, so let us know how it's going.


We're going to take Codidact offline for, we hope, a short time while we deploy these changes. Work on the update will begin November 24, 2020 at 20:00 UTC. During the downtime we will do a full database backup (just in case), deploy code updates, perform database migration, and calculate the initial abilities for everybody. It's this last part that will take some time.

Because we are moving from reputation-based privileges to activity-based abilities, some of you will lose privileges you already had. For example, you might have had enough reputation that you had very few, if any, suggested edits before being able to edit directly. This means you'll have very few suggested edits on your record and so won't qualify for being able to edit directly under the new system. We apologize for the inconvenience. If you feel that something is really off, please let a moderator know and we can try to adjust things for you.

After the update, you'll see a revamped user profile, including what abilities you have. From there you can see a list of all of the abilities, with descriptions and your (approximate) progress toward them. We run abilities checkes a few times a day, so there will be a little lag between when you qualify for an ability and when you have it.

You'll also see improvements to the flags interface, for both flaggers and moderators.

We've tried to test this thoroughly, and some of our testers are very creative, but a test server probably can't reveal all the issues. If you see something that looks wrong, please let us know. Team members will be monitoring Meta, GitHub, and Discord.

These improvements have been a long time in coming, and I want to thank the team for all their hard work on this. luap42 designed and implemented the system and even held some live coding sessions via Twitch to show others what's going on behind the scenes. ArtOfCode assisted with development and setting up the regular checks. Mithical, Sigma, and I wrote the guidance in the user interface and wrote new documentation. All of those folks, and Mithrandir24601 and Moshi, beat up on our poor test servers to find bugs. Many others provided feedback in chat and on GitHub. Thank you all, and if I have missed anyone, please accept my apology.

Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (11 comments)
General comments
luap42‭ wrote about 2 years ago

Oof. So excited; hopefully everything goes well. If not ... you'll probably not be able to tell us 😃

Canina‭ wrote about 2 years ago

In that case, no news is not good news!

Monica Cellio‭ wrote about 2 years ago

Discord and Twitter, @luap42... they'll be able to reach us. So we'd best get this right. :-)

Skipping 1 deleted comment.

ghost-in-the-zsh‭ wrote about 2 years ago

What part of the time estimate calculation was off? Based on wording, was it a network data transfer to get DB migration started, or the actual amount of I/O caused by the migration in the DB locally after transferring the data, or both, or something else?

luap42‭ wrote about 2 years ago

@ghost-in-the-zsh eh... the database migrations themselves took far longer than we expected (for example: 20 mins for one (!) change), likely, because the post and user tables are much bigger than any table we have locally (that one change added a reference between posts and users)

Zerotime‭ wrote about 2 years ago

@luap42 @ArtOfCode Is there a reason that Cooking is still down? Most other sites seem to function.

Monica Cellio‭ wrote about 2 years ago

@Zerotime Cooking is working for me. If it's not for you, try flushing browser cache, in case it cached the redirect to our "down" page?

FoggyFinder‭ wrote about 2 years ago

The main meta page still redirects me to an abilities-downtime page. That's definitely related to browser cache but is there is anything that you can do from your side? If I didn't visit some Q on a meta accidentally I would think Codidact is still down. And I think I'm not the only one who experienced such issue.

Monica Cellio‭ wrote about 2 years ago

@FoggyFinder I asked, and apparently the request isn't even reaching our servers; the caching is happening locally, so there's nothing we can do to force expiration on our end. :-(

Canina‭ wrote about 2 years ago · edited about 2 years ago

@FoggyFinder Unfortunately, for a brief while, the redirection was done as a permanent redirect instead of as a temporary redirect. This was fixed pretty quickly by the team, but permanent redirects are allowed (and encouraged) to be cached in various ways by the browser. Clear the browser cache, check any bookmarks and other places where URLs are stored locally, and keep your fingers crossed; at this point, unfortunately, there's very little the Codidact admins can do.

mbomb007‭ wrote almost 2 years ago

Nice, Font Awesome icons.