Hot answers tagged

8

After some discussion with our SRE team, I have some good news: these redirects will be working by the end of Shabbat.* There are a couple of caveats, however: We are using Cloudflare's free plan which doesn't really offer a service level agreement (SLA). HTTPS is included so you can use links like: https://yodeya.com/q/1 It's possible that service will go ...


8

This should now be fixed in the next build. Thanks for reporting!


7

There is a grace period after a question is put on hold during which an answer that was started before the question was put on hold can still be submitted. The rather-old MSE post I linked to says this grace period is around 4 hours, but my own observation has been that it's somewhere around 30-60 minutes nowadays. Also, apparently the mobile client (I don'...


6

Just to close the loop: this has been resolved.


6

This should be fixed now, it will be live after our next production build.


6

Ok, I've updated some things in cloudflare: I expect the following links to all work (after dns propagation): http://yodeya.com/questions/12760 https://yodeya.com/questions/12760 https://www.yodeya.com/questions/12760 http://mi.yodeya.com/questions/12760 https://mi.yodeya.com/questions/12760 http://meta.yodeya.com/questions/4171 http://meta.mi.yodeya.com/...


6

It actually is parsing it as a list, as checking the HTML of the page confirms. The reason it is outdented is so that the period of the list always appears in the same place. Observe: list break another list


6

Sorry about that. I have a fix ready and queued up for deployment to production. Unfortunately, our full prod builds are currently blocked on testing a major infrastructure change. That should clear up sometime between later today and end of tomorrow, but I don't have a specific time at the moment. In the meantime, I apologize for the annoyance and the ...


5

Quoting from this answer on MSE: We rolled out a new image uploader today. Unfortunately, the design was targeted at the new-design sites only, and so the image uploader stopped working (at all) on the old-design sites. In a hurry to get the image uploader working, we grafted the new image uploader styles to the old base styles. This had some of the side ...


5

This will be fixed in the next build, > rev 2013.4.1.595.


5

My bad - a fix will be pushed out in the next build, > rev 2013.2.21.516.


5

Code was added since that post was created to trim titles down. If you look at the revision before yours (since the first post revision), there's a trailing space on the end. Your edit triggered this code on edit and did change the title...so that's why it shows up as a title edit. Though it's a bit odd in this case, it is working as designed.


5

The canonical answer is always: caching. That said, we have implemented a live update feature for various and sundry pages on the site. The homepage, however, is still subject to a degree of caching. We're gradually moving towards more and more live updating on our sites. It used to take several minutes to have a new question appear. Now, it takes several ...


5

I agree that jewish%20life%20and%20learning should be scrubbed. The convention we should follow would involve changing the slug to judaism, making it into data.stackexchange.com/judaism/queries, as Double AA suggested.


5

I'm adding underline on links to make them pop out more (only on meta). It will be live after our next production build.


5

That question1 was deleted by the community as being "rude or abusive". As the quasi-official description says: The rude or abusive flag (formerly known as offensive) is meant to be used only in extreme cases, like hate speech, abuse against people, or abuse of the community or system. For what it's worth, I agree with the community that this qualified. ...


5

This has been answered adequately by others in the comments to the question; I'm just collecting the information here. The answer was edited from "I read…" to "Perhaps…" within five minutes, which generally doesn't show as a separate edit in the answer's history. Your inbox notification must've either arrived before that edit or been based (blame caching) on ...


4

My apologies. This will be fixed in the next production build, > rev 2013.2.7.1394.


4

Because it hasn't gotten any upvotes yet. The hat is only awarded once it's positively scored. Why didn't (or did) I or some other user get a hat although the requirements were (or weren't) fulfilled?


4

Suggested edits on tag wikis get queued for <20k users. Try it :)


4

Answer can be found here - downvotes and deleted posts are not counted in your monthly (and I assume yearly) score, but are factored in to the displayed total score.


4

The status you see there relates to the whole thread (questions + answers). When an answer is deleted we don't bump the last activity date, we just set the last activity type as modified. We can't leave it with an answered status since this would allow for questions with 0 answers to have an answered status. Unfortunately history is tracked for each post (...


4

StackExchange works on UTC. Right now in, say, NYC Shabbat ends around 6:30 so it's possible if not likely that someone would miss logging in by 7PM EST which is midnight UTC. If that doesn't apply to you, perhaps you didn't do anything particularly active during the 24 hour day? I don't think there are clear guidelines about what must be done to be ...


4

Sorry about that. The notice on the main site is manually configured and stored in a different spot from posts, so while we did automatically rewrite links in posts, it got missed. Fixed it up now, so it should point to the correct domain going forward. Also updated the meta post quoting the message since it was using a relative-protocol link and those were ...


3

I checked with our designer (Jin) - and 1024px is the minimum that we support. While many things happen to work at smaller widths, they aren't officially supported to do so. As you notice, it behaves well down to about 990px, which is pretty much the best we can do to make sure nothing looks awful to someone using that width within a window that isn't ...


3

I've just pushed through a DNS change that should fix this soon. Thanks for letting me know.


3

Yeah, that's bad, not only from a display standpoint, but also from the back-end, which expects only questions to be locked with historical significance. So, I've removed the ability to lock answers as historically significant, which was probably used to keep them from being flagged. To help combat new flags on locked posts, only the "other" reason will be ...


3

As noted in comments above, the same proposal has been made, and has had many, many eyes on it for quite some time, on Meta Stack Exchange. Please see there for more information and future updates. I'm posting this here just to get this question off of the list of unanswered questions here.


3

To the system, there was no edit as the author edited within the initial grace period of five minutes. All edits during this period are just considered a single revision, allowing a chance for simple corrections to not clutter the revision history. We all vote to the same end, but with subtle differences in application. I typically won't vote for a post ...


3

Sorry about that. We accidentally a wrong file in another file.


Only top voted, non community-wiki answers of a minimum length are eligible