We’re moving (and a fundraiser update)!

posted by
December 22, 2016
   
Posted in News

Dear readers,

Today is the last day of the 14th year of Rational Review News Digest. Tomorrow is our 14th birthday and the beginning of our 15th volume under the RRND label. After today's edition, you'll find RRND back at its old-time original home:

http://rationalreview.com

Of course, today's stories are still at ...

http://rationalreview.news-digests.com

... and the nearly 80,000 posts at that URL will remain available as an archive -- if not forever, at least for some time. You should continue to receive email editions as normal, although there will be some format changes we hope you'll like.

The fundraising page will be moving, too, but you can find it for the moment at:

http://rationalreview.news-digests.com/support-rrnd

Speaking of which, thanks to our contributors since December 15 -- EM, EL, LW, PS, KM, SA, SC and DH -- who've our year-end fundraiser total to $1,335.50 versus our goal of $5,000 by December 31.

Please help us get closer to that goal. I try to keep fundraising to a minimum for most of the year because I hate it just as much as you do, but RRND/FND IS a reader-supported publication. If you found it valuable this year, please return some of that value at, once again:

http://rationalreview.news-digests.com/support-rrnd

See you tomorrow at the new place!

Yours in liberty,
Tom Knapp
Publisher
Rational Review News Digest / Freedom News Digest

 
  • dL

    opendyslexic font? A temporary obfuscation?

    • It’s supposed to be the opposite of obfuscation — easier to read for dyslexic and non-dyslexic alike.

      • dL

        unfortunately, for the non-dyslexic, its pretty close to unreadable and atheistically an off-putting eye sore.

        • Hmm. I found it neither.

          • dL

            a quick google search shows around 1/2 agree with me, 1/2 agree w/ you. To me, that font reminds me of reading docs under terminal access to an old windows NT machine w/ poor resolution and font support back in the 90s. But, hey, it’s your site…

          • Well, I would like as many people as possible to like how the site looks. The theme’s default font was fugly and this was a quick and easy undoable fix (a toggle in Cloudflare) that I thought was pretty damn good looking.

            Do you have any font suggestions? If they make the site look good instead of like ass, I’ll be glad to give them a try.

            Of course, unless something has changed in browsers over the last decade or so (which was probably the last time I checked), the reader should be able to set a site for any font he wants.

          • dL

            the better open source fonts for web are open sans, ubuntu, lato and roboto.

            Browser settings allow you to change default fonts but do not allow you to override/customize per site css embedded font rules. You have to resort to an extension from the applicable app store for that.

            You can disable embedded web fonts entirely, which will then allow you display the site in default fonts, but its a global setting applying to all sites. Akin to disabling javascript.

          • I looked at the four fonts you mentioned. All of them except roboto are so much uglier and illegible than OpenDyslexic that I wouldn’t be willing to punish readers with them. I’ll see if I can figure out the CSS to replace everything with roboto, though. It’s only a little uglier and less legible.

          • All right, should be done, and I only pissed myself three or four times from worries about breaking the theme (acutally all I had to do was add a link to header.php and do a global replace of “Oswald” with “Roboto” in the style sheet). Does having the page in Roboto go easier on your eyes?

          • dL

            well, to me it looks much better. But the typography should look good. Roboto is google’s material design app/device platform font.

            Prior to Roboto, I liked Ubuntu and Open Sans. The former being the default font of the Ubuntu dist linux OS and the latter the font used at developer.mozilla.org.

            Lato is the free alternative to myriad, the adobe font used by apple.

  • MamaLiberty

    Oh me… why is it so often that the “new and improved” is simply not much improvement? Why is the text squished into the center 1/3 of the page? There is a lot of room available there, so why use only a tiny part of it? Font shape is fine, just too small… so I’ll have to “ctrl +” each time I visit. No biggie, just seems unnecessary.

    I am happy to have the videos, podcasts and so forth in their own category, since I don’t look at any of them.

    Anyway, that’s my impression after a very limited look at it. :) I’ll be back with more if needed. Thanks for all your hard work at this, Thomas. We’ll muddle through as always. :)

    • Mama,

      Hmm … the title text on the new edition is slightly smaller, but the text within the posts looks larger to me than at the old version. I may fiddle with the sizes of both, though. dL got in first with reader feedback on the font that WAS being used, which was larger and more easily readable all around (or at least seemed to to my naked eye).

      As far as the layout, the size of the story part versus sidebars is a LITTLE smaller — the main difference is that the stories are between two sidebars instead of on the left with both sidebars to the right. And on the old edition, all the stories except the one at the top were squeezed to two stories across instead of one. BUT:

      I don’t like having sidebars on both sides either. I strongly prefer right sidebars, but this theme came with the option of either one sidebar on the right, or two sidebars, one on the right and one on the left. On my “to do” list, I have plans to move to one sidebar, on the right, increasing the width of the section for stories.

      The site is GOING to get better, based on your feedback, on feedback from others, and on my ability to modify the theme (as I get older, I have more trouble retaining coding/scripting skills and have to re-learn every time I start a new project).

      • dL

        The theme uses a 960px grid, which looks fine on touch devices and small screens, but can look like a floating plank on an ocean for large Hi-res HD screens. I use a 27″ 1920×1080 HD screen, so lots of gold background around the centered content area. Probably the same issue w/ mama.

        • There’s that, and I think part of her problem was also the main content area being scrunched between two sidebars and only being given half the space that IS used.

          Once I figure out how to get it done — I thought I KNEW how, but for some reason it isn’t working — there will only be a right sidebar instead of left and right, and the content area will have been stretched to use the space once occupied by the left sidebar. I might expand the total grid a little too, after I see the results at 960. Waiting on a support request with the theme creator to find out what element I’m missing when I go through trying to get rid of the sidebar.

          • dL

            well, with css, you can accomplish that using the following rules in the theme’s style.css file:

            #sidebar-primary {
            display: none;
            }

            #content {
            width: 620px;
            margin-left: 0;
            }

          • Nope.

            I had tried something like that already (the content width/margin change and just eliminating the sidebar-primary style rule) and it hadn’t worked.

            Just tried this and it didn’t work either. It SHOULD work, but it DOESN’T.

            That’s why I finally wrote to the theme company help desk. I purchased the paid version of the theme precisely because it comes with six months of support.

            Thanks for trying to help, though. The similarity of what you proposed to what I tried tells that I was at least on the right track and not just completely out in left field with what I was trying to do. Presumably there’s a line of code/script SOMEWHERE that’s overriding the changes.

          • Aha — I figured out a way. This theme has a specific customization option where CSS can be added that will overrule the theme defaults (I had already used it to put the box around each post). I plugged your suggested code in there and now it is the way it’s supposed to be. Thanks!

          • dL

            Tom:

            You might want to also add the following media query css rule to get full content stretch on tablet and prevent horizontal scroll on phone.

            @media only screen and (max-width: 768px)
            #content{
            width: 100% !important;
            }
            }

          • I tried that in the “custom CSS” section, and it had no effect on either my phone (newest version of Android) or tablet (very old version of Android — it did have full content width on the table either way). When I looked in the theme style sheet, it did have something similar:

            @media only screen and (max-width: 768px) {

            #container, #footer-container {
            width: 100%;
            }

            In theory, this theme was supposed to come with a mobile-friendly version, which I assume is why there is an entire section in the style sheet for mobile phones. But there is definitely side-scrolling and so forth on the phone. I’m planning to:

            1) Check plugins that will redirect to a nicer mobile setup; and

            2) Put together a simple Android app — most of those run off of RSS, which used to be problematic when important stuff was in non-feed custom URLs but that stuff is now part of the regular post content.

          • dL

            i don’t see the new rule in the style sheet. You need the !important to ensure overriding an existing applied rule. if you put that rule in, I will test it for you on my devices.

          • I tried it, both in the style sheet and in the “special CSS that overrides style sheet rules” gadget. Nothing changed. So I took it back out. When I make changes that don’t do anything, I prefer to undo them.

            I’ll put it back into the special CSS section, which seems to work better. It should be there within about two minutes after I post this reply. Let me know if it does anything for you.

          • dL

            yeah, the css rule is still not showing up, which is why it is being applied.

          • I don’t understand what you just wrote.

          • dL

            sorry, “which is why it isn’t being applied.” The css rule is not in the style sheet nor in the custom filters.

          • That’s very strange. I added it and saved it, and looked at it again to make sure it had saved, but now it’s gone.

            I think I see what happened. When I try to save it now, it tells me that the brackets are un-balanced. I just removed that second closing bracket, which I was wondering about anyway.

            It seems to be sticky now — I’ve gone out and in, logged out and in, etc. and it still shows now. But I’m still seeing side scroll on my phone.

          • dL

            yeah, i see it in the style filter(injected inline as a style tag in the html), but it is not correct syntax. You need to have the curly brackets like so:

            @media only screen and (max-width: 768px) {
            #container, #footer-container {
            width: 100%;
            }
            }

            Probably have to add it directly to the theme style.css. The widget is probably not made to handle media-query injections(which applies css rules for the specified screen size).

          • dL

            sorry, i c&p’d yours from above. The media query rule should be:

            @media only screen and (max-width: 768px)
            #content{
            width: 100% !important;
            }
            }

          • dL

            hah, mine above is not syntactically correct(nor the original one I wrote). That’s probably the issue. It should be:

            @media only screen and (max-width: 768px){
            #content{
            width: 100% !important;
            }
            }

          • Implemented. I still see no change, although I did just notice that I can use a gesture to zoom the site out on the phone such that there is no side-scrolling. I didn’t notice if that functionality was there before.

          • dL

            ok, media query is now applying correctly. It stretches now to full width on tablet(portrait orientation) and no longer horizontally scrolls on phone. Tested on two android devices.

            The pinch and zoom is enabled by default. You can control that using the content attribute on a meta tag. Not a css or javascript thing.

          • dL

            note:

            tested another android phone. It does have maybe a 20px horizontal scroll on that one.

          • Thanks for all the help!

Our Sponsors