Re:John Carmack: Steps to Avoid Aliasing in VR
by mcpherrinm on Friday July 29, 2016 @01:49AM
(#12185207)
Whether or not a post is available to "the public" (signed in or not) is completely the choice of the author, not some mysterious committee at Facebook.
[ Parent
| on HN ]
Re:John Carmack: Steps to Avoid Aliasing in VR
by rmtew on Friday July 29, 2016 @04:10AM
(#12185550)
Have you tried to read a page on facebook without an account? It's intended to be an almost unusable experience.
On loading a page, I get a modal popup obscuring all content insisting I "register" or "login", with a "not now" option. Then when you click "not now", the bottom third of the screen is obscured by a fixed overlay.
It is loosely describable as readable, but in practice, it's a fight to read it. The element has randomly generated id, so can't easily be blocked with ublock or similar.
Re:John Carmack: Steps to Avoid Aliasing in VR
by tmsbrg on Friday July 29, 2016 @05:56AM
(#12185821)
I agree Facebook is a bad place for placing public content. Note though that it's currently a lot more bearable if you disable JavaScript for Facebook. As someone who doesn't use Facebook at all it's easy for me to keep it disabled with NoScript. Then I just see content, no popups.
indeed: inspect element -> style='display: none' should not be mandatory to read a page. Grease monkey is an option, but still.
Re:John Carmack: Steps to Avoid Aliasing in VR
by intoverflow2 on Friday July 29, 2016 @05:55AM
(#12185818)
It's coded in react or whatever so it just gets recreated a second or so later.