27

Going back to the future sets a cookie named tm2019. Unfortunately it sets it only for a particular question path, but using the browser devtools you can change the path to / that causes it to effect the entire domain. You will have to do it on every SE site individually though - but you can also change the domain to .stackexchange.com to make it act like a ...


21

Your on/off preference should persist across each site now. Happy time traveling! :)


16

The public timeline for all questions and answers is now available for all users. More details are available here.


15

The idea of using UTC (as a "universal" time standard) is that it doesn't suggest an indigenous preference to being in any particular location on Earth. You may argue that calling it a "timezone" is incorrect wherever you found it, but that would be the bit to change (bug or feature request). But it doesn't make sense to switch to GMT simply to make the use ...


14

This answer previously contained a line of code that would disable this feature for a given site, but that is no longer necessary as SE has changed it to affect all pages rather than just the one. However, you can install this user script to remove it from all sites, network-wide, permanently, in your browser. As written, this script will permanently ...


13

I too find this new banner extremely distracting. I now see it often when hitting any Stack Overflow question from Google. I think the primary issue is that it's one of the top elements on the page, as if it was a site-wide banner or notification. It's the first thing I'm drawn to read, even more so than the question title or body. It also annoyingly ...


12

They are displayed in the order you unlock the queues. On regular sites you earn close/reopen voting privileges at 3,000 reputation, and that is when you gain access to those queues. You gain edit privileges at 2,000 reputation, and that gives you access to the Suggested Edits and Low Quality Posts queues. Aside from reviewing suggested edits, the low ...


11

The user page hasn't been updated with the responsive design yet, and 1200px isn't wide enough for it with the left nav enabled. I, too, use windows that are not humongously wide, and I disabled the left nav as soon as that option became available so I could reclaim the wasted space. (You can still access those few links on hover.) If you want to change ...


11

I've built a userscript to disable Time Travel mode on all sites, which you can install from here. The updated version (0.3) does not interfere with the fix rolled out by the developers. Thanks to @Makyen, @SonictheWizardWerehog and indirectly to @Bergi for your contributions. // ==UserScript== // @name Disable Stack Exchange Time Travel Mode // @...


11

I have written a short userscript that repositions the post notices back to their original locations: You can install it with this direct link (if you have a userscript manager) or view the source code on GitHub.


10

Yep, our capitalization is all over the place. The tricky part is our localization strings for other communities are based on the original English text. This means that if we change "share" to "Share", our translated communities (Russian, Japanese, Spanish, etc.) each have to re-translate. We'll be making things more consistent as we refactor and modify ...


10

The tag synonym dashboard got a redesign a few months ago and this seems to have been solved. When I click 'Delete' it clearly shows which synonym we're talking about:


9

The system has changed a bit over the years. Nowadays, Community doesn't edit the question anymore, instead, the link to the original question is shown as another banner at the top of the page: (live example)


8

A fix is merged to master, but will take some time to get deployed over the weekend. Thanks for pointing this out!


7

I have been FGITW'd by a cookie edit already, but if for some reason you prefer a userscript solution, let me provide one. // ==UserScript== // @name Novikov Self-consistency Enforcer // @namespace http://tampermonkey.net/ // @version 0.1 // @description Disables time travel on SE (April Fools 2019) // @author John "Novikov" Dvorak // ...


7

This feels bad for the community, and it feels fixable. Unfortunately, the second part is a misconception. In order to fix this, SE Inc. would have to work closely with the community. Your question would be a good starting point for such activities. Like a question that I asked on MSO about one year ago: How to fix triage!. I simply suggested to rework ...


6

There are several reasons why certain icons/logos are the way they are. Copyright: Ask Different is not allowed to use Apple's own logo. They settled for the Mac's Command Key logo instead, which was already 'public domain'. Size: I personally like the Mathematics logo; when it's in full size you can see it's derived from the Reutersvärd / Penrose triangle. ...


6

The Highly Active Question banner is now only shown to users who either do not have enough rep to answer (10 earned rep), or who have enough rep to unprotect (15K earned rep). Users who are in between these two privilege levels (and thus are able to answer, but can't do anything about the protected status) are no longer shown this banner.


5

Starting today, this message now reads: Your recent flag was declined - please review it before flagging this post! ...and links directly to the list of your recently-declined flags.


5

Calling this done - I added the question count to tags with a single question, and if you're happy with that, I'm happy as well. :)


5

What's going on is that when you vote to close your own question, it is not normally* considered a binding vote merely because you are its owner. Instead, the vote is recorded like any other vote. However, when a non-binding close vote is recorded of the Duplicate type, leaving the question still open, then the owner of that question is presented with a ...


4

I'm sorry, but your pedantry compass needs to be recalibrated. Time stamps on Stack Exchange are on the UTC time scale, not on the GMT time scale. It's pedantry, because the difference is less than one second at any time. Stack Exchange servers, like pretty much anyone on the Internet, presumably set their clock using NTP. NTP distributes UTC, including ...


4

My achievement dialog says "UTC TIME", not "UTC TIME ZONE". One could argue that the 'T' in UTC already stands for time, and 17:47 UTC would be more appropriate. Granted, but GMT TIME would suffer from the same problem.


4

This is a user-script bug. The "Purge all" button and the way it updates the UI is different from how the moderator menu does it. When the moderator menu purges comments, it follows it with a call to StackExchange.moderator.loadAllComments($post) which is mostly just a wrapper around StackExchange.comments.loadAll($post, '?includeDeleted=true'). This ...


4

Stack Overflow, as the first site on the network, always had sans-serif, I think. It's pretty common for websites. Sans-serif is essentially the default for Stack Exchange sites. The math site did not start out with serifs. This changed when the site got a design because Jin, the designer at the time, "believe[d] the serif typeface on the header and ...


4

I fully second this feature request. In scientific journals the keywords and the classification is also given right at the beginning (below the title or below the abstract) and not at the end of the article.


4

The dates should be numerical, ordered and include the complete data. This makes it possible for humans and machines to parse it with minimal thought on the format. There is no case to be made for using a regional format globally when the regional format fails on all the required fronts. The YYYY-MM-DD HH:MM:SS format can be parsed by anyone because it ...


3

Yes, this is a recent update from Stack Exchange, so this message is generic. The change applies only to comments and was announced in this post: Updated comment flagging - Supporting the new Code of Conduct In addition to this, a thank you response toast notification was added when a user flags a comment to show appreciation for that flag - and in the ...


3

Feedback on comment flags changed a few months ago as part of a reworking of the UI for comment flags. Everybody sees this message (with the green background, near the top of the frame) when flagging a comment; even moderators see it. (Why would a moderator flag comments instead of just deleting them? Sometimes we do it for auditing purposes, particularly ...


3

As the layout apparently changed again over the years, this feature request becomes valid again.


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