7 ms·

Explanation in this comment: https://github.com/bountysource/core/issues/1147#issuecomment-345923247 https://github.com/bountysource/core/issues/1147#issuecomme

Explanation in this comment: https://github.com/bountysource/core/issues/1147#issuecomment-345923247 https://github.com/bountysource/core/issues/1147#issuecommen... 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. Sounds like it's (hopefully) not permanent.

wonderous 9y ago
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 9y ago
  > 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 9y ago
    It sets a maximum width with scroll, so text is clipped horizontally. That requires you to scroll back and forth for each line.
  - kbrosnan 9y ago
    Using your browser's responsive design tools should be able to display the problem.
  - haikuginger 9y ago
    It looks like this: https://i.imgur.com/6Zw2fyr_d.jpg?maxwidth=640&shape=thumb&fidelity=medium https://i.imgur.com/6Zw2fyr_d.jpg?maxwidth=640&shape=thumb&f...
    - jordigh 9y ago
      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?
      - zaarn 9y ago
        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.
        9y ago
Sir_Cmpwn 9y ago
As someone who does not want BountySource involved in their open source projects, I applaud GitHub for this move. IMO BountySource is a borderline bad actor. It was a pain in the ass to get them to remove my projects from their platform and then they only "sort of" did.
- MadcapJake 9y ago
  Would you care to elaborate on "borderline bad actor"?
  - Sir_Cmpwn 9y ago
    I did, in my original comment, immediately following the accusation.
    - openasocket 9y ago
      Do you mind linking to it? I tried digging through your comment history to find it and couldn't.
      - Sir_Cmpwn 9y ago
        Is this a joke? The third parent of your comment. https://news.ycombinator.com/item?id=15747940 https://news.ycombinator.com/item?id=15747940
        jpeterman 9y ago
        He said ELABORATE, "to develop or present in detail". Your explanation for them being a "borderline bad actor" is sparse to say the least.
        openasocket 9y ago
        To which MadcapJake responded "Would you care to elaborate", and you responded "I did, in my original comment, immediately following the accusation." I assumed that meant you had made some other comment earlier that explains your complaint in more detail. Did you mean by that that you had just edited your original comment? I'd really like to hear some more detail. I've not heard of BountySource before today, I thought you could go into detail on what you had to do to get your stuff off their site and whatnot.

wonderous 9y ago

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 9y ago
> 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 9y ago
  It sets a maximum width with scroll, so text is clipped horizontally. That requires you to scroll back and forth for each line.
- kbrosnan 9y ago
  Using your browser's responsive design tools should be able to display the problem.
- haikuginger 9y ago
  It looks like this: https://i.imgur.com/6Zw2fyr_d.jpg?maxwidth=640&shape=thumb&fidelity=medium https://i.imgur.com/6Zw2fyr_d.jpg?maxwidth=640&shape=thumb&f...
  - jordigh 9y ago
    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?
    - zaarn 9y ago
      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.
      - 9y ago

Sir_Cmpwn 9y ago

As someone who does not want BountySource involved in their open source projects, I applaud GitHub for this move. IMO BountySource is a borderline bad actor. It was a pain in the ass to get them to remove my projects from their platform and then they only "sort of" did.

MadcapJake 9y ago
Would you care to elaborate on "borderline bad actor"?
- Sir_Cmpwn 9y ago
  I did, in my original comment, immediately following the accusation.
  - openasocket 9y ago
    Do you mind linking to it? I tried digging through your comment history to find it and couldn't.
    - Sir_Cmpwn 9y ago
      Is this a joke? The third parent of your comment. https://news.ycombinator.com/item?id=15747940 https://news.ycombinator.com/item?id=15747940
      - jpeterman 9y ago
        He said ELABORATE, "to develop or present in detail". Your explanation for them being a "borderline bad actor" is sparse to say the least.
      - openasocket 9y ago
        To which MadcapJake responded "Would you care to elaborate", and you responded "I did, in my original comment, immediately following the accusation." I assumed that meant you had made some other comment earlier that explains your complaint in more detail. Did you mean by that that you had just edited your original comment? I'd really like to hear some more detail. I've not heard of BountySource before today, I thought you could go into detail on what you had to do to get your stuff off their site and whatnot.