Live data from Hacker News

Stop the Slow Lane

stoptheslowlane.com

21–30 of 52 posts

Re: Stop the Slow Lane

#21
post #19
post #11

Earlier quoted context omitted.

We are considering an option that blurs out the page instead. Also - we'll add more context to the page.

I think you may have missed my point there.

If we made a version that stripped out the slowdown effect and just had the action ask, would you run that?

Our impression (and experience) is that people get more excited about doing something symbolic.

Again, any direct recommendations about how to improve this, and we'll improve it :)

Re: Stop the Slow Lane

#22
post #17

perhaps it should be a button on the website, like "experience the site with FCC's Slow Lane". That way, they can see what the site is like and if they choose to press the button, they can see what it is like to be on the slow lane. Otherwise, the first time visitor may not give the site a chance at all.

If it's a site you visit regularly, it's likely to make you really curious, right?

We're making a version that's just an anigif that people can embed. That should be live really soon. So, that works for people who don't want to interrupt visitors with a message.

Re: Stop the Slow Lane

#24

Condescension is not exactly the best way to win people over to your cause.

can you tell us more about why it feels condescending?

It feels condescending because people don't really need an exaggerated demonstration of what the word "slow" means. I agree that people need to be made aware that what FCC is doing is going to make things slower for regular users, but this is excessive.

Re: Stop the Slow Lane

#25

While I understand the sentiment, this seems more likely to just encourage site visitors to hit the back button rather than take the desired action.

I disagree. If the site is somewhat heavily trafficked already (which is the kind of site that will actually have an impact), then they'll wait.

Heavily trafficked sites are already paying for a "fast lane" in the form of CDNs that cache everything but dynamic content. These CDNs already have interconnect agreements with the large ISPs (and have for years).

Re: Stop the Slow Lane

#28
Another idea is to provide a banner with a good message and a "toggle" button for the slow lane. So users can experiemnt it, but be in control as not to harm the product experience. Maybe it's too passive?

Re: Stop the Slow Lane

#29
post #19

Earlier quoted context omitted.

I think you may have missed my point there.

If we made a version that stripped out the slowdown effect and just had the action ask, would you run that? Our impression (and experience) is that people get more excited about doing something symbolic. Again, any direct recommendations about how to improve this, and we'll improve it :)

You're asking about the efficacy of passive messaging - I don't think it would work if you asked people. Likewise, I think simply doing it is more likely to annoy people than incite passion.

Visibility is the issue, not understanding the problem. I think the message of "the internet could be slower without net neutrality" is the one that needs to be delivered. People generally know what "slower" means.

As I mentioned, a standardized message would probably be more effective, but it's also not something that would be particularly exciting to share on, say, Hacker News.

Re: Stop the Slow Lane

#30
I don't think this is the right approach. I realize that the principle is fundamentally the same with SOPA protests (depriving users of content to highlight the danger of this passing), but there's a more salient argument that you could make here if you really wanted.

Why not implement a loading bar that actually progressed slowly and then put a brief explanation underneath the loading bar describing the FCC "slow lane" and how it would negatively impact users?

To add insult to injury, give the user 3 options:

- pay the site owner to access the "fast lane" to your content

- send an email (to FCC chair? maybe a representative?) to voice their anger

- get used to waiting; that'll be the new norm if nobody prevents this, right?

The first option would be incredibly controversial, but would underscore how objectionable the "Slow Lane" idea even is. If anyone is stubborn enough to pay, you could funnel that money into the EFF or some other relevant organization.

The point is that just throwing people a loading screen (especially without a good explanation) will leave the user confused. Once the content loads they'll probably forget about that loading screen anyway (at least on a conscious level), so don't wait until afterward to explain what just happened.

As an aside, there was a comment that users will wait for a website that's sufficiently highly trafficked, but I don't think that's true. I remember some Google presentation[0] where an engineer explained that virtually any extra loading time was enough to discourage users from returning. Maybe that's just with search or other highly interactive sites (rather than reading a blog, for example), but I wouldn't want to test that hypothesis with any site I cared about and managed.

0: https://www.youtube.com/watch?v=Il4swGfTOSM - The "impact of slow sites" comes up early on.

Post reply on HN