News for hackers. Stuff that matters.
Re:Web Fonts Collateral Damage of Ad Blockers by dredmorbius on Sunday October 04, 2015 @01:56AM (#10326649)
Fuck your web fonts. Seriously, just fuck them to hell.

I've been online since long before the World Wide Web was a thing, and I've watched the evolution of Web design from TBL's first proposals, through background wallpapers, animated flames, multicoloured layouts, spacing pixels and table-based layouts through to the saviours that were supposed to be CSS and AJAX.

It's all been a terrible mistake.

I'm leaning to a model in which a standard set of templates exist: article page, index, gallary, catalog, search -- and the client has a set of standard (or custom) templates to view them with. Client overrides server and author.

Yes, this means putting all but three Web designers in the world out of work. Couldn't happen soon enough.

A recent discovery of mine was that the combination of uMatrix and Stylish is fantastic. As the first blocks by default all CSS, fonts, and JS, I'm given a blank canvas from which I can apply my own preferred stylings (look up Edward Morbius's motherfucking Web page for a general taste). https://ello.co/dredmorbius/post/GwGDOuSqWn91CRkQBUQeYQ

Before this it was a stable of over 1800 local stylesheets, most quite brief and/or standard, to fix common gripes.

And it's not just me. A visually disabled friend, totally blind in one eye, 20/60 vision at best with correction in the other, and generally not particularly computer literate, has endless frustrations with gimmicky websites with all the usual crap: low contrast, tiny font sizes, hard-to-read fonts, poor colour choices, content which re-renders multiple times,etc.

I just spent an hour at the local Apple store exploring various accessibility options. While there are some for Mac and iOS products, they're terribly insufficient. No way to globally set user font sizes. No way to make "reader mode" the default for either Safari or Firefox. No alternative to mouse and icon interactions in far too many cases.

And that's just the OS. The Web as a whole is many times worse.

Readability Mode for the entire Web, with a small header space for branding, would be a huge improvement over the status quo.

Re:Web Fonts Collateral Damage of Ad Blockers by 36erhefg on Sunday October 04, 2015 @02:17AM (#10326682)
I mostly agree with you. The web itself is wholly incorrectly designed, or should I say evolved incorrectly. Instead of generic content that gets modified to individual users preference, we have the inverse, every site has some special functionality/code and therefore needs a web designer. This is not only increasing complexity, but also cost. With generic web, anyone could make a web page, no coding required, and anyone could read it. You can see that there is actual demand for this, as there are emerging solutions out there that try to solve it. Unfortunately they are solving it the only way possible, by using the current web standards of building stuff on top of more stuff.
Re:Web Fonts Collateral Damage of Ad Blockers by recursive on Sunday October 04, 2015 @03:19AM (#10326777)
Generic standards are the standards of the web. You don't need to use css. You can use semantic tags. It looks very bland, as it must, since no specific design thought has gone into it.

But this will never suffice for companies that have a marketing budget. They need to promote their brand more than they need to distribute information. It's not the web's fault. And any scheme you come up with is going to suffer the same fate.

Re:Web Fonts Collateral Damage of Ad Blockers by dredmorbius on Sunday October 04, 2015 @02:23PM (#10328302)
Using generic tags and allowing clients to specify presentation is pretty much precisely where I'm headed.

For an excellent example of the first half of this, see Mark Pilgrim's excellent "Dive into HTML5". I'm referring here to the structure of the document, not the content (though that's also excellent). The document is virtually entirely bare-bones HTML5 tags, with a typical nesting depth of 2-3 elements, rarely more.

Mark has also applied an excellent (and being the exception, proving the rule that virtually all CSS sucks) stylesheet to the site. Again with a minimum of chrome and glitter.

My thought, again, is that, similar to how LaTeX offers a few basic documenbt templates, a set of standardised site semantic layouts, for which clients offer standard presentation formats, with variants for high and low contrast, "night mode", and simplified design, might be preferable.

http://diveinto.html5doctor.com/

Re:Web Fonts Collateral Damage of Ad Blockers by 36erhefg on Sunday October 04, 2015 @03:50AM (#10326833)
Don't call them the standards, if almost nobody is using them.
Re:Web Fonts Collateral Damage of Ad Blockers by recursive on Sunday October 04, 2015 @02:42PM (#10328365)
In that case, the standards being proposed can't exist based on your definition.
Re:Web Fonts Collateral Damage of Ad Blockers by nicklaf on Sunday October 04, 2015 @02:37AM (#10326708)
I just tried out uMatrix and disabled all CSS.

Am I now expected to either write, or hunt down a stylesheet for every single host?

Without the CSS, the navigation sidebar just goes at the top, which makes most sites unusable.

Re:Web Fonts Collateral Damage of Ad Blockers by dredmorbius on Sunday October 04, 2015 @01:51PM (#10328183)
I have a single stylesheet, I call "unstyled", which I apply to those sites I don't either explicitly style myself or allwo the site style via uMatrix.

I'm not claiming that the user experience of individually styling each website is preferable. I am stating that the design experience of utterly nuking virtually all sites' CSS is vastly preferable to suffering through what's shoved at me.

Using Stylinsh, I can:

1. Create a default CSS which applies to all sites.

2. Create individual stylesheets matching a specific site, or regex, or domain.

3. Create one or more stylesheets which apply to multiple sites, though those have to be individually specified.

Again: I'm not claiming that the overall result is perfect or even good, simply that, for me, with reasonable CSS chops and sufficient frustration with the status quo to care and take the effort, that what I end up with is better than what I started with, and worth the (varying levels of) effort (on a per-site basis).

The more often I use/visit a site the more likely I am to change its CSS to suit my tastes. Some site I visit only once, I'll simply leave unstyled or apply "unstyled" to it (manually).

I've posted a few iterations of "unstyled" to Pastebin, one from August: http://pastebin.com/7TRnwG78

(This may not be the most recent, system on which that lives is currently unavailable.)

Re:Web Fonts Collateral Damage of Ad Blockers by nicklaf on Sunday October 04, 2015 @02:46PM (#10328383)
Thanks for sharing your stylesheet. Skimming the code, am I not mistaken in concluding that the navigation bar will still be shoved to the top of the page?
Re:Web Fonts Collateral Damage of Ad Blockers by dredmorbius on Sunday October 04, 2015 @03:05PM (#10328430)
Since that applies to sites for which CSS is entirely disabled, it tends not to be an issue (some sites use in-line styles, causing problems).

That said, there's a separate "annoyances" CSS (which I don't believe I've posted though you might find a copy via DDG/Google) which attacks a whole slew of other gripes: headers, footers, interstitials, modals, flyovers, etc. It's very broad (e.g., [class="modal"], [id="modal"], modal, ..., with a bunch of similar patterns for annoyances. I've got to explicitly override those on selected sites, particularly where they use confirmations and other dialogs.

Re:Web Fonts Collateral Damage of Ad Blockers by nicklaf on Sunday October 04, 2015 @04:43PM (#10328741)
Thanks. It sounds like it might be more trouble than it's worth for me at this point, but I definitely appreciate the effort.

Of course, the root of the problem is that HTML is not really a good basis for implementing hypermedia.

Re:Web Fonts Collateral Damage of Ad Blockers by dredmorbius on Sunday October 04, 2015 @06:44PM (#10329109)
I forget just who it is that said this, but the problem isn't so much HTML, as that there's no single entity in the role of enforcer to require that what's posted as HTML is actually sane HTML.

It's possible to do _very_ good things with HTML, CSS, tables, and Javascript even. I've done a few things myself of which I'm somewhat proud (my CodePen, referenced earlier in this thread, carries a few examples). But, as with much else, it's possible to throw out complete crap.

And browsers will render it. They've got multiple sets of quircks and brokenness modes to deal with just such issues.

Search engines will index that crap. Hell, many SEO optimisation techniques themselves are based on abuse of HTML (keyword and other semantics stuffing).

Tools that simply say "fuck you" and stop rendering shit content, or just do what the user actually wants, would go a large step toward fixing this. Various ReaderMode tools (now on Safari and Firefox) are a key example. I'm actually using the latest Firefox for Android and it specifically addresses a number of my own key browser grips in at least part (though by no means all or completely).

Google's Chrome is actually about the worst of browsers from this perspective, it's leaning far too much in the direction of yielding full power to Web authors. Yes, it's possible to create some slick Websites in that process, but you and up with gobs and gobs of shite.

Re:Web Fonts Collateral Damage of Ad Blockers by dredmorbius on Monday October 05, 2015 @07:49PM (#10335815)
"The Web is an Error Condition" -- not an essay of its own but a comment within this one:

http://deirdre.net/programming-sucks-why-i-quit/

Honestly, I miss the days when Netscape Navigator would just halt rendering in the middle of your page, saying, “No, I will not parse any more of your shit until you fix it.”

Re:Web Fonts Collateral Damage of Ad Blockers by PhasmaFelis on Sunday October 04, 2015 @03:48AM (#10326826)
Remember when the way that you styled body text was by putting it inside the <body> tag? It just baffles me that writers and creators took one look at the no-nonsense information delivery systems of the early Web and promptly spent 20 years working their hearts out making it slower, heavier, and harder to read.
Re:Web Fonts Collateral Damage of Ad Blockers by kpcyrd on Sunday October 04, 2015 @03:15AM (#10326770)
Did you just refer to your own website in third person?
Re:Web Fonts Collateral Damage of Ad Blockers by dredmorbius on Sunday October 04, 2015 @02:25PM (#10328310)
I referred to the title and a useful search-engine keyword set. Edward Morbius strives to avoid third-person references to himself.
Re:Web Fonts Collateral Damage of Ad Blockers by Too on Sunday October 04, 2015 @03:18AM (#10326774)
Twitter bootstrap is in a way one step in this direction. All pages look kindof the same but since they all build on the same framework it's easy to customize it over and over again to get some kind of branding applied or to revert branding clientside for accessibility.
Re:Web Fonts Collateral Damage of Ad Blockers by dredmorbius on Sunday October 04, 2015 @06:45PM (#10329113)
Not familiar with that, though microformats generally, somewhat encouraged by Readability, seem like progress as well.
Re:Web Fonts Collateral Damage of Ad Blockers by Asbostos on Sunday October 04, 2015 @06:17AM (#10327109)
Yes. Somehow having a consistent look and feel is considered to be good for native apps but bad for websites. On Windows you have to make sure your controls look and behave the same as every other app or people will get lost and think it's some clunky port of an open source Linux app. On the web, somehow every designer wants to reinvent the wheel.
Re:Web Fonts Collateral Damage of Ad Blockers by pmontra on Sunday October 04, 2015 @06:40AM (#10327156)
Apple and to some extent Microsoft impose the look and feel of the apps on their platforms (desktop and mobile) but nobody has control of the web. It's just too large and decentralized. Best practices are all we have but not everybody knows them. Just check the number of pages with a light background and text of a color too light to be read comfortably, or that you can't pinch to zoom on a tablet and you need a lens to read.

Edit: check this http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3129953/ about reiventing the wheel, a horizontal scrollbar to flip pages instead of the plain vertical scrollbar of the browser.

Re:Web Fonts Collateral Damage of Ad Blockers by dredmorbius on Monday October 05, 2015 @11:09AM (#10332284)
That horizontal scrollbar is similar to the one on the Internet Archive's BookReader Web app. I find it appropriate there.

The NIH page suffers in that it doesn't scroll down, allowing for full-screen viewing on tablets such as the one I'm using. There's a permanently visible browser nav and tab bar on it, which I'd prefer to have go away. Many sites with persistent headers suffer similarly (e.g., G+).

Re:Web Fonts Collateral Damage of Ad Blockers by dredmorbius on Sunday October 04, 2015 @02:49PM (#10328392)
Google and other search providers are probably best positioned to encourage improvements in design and presentation. They've already done quite a bit of this in regards to accessibility generally and mobile and HTTPS useage. I'm hoping that they'll tackle usability and design simplicity in future.
Re:Web Fonts Collateral Damage of Ad Blockers by pmontra on Monday October 05, 2015 @02:25AM (#10330216)
I worked in a project that had to implement an ebook like ui like that. Not trivial. Why did that have to it in that site is a mystery.
Re:Web Fonts Collateral Damage of Ad Blockers by SixSigma on Sunday October 04, 2015 @03:52AM (#10326837)
I'm with you buddy. I have buttons for turning off allnthat stuff. Let me choose the font I find best, at the size my old eyes like for the device I'm using.

The arguments I've had when higher ups want the Web page to render pixel perfect to the "design". "But all renderers are different"