[wonderous]

For mobile users [1], quote above:

“On July 27, we reached out to Bountysource in response to a complaint we received from a user. During our investigation and discussions with members of your team, we found that your organization does not have a mechanism for responding to removal requests from users, which is required by our Terms of Service. Specifically, Bountysource does not 'respond promptly to complaints, removal requests, and do not contact requests from GitHub or GitHub Users.' Over two months later, you have not made any changes to your platform in response to our requests.

Therefore, we have suspended your application until you create a process for actively responding to all personal information removal requests, including those related to projects and issues. In order for us to remove the suspension, we would ask to see two things:

1. Confirmation from you that you have a process in place for responding to takedown requests about all areas of your website.

2. Inclusion of a public notice to your users stating how to request the removal of information. That notice can be included in your documentation or other legal notices.

Once you have that process and public notice in place, we'll be happy to review your site and consider lifting the suspension.”

[1] Please don’t use CODE-SNIPPET formatting to quote text, it is unreadable on mobile.

[jordigh]

> Please don’t use CODE-SNIPPET formatting to quote text, it is unreadable on mobile.

I don't use mobile, can you show us what does it look like? Is there a maximum width that works?

HN doesn't offer a lot of markup and indenting text for monospacing is about the only tool that they offer for code snippets.

[bastawhiz]

It sets a maximum width with scroll, so text is clipped horizontally. That requires you to scroll back and forth for each line.

[haikuginger]

It looks like this:

https://i.imgur.com/6Zw2fyr_d.jpg?maxwidth=640&shape=thumb&f...

[rasz]

rotate 90 degrees

[jordigh]

So, it looks like if I set my fill-width to 25 columns, I can still use this and make it readable to pocket computers, right?

[throwanem]

At the cost of making it hard to read on desktops, yes. Or you could just, you know, use the leading > style and not have to worry about it the more...

[zaarn]

You should generally not assume a text is readable because it uses x-wide columns.

At 25 character columns it will also look rather awful on desktop or widescreen monitors.

Borrowing from email etiquette I find using > arrows to be most indicative of quotes, although HN sometimes eats newlines for breakfast.

[jordigh]

But if short lines are readable on one screen, surely short lines are also readable on another screen, right? It's not like eyes depend on the width of the screen, just on the width of the line.

[zaarn]

Using short lines on a screen too wide leads to wasted screen space, usually people dislike that, it interrupts the reading flow.

Same for too wide lines.

The ideal length of a line is somewhere between 50 and 70 characters.

Readable != Good Writing

This is not an issue if you don't use codeblocks, the browser is then free to reflow the text as necessary. If you use codeblocks the browser cannot reflow (by default) and you make the entire UX worse.

[styfle]

Where can I find the formatting syntax for Hacker News? Clearly it's not markdown :P

[couchand]

https://news.ycombinator.com/formatdoc

[zaarn]

I think just using markdown gets the point across sufficiently.

The HN format captures the most important parts of MD; italics, code and ALL CAPS.

[kbrosnan]

Using your browser's responsive design tools should be able to display the problem.

[nwah1]

Seems like this is just a bug that HN should fix.