LWN: Comments on "Touring the hidden corners of LWN" https://lwn.net/Articles/622988/ This is a special feed containing comments posted to the individual LWN article titled "Touring the hidden corners of LWN". en-us Sun, 09 Nov 2025 14:49:20 +0000 Sun, 09 Nov 2025 14:49:20 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net Touring the hidden corners of LWN https://lwn.net/Articles/645710/ https://lwn.net/Articles/645710/ sethml <div class="FormattedComment"> Yes yes yes!<br> <p> Also useful for browsing difficult comment threads on a small screen would be "up", "next", and "previous" links on comments, which would scroll to the parent, sibling, and prior comments, respectively. I often find myself buried in reading some flame war or a discussion of the minutiae of the history of some kernel bug, and decide I'd like to move on. With scrolling links, this would be easy: hit "up" until I find the responsible parent comment, then hit "next". As it stands, I have to scroll while judging from indentation when I've escaped the uninteresting section - almost impossible.<br> <p> Links would be easy to implement with anchors for each comment, and I think would eliminate much of the need for collapsible comments.<br> </div> Sat, 23 May 2015 16:12:24 +0000 Sidebar background https://lwn.net/Articles/628983/ https://lwn.net/Articles/628983/ Brenner <div class="FormattedComment"> Indeed, #ffcc99 in the "Left column color w/new page engine" is much better !<br> <p> PS:<br> This comment mostly there so that I can find it later easily in my "Comments you have posted" list.<br> </div> Fri, 09 Jan 2015 09:49:59 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/625458/ https://lwn.net/Articles/625458/ nix <div class="FormattedComment"> Yeah, but either sites have to apply this themselves (which none of them do) or you have to override everything with a custom stylesheet (which smashes a lot of sites into screaming flinders). I wish there was a better way...<br> <p> </div> Wed, 10 Dec 2014 16:27:04 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/625457/ https://lwn.net/Articles/625457/ nix <div class="FormattedComment"> The 'Stylish' browser extension for Chrome and firefox has a 'Dark LWN' theme in its style library.<br> </div> Wed, 10 Dec 2014 16:24:12 +0000 RSS https https://lwn.net/Articles/624755/ https://lwn.net/Articles/624755/ Darkmere <div class="FormattedComment"> Personally I'd hope for something like<br> $ find . -type f -print0 | xargs -0 sed -i s/http:/https:/g <br> <p> </div> Fri, 05 Dec 2014 10:28:21 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/624721/ https://lwn.net/Articles/624721/ jschrod <div class="FormattedComment"> <font class="QuotedText">&gt; You should not be using Windows XP, and you should not be using IE 8.</font><br> <p> "You should not be using Windows XP, and you should not be using IE 8, for reading lwn.net"<br> <p> FTFY.<br> <p> There are lots of reasons to use XP and IE8. Almost all of them have to do with the fact that people still use it and one wants to have a test environment to observe their experience. I have dozens of such VMs lying around and I need them badly.<br> <p> That said, a reason to use such environments outside virtual machines that don't connect to the Internet -- well, that's hard to find.<br> <p> What I want to communicate: reality aint't that black-and-white. You have to ask for the context first; then you can make assertions like you did.<br> </div> Fri, 05 Dec 2014 02:19:20 +0000 RSS https https://lwn.net/Articles/624715/ https://lwn.net/Articles/624715/ intgr <div class="FormattedComment"> Same with "subscriber links"<br> <p> </div> Fri, 05 Dec 2014 00:40:44 +0000 Any comment thread collapse? https://lwn.net/Articles/624690/ https://lwn.net/Articles/624690/ cdmiller <div class="FormattedComment"> One thing that would be nice IMO is the ability to collapse any thread, not just the filtered ones.<br> <p> I'm sure you hear this all the time, but thanks for all the great work over the years by LWN. The approach of concentrating on the quality of content before all else is much appreciated.<br> </div> Thu, 04 Dec 2014 22:57:01 +0000 HTTP redirection https://lwn.net/Articles/624554/ https://lwn.net/Articles/624554/ nye <div class="FormattedComment"> <font class="QuotedText">&gt;SSL was trademarked to Netscape, when it became a standard for more than a single vendor, it had to change the name, to TLS instead</font><br> <p> [citation needed]<br> <p> I can find only one other reference to this, an off-hand comment without citation <a rel="nofollow" href="http://technotes-fran.blogspot.co.uk/2010/05/ssls-dirty-little-secret.html">http://technotes-fran.blogspot.co.uk/2010/05/ssls-dirty-l...</a>); it's not mentioned at all on the Wiki page for SSL or TLS.<br> <p> Additionally, a search of the USPTO's trademark database comes up with nothing relevant (though there are a lot of more recent trademarks *containing* SSL), which leads me to conclude tentatively that this is probably not true.<br> </div> Thu, 04 Dec 2014 16:47:11 +0000 HTTP redirection https://lwn.net/Articles/624549/ https://lwn.net/Articles/624549/ robbe <div class="FormattedComment"> That explains why it was called TLS. But giving it a 1.0 version was certainly dumb.<br> <p> I can't imagine though, that the trademark has survived.<br> <p> </div> Thu, 04 Dec 2014 16:25:25 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/624528/ https://lwn.net/Articles/624528/ mina86 <div class="FormattedComment"> OK, nvm. I've noticed the menu button in bottom left. <br> </div> Thu, 04 Dec 2014 15:08:37 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/624488/ https://lwn.net/Articles/624488/ jani <div class="FormattedComment"> Chrome on Nexus 4, the menu on the left (when popped up using the button) gets cropped from the left using the new page engine. Seems to be related to Settings | Accessibility | Text scaling option, which I've set to 125%. (Even with that set back to default 100% the menu starts at the very edge of the screen, with zero padding.)<br> <p> </div> Thu, 04 Dec 2014 12:35:26 +0000 Mark read comment https://lwn.net/Articles/624487/ https://lwn.net/Articles/624487/ jani <div class="FormattedComment"> That's a feature I've been looking for in the article view, highlighting of all messages that would show up in <a href="http://lwn.net/Comments/unread">http://lwn.net/Comments/unread</a>.<br> <p> <p> </div> Thu, 04 Dec 2014 12:28:46 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/624485/ https://lwn.net/Articles/624485/ mina86 <div class="FormattedComment"> Am I blind or did mobile version loose “go to previous edition” and “go to following edition” links? For me those are a must since otherwise I seem to be forced to go through the Archive which is many more clicks and scrolls. <br> </div> Thu, 04 Dec 2014 12:25:33 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/624463/ https://lwn.net/Articles/624463/ gidoca Chrome for Android also has this effect, see <a href="https://s3.amazonaws.com/pushbullet-uploads/ujvtEghnLUa-JRSTPo5olox7vd7P5ZF4WhMRNxSxN1f9/Screenshot_2014-12-04-11-04-00.png">this screenshot</a>. Thu, 04 Dec 2014 10:05:21 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/624194/ https://lwn.net/Articles/624194/ lsl <div class="FormattedComment"> <font class="QuotedText">&gt; You pull your browser window wide because you want it to fill the whole screen -- but of course on widescreen monitors that means large margins or horribly hard-to-read text.</font><br> <p> Yeah, but why do you want it to fill the whole screen when all it results in is pain? Open another window and make them fill the screen together. If you can't think of anything to put in the other half of the screen just make it an additional browser window. It will fill itself in the course of a browsing session.☺ <br> </div> Wed, 03 Dec 2014 06:20:50 +0000 IE 8 https://lwn.net/Articles/624193/ https://lwn.net/Articles/624193/ lsl <div class="FormattedComment"> <font class="QuotedText">&gt; More seriously: I guess this very much depends on how demanding/picky you are. I don't think supporting a browser version is a black or white question. I doubt the site is completely unreadable in IE8 as it is right now, or is it?</font><br> <p> From time to time I visit LWN using Tom Duff's Mothra as my user agent. It looks very different from LWN in most other browsers but you can actually read the articles (and navigate the site!) just fine, albeit somewhat quirky. So no, it's not a binary decision, except maybe for websites that require tons of javascript to even load the page.<br> </div> Wed, 03 Dec 2014 06:04:26 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/624153/ https://lwn.net/Articles/624153/ Seegras <div class="FormattedComment"> <font class="QuotedText">&gt; The right fourth or so of the screen is entirely blank (1920x1080, 12" </font><br> <font class="QuotedText">&gt; screen), no matter what text zoom. I don't understand why.</font><br> <p> Monitors are bloody well not made so you can spread text beyond the borders of anything sane. And in case of text, its supposed to be where your eyes are, and not that you need to constantly move your head. 1920x1080 is made for movies, not text, and as it happens you've got resizeable windows, so you can spread text to more natural dimensions. <br> <p> I read LWN in a format that's natural and nice to read, namely 1:1.681, also known as golden ratio. <br> <p> And this leaves space for terminals on the side of the browser window as well, which is most probably as K&amp;R intended ;). <br> <p> So if your browser window is in anything but the golden ratio dimension, you're obviously doing it wrong, and you shall live in a hell of bad typography (I'm pretty sure you also think Arial is nice, and Comic Sans looks good) and bad layout.<br> <p> </div> Tue, 02 Dec 2014 22:34:50 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/624022/ https://lwn.net/Articles/624022/ cesarb <div class="FormattedComment"> <font class="QuotedText">&gt; The *right* solution would be for web browsers to learn how to produce multicolumn text output on the fly, as needed.</font><br> <p> You mean "column-count: auto"? <a href="http://www.w3.org/TR/css3-multicol">http://www.w3.org/TR/css3-multicol</a><br> </div> Tue, 02 Dec 2014 13:26:03 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/624015/ https://lwn.net/Articles/624015/ nye <div class="FormattedComment"> I don't disagree with the general idea behind your post, but I feel I have to make a factual correction:<br> <p> <font class="QuotedText">&gt;You should not be using Windows XP, and you should not be using IE 8.</font><br> <font class="QuotedText">&gt;Both are not supported any more, which means you would be irresponsibly putting yourself and others at risk.</font><br> <p> Not only is IE8 still supported, it will remain supported until 2020.<br> <p> In fact, even IE*6* is still supported for a few months more, though only on Server 2003.<br> </div> Tue, 02 Dec 2014 13:05:03 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/624006/ https://lwn.net/Articles/624006/ tpetazzoni <div class="FormattedComment"> This is indeed simpler, but still I'd have to run this a cronjob. LWN could be running this instead, and send the result to the @kindle.com address of interested subscribers.<br> </div> Tue, 02 Dec 2014 12:20:51 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/623991/ https://lwn.net/Articles/623991/ nix <div class="FormattedComment"> Perhaps I'm missing something, but why do you need a whole recipe when<br> <p> ebook-convert "LWN.net Weekly Edition.recipe" ~/tmp/conversion/lwn-$(date +"%Y-%m-%d").mobi --output-profile=kindle --username=$USERNAME --password=$PASSWORD --keep-ligatures --smarten-punctuation &amp;&amp; calibre-smtp -a ~/tmp/conversion/lwn-$(date +"%Y-%m-%d").mobi -s "LWN subscription" -r $MAILSERVER -p 25 -e NONE my@email.address my.kindle.address@free.kindle.com<br> <p> will do?<br> </div> Tue, 02 Dec 2014 11:19:04 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/623990/ https://lwn.net/Articles/623990/ nix <div class="FormattedComment"> You pull your browser window wide because you want it to fill the whole screen -- but of course on widescreen monitors that means large margins or horribly hard-to-read text.<br> <p> The *right* solution would be for web browsers to learn how to produce multicolumn text output on the fly, as needed. But that's hard...<br> </div> Tue, 02 Dec 2014 11:16:31 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/623975/ https://lwn.net/Articles/623975/ Seegras <div class="FormattedComment"> You should not be using Windows XP, and you should not be using IE 8.<br> <p> Both are not supported any more, which means you would be irresponsibly putting yourself and others at risk.<br> <p> Furthermore, IE8 can't do forward secrecy if you don't support some very stupid ciphers in your https configuration (IE6, by the way, can only do SSLv3, which should be turned off anyway). But there are other browsers that work on XP and Vista.<br> <p> And if your company policy insists on XP and IE, you should be working somewhere else. Because such a company policy, like mandating that company cars must not be fitted with safety belts, shouldn't have survived your starting to work there ;)<br> <p> Really, lwn should not make any efforts to support such old and broken browsers. <br> <p> </div> Tue, 02 Dec 2014 08:14:36 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/623970/ https://lwn.net/Articles/623970/ eru <i>Since you seem to have IE8, how does the new site look with it for the moment?</i> <p> Readable, but the left sidebar disappears completely. Tue, 02 Dec 2014 06:47:52 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/623957/ https://lwn.net/Articles/623957/ rodgerd <div class="FormattedComment"> <font class="QuotedText">&gt; I think how you feel about supporting obsolete versions of Internet Explorer corresponds strongly with how much of your life you've spent doing browser-based development.</font><br> <p> More than I care to think about, and in the era of Navigator 4 and IE 4 and 5. <br> </div> Tue, 02 Dec 2014 04:17:07 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/623946/ https://lwn.net/Articles/623946/ b3nj4m <div class="FormattedComment"> Commonly known as the "Android stock browser".<br> </div> Tue, 02 Dec 2014 01:44:32 +0000 IE 8 https://lwn.net/Articles/623936/ https://lwn.net/Articles/623936/ marcH <div class="FormattedComment"> <font class="QuotedText">&gt; With luck it shouldn't be too hard.</font><br> <p> Famous last words!<br> <p> More seriously: I guess this very much depends on how demanding/picky you are. I don't think supporting a browser version is a black or white question. I doubt the site is completely unreadable in IE8 as it is right now, or is it?<br> <p> </div> Tue, 02 Dec 2014 00:43:29 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/623918/ https://lwn.net/Articles/623918/ k8to <div class="FormattedComment"> I think how you feel about supporting obsolete versions of Internet Explorer corresponds strongly with how much of your life you've spent doing browser-based development. I rather expect those who have done it as their main job for years would feel it's not worth bothering. If only from wanting to spare others from the pain.<br> </div> Mon, 01 Dec 2014 23:01:13 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/623915/ https://lwn.net/Articles/623915/ k8to <div class="FormattedComment"> I also get the blank right side. At the moment, fwiw, I'm running Firefox 33.1.1 on os x 10.8.<br> </div> Mon, 01 Dec 2014 22:57:25 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/623898/ https://lwn.net/Articles/623898/ dlang <div class="FormattedComment"> has anyone put together a reverse color scheme? the office I work in is rather dark and I would prefer white text on a back background, but with so many different colors to set I haven't gone through to figure out a set that work.<br> <p> It would be handy if that page had a sample that refreshed with the different colors as you set them rather than having to refresh the entire page (and potentially end up with a color scheme that makes it really hard to see what's what to fix)<br> </div> Mon, 01 Dec 2014 21:35:20 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/623896/ https://lwn.net/Articles/623896/ utoddl I would particularly like to see an option to pick a serif font vs sans-serif font. Font preference surely varies greatly among users, but I find the sans-serif particularly harder to read. (There's a reason my browser has a default font, and my default is not sans-serif.) Mon, 01 Dec 2014 21:24:53 +0000 IE 8 https://lwn.net/Articles/623885/ https://lwn.net/Articles/623885/ corbet FWIW, I would rather people were able to read LWN even if they're somehow stuck with a nasty old browser that takes extra effort to support. The fact that it isn't working yet makes it clear where this sits on the priority list, but I do intend to make it work before too long. With luck it shouldn't be too hard. Mon, 01 Dec 2014 20:03:03 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/623878/ https://lwn.net/Articles/623878/ flussence <div class="FormattedComment"> No, LWN (or any other site) should *not* be wasting its time catering to an obsolete, broken-at-release version of a Microsoft browser, especially not one that currently requires extra effort to inflict on oneself. That you're even trying to argue the contrary position is absurd.<br> </div> Mon, 01 Dec 2014 19:25:51 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/623867/ https://lwn.net/Articles/623867/ marcH <div class="FormattedComment"> <font class="QuotedText">&gt; From browsing support pages, I have come to the conclusion it comes down to its graphics chip. Takes Microsoft to create a browser with this kind of HW dependency!</font><br> <p> Graphics seems to have been an highlight of the release version 9, however HW acceleration does not seems to be mandatory, at least not in theory: <a href="http://support.microsoft.com/kb/2528233">http://support.microsoft.com/kb/2528233</a><br> <p> Maybe the installer requires HW acceleration and you can't disable HW acceleration until you've installed :-)<br> <p> Since you seem to have IE8, how does the new site look with it for the moment?<br> <p> </div> Mon, 01 Dec 2014 17:42:20 +0000 Comment filtering https://lwn.net/Articles/623866/ https://lwn.net/Articles/623866/ dskoll <p>Sorry, my bad. Comment filtering does work. I plead pre-coffee dementia... Mon, 01 Dec 2014 17:25:08 +0000 Comment filtering https://lwn.net/Articles/623848/ https://lwn.net/Articles/623848/ jake <div class="FormattedComment"> <font class="QuotedText">&gt; Could you enable comment filtering for members of a corporate group subscription? </font><br> <p> Hmm. If comment filtering is not available for members of a group subscription, that's a bug. We certainly intend it to be and I would be surprised if it isn't, since we would likely have gotten a complaint or two along the way.<br> <p> Can you send us the details to the lwn alias here at lwn.net?<br> <p> thanks,<br> <p> jake<br> </div> Mon, 01 Dec 2014 16:43:04 +0000 Comment filtering https://lwn.net/Articles/623846/ https://lwn.net/Articles/623846/ dskoll <p>Could you enable comment filtering for members of a corporate group subscription? Pretty please? Mon, 01 Dec 2014 16:18:24 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/623840/ https://lwn.net/Articles/623840/ rodgerd <div class="FormattedComment"> Because clearly complaining Jon shouldn't make lwn usable in particular browser/OS combos isn't excluding people.<br> </div> Mon, 01 Dec 2014 15:16:47 +0000 Touring the hidden corners of LWN https://lwn.net/Articles/623820/ https://lwn.net/Articles/623820/ jzb <div class="FormattedComment"> One feature I'd love to see one day - the ability to collapse a thread of comments. Sometimes a single comment spawns a really, really long thread of discussion I've no interest in - would love to be able to collapse that and move on to the next. (Not so bad on a desktop, but less fun on mobile.)<br> </div> Mon, 01 Dec 2014 12:09:22 +0000