After I started working on my own RSS reader, I started converting more and more website to RSS feeds (e.g. twitter, youtube, all news site) where I only extract interesting bits. It's faster and cleaner, not to mension no ads.
More and more sites (twitter is a major offender here) are switching off their RSS feeds because they can't control the readers. See for instance: https://api.twitter.com/1/statuses/user_timeline.rss?screen_...
The Verge's web sucks
111–120 of 137 posts
Re: The Verge's web sucks
#112Earlier quoted context omitted.
What's this about comments? Do their articles not have comments and a form at the bottom anymore?
Temporarily disabled by default but they turn them on for certain articles. They claimed this was because comments had become too negative. It is possible they are genuinely just trying to protect the mental health of their staff who are usually the targets of more aggressive comments but somehow I doubt it.
https://www.reddit.com/r/AndroidMasterRace/comments/37nw4p/i...
Re: The Verge's web sucks
#113At lot of replies to that Verge article seem to be addressing the click-bait title and not the content. The content is concerned with why an old Macbook (with comparable specs to a new iPhone) will handle the web much better than said iPhone.
Re: The Verge's web sucks
#114I wonder which kinds of proposals you would suggest. It should also cover analytics.
Re: The Verge's web sucks
#115Earlier quoted context omitted.
> I wonder if that is going to be what it takes to fix today's bloat problems: Google takes the hammer to sites that too much advertising cruft. That could get interesting: Google, using the argument that all those ad-related scripts make things slow, ranking sites with a lot of them lower than sites which don't, and at the same time hitting their competitors hard: after all, Google makes money through ads, if their…
nah, that wont work. that would surely end up in legal battle, from the ad agencies saying that Google used their monopolistic power on the search industry just to boost their analytics product.
Re: The Verge's web sucks
#116browsers themselves offered built-in mechanisms to support advertising that respect privacy & performance? I wonder which kinds of proposals you would suggest. It should also cover analytics.
Re: The Verge's web sucks
#117browsers themselves offered built-in mechanisms to support advertising that respect privacy & performance? I wonder which kinds of proposals you would suggest. It should also cover analytics.
Well, some of the proposals flip the relationship on ads. For example, rather than getting access to fine-grained personal data about readers, a marketer gets some coarse data like general location (eg. midwest US) and language. Using that, they propose a set of ads to the browser, and the browser decides which might be relevant based on what it knows about you. The browser keeps the personal data to itself, though.…
Re: The Verge's web sucks
#118I'm curious as to how that could ever be done. I feel that it's almost impossible without somehow getting user information. I feel the trend is that ads are going to continue to be tuned to people and aspects about them. Maybe fully homomorphic encryption can do that without violating privacy but that's a long way off.
> Here's another idea: Almost a year ago, I heard the notion of "Subscribe 2 Web" at Mozilla. The gist is that you're worth about $6.20 per month across publishers via advertising revenues. What if you paid that much into an account yourself every month and used a mechanism built into your browser to distribute that money? Yeah, it's micropayments, but I find it interesting that these folks came up with a specific dollar amount that doesn't sound terrible.
It exists. It's called Contributor by Google: https://www.google.com/contributor/welcome/. If anybody needs an invite please let me know.
Re: The Verge's web sucks
#119Wow. From the article, an example post on the Verge "downloaded 12MB - a little over 7MB in that is JavaScript" and a refresh of the page with things cached still downloaded 8MB again. And key here -- the article HTML content itself was 75k, the rest is ad network Javascript. (apparently over 20 different companies) I don't like tracking scripts either but why can't the ad networks get together and create a shared sc…
This is complicated because of how ad networks work and all the layers involved. We have somewhat of a standard called RTB (real-time bidding) where an exchange will see each impression and run an auction in 100ms for each ad slot and then take the winning bid and render it on the page. That was easy and efficient when it was just an image. Now ad formats have become more "engaging" and require javascript tags to run…
Alternately, a technical benchmarking-only system, where you try to identify how much their contribution is to page-load without respect to security/etc.
Re: The Verge's web sucks
#120That article gets a score of 15% on Google PageSpeed - https://developers.google.com/speed/pagespeed/insights/?url=...
It likes to yell at me that my font size is too small, and tell me to "set a legible font size". When I'm not actually setting a base font size and instead adjusting things relative to the browser's default.
Their recommendation to "fix" this is to specify absolute font sizes, which is the opposite of basically every accessibility requirement I've ever read.
Similarly, they complain that I'm not "leveraging browser caching" -- but the un-cached resource is the Google Analytics JavaScript.
It also doesn't catch the one actual user-experience-problem bug that I know about and am working to fix.
So while it's enjoyable to poke fun at someone through PageSpeed results, I'd take it with an extremely large grain of salt.