LW Update 2019-03-12 -- Bugfixes, small features
post by jimrandomh · 2019-03-12T21:56:40.109Z · LW · GW · 7 commentsContents
7 comments
We've deployed an updated version of LessWrong, with a bunch of bug fixes and small features added since last time (March 1).
Features and Changes
- Auto-linkify URLs in posts and comments
- Coauthored posts appear on your user profile page
- Drafts that are shared with you appear in the Drafts section of the user profile page
- Negative-karma change notifications don't use red color
- Posts on the All Posts page have a menu on the right
Bug Fixes
- Address some compatibility issues with Opera Mini, Edge, and IE11
- Remove broken New Users Notification and New Posts Notification settings
- Table of Contents: Empty blocks can't be headings
- Remove spurious All Posts View setting from user profile page
- Fix a visual glitch during loading (SSR) of the all-posts page
- Fix a bug where the RSS synchronization cron job would sometimes stop running
- Don't redundantly show the AF icon on alignmentforum.org
- Remove a duplicate Load More button on the user profile page
- Fix a crash in the Sunshine Sidebar with reports of already-deleted comments
- Various fixes to search indexing
- Fix a security vulnerability that could reveal unpublished drafts
API Changes
- Add localStartTime and localEndTime resolvers to posts, which return the time of a meetup in the time zone of the meetup location (null if no location specified)
Technical
- Clean up sequences
- Infrastructure for validating database contents against schemas
- Optimize some slow mongodb queries
- Migration infrastructure for dealing with denormalized fields
- robots.txt now blocks crawlers from our test servers (no change on the main site)
7 comments
Comments sorted by top scores.
comment by Taymon Beal (taymon-beal) · 2019-03-13T04:38:42.080Z · LW(p) · GW(p)
The Slate Star Codex sidebar is now using localStartTime to display upcoming meetups, fixing a longstanding off-by-one bug affecting displayed dates.
comment by Pattern · 2019-03-14T01:26:12.508Z · LW(p) · GW(p)
Auto-linkify URLs in posts and comments
When people type the URL, the option is automatically presented, or when people post something containing a URL (without a link), one is automatically added?
Replies from: jimrandomh↑ comment by jimrandomh · 2019-03-14T01:50:52.521Z · LW(p) · GW(p)
The latter, but it applies immediately when you type it (rather than waiting until you click Submit), so it won't happen without you noticing.
Replies from: Pattern↑ comment by Pattern · 2019-03-15T00:22:57.704Z · LW(p) · GW(p)
I initially wondered because I'd seen a comment written after this post which had a URL, but no link. I've found the auto-linking works just fine for me though.
Replies from: Raemon↑ comment by Raemon · 2019-03-15T00:34:44.029Z · LW(p) · GW(p)
Possibly the comment was from greaterwrong, or maybe markdown editor? (I'm not sure how either of those currently handle links)
Replies from: jimrandomh↑ comment by jimrandomh · 2019-03-15T00:39:54.599Z · LW(p) · GW(p)
Neither of those will autolink. Autolinking is handled at the UI level, in the default (WYSIWYG/draftjs) editor only.
Replies from: habryka4↑ comment by habryka (habryka4) · 2019-03-15T01:28:39.492Z · LW(p) · GW(p)
Not true. The markdown editor also autolinks, and it does so on the server-side, so greaterwrong should also be good (unless they send HTML directly, in which case it won't work).
We implemented the markdown editor autolinking a few weeks ago, since it was literally just adding a single option to our markdown parser.