3 ms·

This is a remarkable landing page. Fantastic. 1. Clear problem every developer has (most don't even know !!) 2. Inform on how to solve the problem 3. Offer t

This is a remarkable landing page. Fantastic. 1. Clear problem every developer has (most don't even know !!) 2. Inform on how to solve the problem 3. Offer the convenient solution. Wow.

wwhitlow 8y ago
Yes I do think this is a tremendous PR campaign.
geofft 8y ago
It's also remarkable because it's fear-mongering. It's not a "problem," and most developers would be mad if they stopped getting credit for their pull requests in projects using a rebase workflow, which is what their "solution" would require. (See my other comment for details.)
- lisper 8y ago
  It's not just fear-mongering, it's marketing for a product. (And IMHO somewhat sleazy marketing.)
- EthanHeilman 8y ago
  >It's not a "problem," To me it is a problem and I'm glad they are pointing it out. I suspected this was possible but wasn't sure, now I know for sure.
  - lqet 8y ago
    Technically, it is the same "problem" as falsely writing "this proofs P = NP" into the commit message. It's just free text, you can put whatever you want there (as long as the email address is formatted correctly, I guess). Edit: Github actually marks verified commits in their GUI: https://help.github.com/assets/images/help/commits/gpg-signed-commit-verified-without-details.png https://help.github.com/assets/images/help/commits/gpg-signe...
    - geofft 8y ago
      I will admit that GitHub formats the commit in a way where it looks like the commit author may have been verified in some way (because it's linked to a GitHub account, and approximately no other type of online service permits posting things from an account without actually being from that account - the PGP keyservers are the only other one I can think of!), and the content of commit messages don't look like they're endorsed by GitHub. I'm not sure if there's an easy way in the UI to demonstrate unverified/verified, though. Even a small broken-lock icon would imply that something is wrong when it's not really wrong, it's just common practice for this to be entirely based on trust. Perhaps it would help to show the verified identity of the user who pushed the commit to GitHub alongside the unverified author?
      - Boulth 8y ago
        It reminded me of this interesting behavior of keyservers, that is by design but still surprising - anyone can add UIDs to any key: https://bitbucket.org/skskeyserver/sks-keyserver/issues/41/web-app-displays-uids-on-keys-that-have https://bitbucket.org/skskeyserver/sks-keyserver/issues/41/w...
- samschooler 8y ago
  It does emphasize something, that isn't a "huge" issue for some, but they way the portray it on the page, really drives their sales pitch.

This is a remarkable landing page. Fantastic. 1. Clear problem every developer has (most don't even know !!) 2. Inform on how to solve the problem 3. Offer the convenient solution. Wow.

wwhitlow 8y ago

Yes I do think this is a tremendous PR campaign.

geofft 8y ago

It's also remarkable because it's fear-mongering. It's not a "problem," and most developers would be mad if they stopped getting credit for their pull requests in projects using a rebase workflow, which is what their "solution" would require. (See my other comment for details.)

lisper 8y ago
It's not just fear-mongering, it's marketing for a product. (And IMHO somewhat sleazy marketing.)
EthanHeilman 8y ago
>It's not a "problem," To me it is a problem and I'm glad they are pointing it out. I suspected this was possible but wasn't sure, now I know for sure.
- lqet 8y ago
  Technically, it is the same "problem" as falsely writing "this proofs P = NP" into the commit message. It's just free text, you can put whatever you want there (as long as the email address is formatted correctly, I guess). Edit: Github actually marks verified commits in their GUI: https://help.github.com/assets/images/help/commits/gpg-signed-commit-verified-without-details.png https://help.github.com/assets/images/help/commits/gpg-signe...
  - geofft 8y ago
    I will admit that GitHub formats the commit in a way where it looks like the commit author may have been verified in some way (because it's linked to a GitHub account, and approximately no other type of online service permits posting things from an account without actually being from that account - the PGP keyservers are the only other one I can think of!), and the content of commit messages don't look like they're endorsed by GitHub. I'm not sure if there's an easy way in the UI to demonstrate unverified/verified, though. Even a small broken-lock icon would imply that something is wrong when it's not really wrong, it's just common practice for this to be entirely based on trust. Perhaps it would help to show the verified identity of the user who pushed the commit to GitHub alongside the unverified author?
    - Boulth 8y ago
      It reminded me of this interesting behavior of keyservers, that is by design but still surprising - anyone can add UIDs to any key: https://bitbucket.org/skskeyserver/sks-keyserver/issues/41/web-app-displays-uids-on-keys-that-have https://bitbucket.org/skskeyserver/sks-keyserver/issues/41/w...
samschooler 8y ago
It does emphasize something, that isn't a "huge" issue for some, but they way the portray it on the page, really drives their sales pitch.