Hmm, you can see all recent posts on /daily on the new LW.
Habryka
Karma: 290
Sorry for not being around more! We launched the Community/Meetup interface just before we announced the vote, so I’ve been busy polishing that up and making sure everything for that works.
Now that that system works more stably, I will be more responsive in answering questions about the vote and the transition, etc. And in general I check LW2 more often than here, so if you have questions asking over there will probably get you a faster response.
Re password reset: Yep, everything you said is correct, and it does seem reasonable to have a page with both developer contact info and password reset functionality that is accessible without fancy JS. But I don’t know how much I can promise yet for that, since it might just end up being a big pain to make the Meteor password reset work without any JS whatsoever. But we should test it so that it at least works in IE 9+.
Oh, huh. I didn’t realize this as a bug. Thanks for pointing it out!
We have plans to allow people better filtering options for comments and posts in general, somewhat similar to what greaterwrong has to show posts sorted by month and year. So that would fix this problem. I am hesitant to allow the serve to return more than 1000 comments on a single graphQL request though, simply because of server-load reasons. So a proper pagination approach would help with this, which would come with the better filtering and sorting I am imagining.
In general, I think it’s very important to make the old content on the site discoverable and findable, and I definitely want to make sure we fix the kinds of bugs you brought up here.
The site should now work properly on Firefox 48. Are there any other browsers you use on which it still breaks?
Yeah, we are working on browser compatibility. I actually just figured out what was causing your specific bug, so that one should be fixed within at least the next two or three days.
Some navigation aspects are definitely hard to make work with javascript completely disabled (example: The hamburger menu), but we should be able to make it so that the site fails gracefully when some javascript stuff doesn’t work.
Yep, I agree with this. I’ve learned quite a few things from the GreaterWrong design and overall think that the LW2 UI will be significantly better because of that. It’s great to have a platform that experiments in a very different direction from the main site.
(i.e. There should be no further issues with LaTeX not rendering)
Yeah, that’s a bug. I am planning to remove the whole website field soon anyways.
Alas, I haven’t been super much on top of support lately, so sorry for not responding.
Sorry for this happening. I mistook you for Eugine_Nier, who was spamposting with a bunch of highly political stuff right at the minute you made your first few comments. It looks like you accidentally posted a comment twice, and the one that you posted twice was one that commented on the relationship between the MTG wheel and Nazism (actually making an OK point, but my pattern match system immediately matched it to Eugine’s other spam comments). That, together with the fact that your email address was a fake email led me to the false belief that you were one of Eugine’s sockpuppets.
I unbanned you, and will try to be more on top of support in the future.
We actually have plans for a more chat-like section of the site, though we haven’t yet fully converged on an implementation. Here is the relevant section from the LessWrong 2 strategy doc:
Shortform (implementation unclear)
Many authors (including Eliezer) have requested a section of the site for more short-form thoughts, more similar to the length of an average FB post. It seems reasonable to have a section of the site for that, though I am not yet fully sure how it should be implemented.
Yep, though I do expect this to happen at least in its basic functionality by the end of the year, though we might not be able to get full feature parity before we move over towards the new site. I would be interested in getting a list of the most important features you see for our meetup functionality.
You can now also deactivate Intercom on your profile. I really wish Intercom wouldn’t do the horrible thing with the tab-title.
Because that would add a whole different level of complexity to our code, where now instead of just managing CSS styles, we would need to both manage css styles in one section of our page, and JS-inline styles in another section of the page. Since the interface by which you change the material-UI inline-styles is by passing style-objects to the relevant React components.
We tried this for a bit, but this made things much harder to maintain and keep clean than having important-statements in some parts of the CSS.
In the long-run I want to move towards a styled-components approach, where all styles live in the component files, which we can do after the current @next branch of material UI reaches maturity and feature parity with the current one.
Ah, i agree that that is usually a good heuristic. In our case it’s a bit different though.
We are currently using the Material-UI frontend framework, which is great on a really large set of dimensions, but does all of it’s styling in the form of inline CSS (the latest version is moving away from that, but that is currently only in prerelease).
In our case, the vast majority of the !important statements are there to override one specific lowest level material-UI inline style, and are not there to override any other styles in our own CSS files. This makes the impact of those statements significantly less bad than they would usually be. Still not happy about having to use the important tags that way, and it does definitely have some cost, but overall the cost is much lower than one would naively expect.
We actually just cleaned up our CSS a bit, but agree that we probably want to make that part cleaner in the long run. Though I haven’t found making changes particularly difficult.
That is correct! I’ve been a bit less responsive in the last week, but usually get back to people within half an hour to an hour, and have helped dozens of people migrate their accounts, fix bugs, change email addresses, etc.
This is fixed now.
The plan is to keep the wiki but to not integrate it particularly much into the site. Old links will continue working, but it won’t be something that’s prominently linked from the site anymore.
It probably makes sense to rework the wiki as well and then integrate it into the site more properly, but until then we are probably going to deemphasize the wiki but otherwise leave it as is.
Strongly agree with 1. I have a plan for a separate thing at the top of the frontpage for logged-in users that takes up much less space and is actually useful for multiple visits. Here is a screenshot of my current UI mockup for the frontpage:
https://imgur.com/a/GXjTY
The emphasis continue to be on historical instead of recent content, with the frontpage emphasizing reading for logged-in users. If you don’t have anything in your reading-queue the top part disappears completely and you just have the recent discussion (though by default the HPMOR, The Sequences and The Codex are in your reading queue)
All activity between now and 7:00PM on the page will be lost.