3 ms·

This seems like it could be great—can I drop this into my CI workflow to find visual regressions? That's the question you should be answering. Not trying to se

This seems like it could be great—can I drop this into my CI workflow to find visual regressions? That's the question you should be answering. Not trying to sell some "self-actuated change awareness" mumbo jumbo. The video literally sounds like an infomercial for a cult. Sorry for being harsh, but it sounds like you have some cool technology which is unfortunately overwhelmed by terrible marketing.

wickedlogic 11y ago
Good feedback, thanks. I do see your pointed about CI workflow, but I think visual regressions are the current obsession and a limited use case. A very valuable and useful use case, granted. But if something like diff.io was in place in your browser, in your content publishing system, in your social networks, having it just in your CI would seem limited. Would you agree?
- morgante 11y ago
  > But if something like diff.io was in place in your browser, in your content publishing system, in your social networks, having it just in your CI would seem limited. Would you agree? No, I don't. I have about 0 interest in seeing diffs of social networks or most web pages. It might make sense in a CMS but even there I think most people are better served by traditional textual diffs. It sounds like you've found a good solution for a medium problem (preventing visual regressions) but want to expand it into a "movement."
nodesocket 11y ago
One solution would be to use an existing GitHub integration to trigger a screenshot on diff.io. Shameless plug: I'm the founder of https://commando.io https://commando.io, and we have a GitHub service that allows users to run scripts (we call them recipes) on push of a repo on servers. You could write a simple recipe in Commando.io in bash to trigger the screenshot on diff.io: http://public.recipes/Xr1eCr http://public.recipes/Xr1eCr
unclebucknasty 11y ago
>mumbo jumbo...cult...terrible marketing Meh, I don't think it's that big a deal, nor do I think the marketing is bad. You clearly understood that there was some "cool technology" there, right? And, CI is just one use case, right? Still, while the creator doesn't appear to have designed it so narrowly, you are nevertheless seeing the potential application and inquiring. I'd say that's a marketing win. Of course, with more interest and feedback, the product and message can be honed. So, maybe your feedback will help the creator, but there are better ways to communicate your opinion. Don't want to be "harsh"? Then, don't be. No need for the side commentary about cults, mumbo-jumbo, and terrible marketing. Those phrases contributed nothing to your otherwise potentially useful feedback. But, they may be discouraging early words for someone who's just poured a lot into a project.
roldie 11y ago
Perhaps you're looking for Percy [0]? Similar functionality unless I'm missing something, but more focused on the CI use case than CMS. [0] - https://news.ycombinator.com/item?id=9624673 https://news.ycombinator.com/item?id=9624673

wickedlogic 11y ago

Good feedback, thanks. I do see your pointed about CI workflow, but I think visual regressions are the current obsession and a limited use case. A very valuable and useful use case, granted. But if something like diff.io was in place in your browser, in your content publishing system, in your social networks, having it just in your CI would seem limited. Would you agree?

morgante 11y ago
> But if something like diff.io was in place in your browser, in your content publishing system, in your social networks, having it just in your CI would seem limited. Would you agree? No, I don't. I have about 0 interest in seeing diffs of social networks or most web pages. It might make sense in a CMS but even there I think most people are better served by traditional textual diffs. It sounds like you've found a good solution for a medium problem (preventing visual regressions) but want to expand it into a "movement."

nodesocket 11y ago

One solution would be to use an existing GitHub integration to trigger a screenshot on diff.io. Shameless plug: I'm the founder of https://commando.io https://commando.io, and we have a GitHub service that allows users to run scripts (we call them recipes) on push of a repo on servers. You could write a simple recipe in Commando.io in bash to trigger the screenshot on diff.io: http://public.recipes/Xr1eCr http://public.recipes/Xr1eCr

unclebucknasty 11y ago

>mumbo jumbo...cult...terrible marketing Meh, I don't think it's that big a deal, nor do I think the marketing is bad. You clearly understood that there was some "cool technology" there, right? And, CI is just one use case, right? Still, while the creator doesn't appear to have designed it so narrowly, you are nevertheless seeing the potential application and inquiring. I'd say that's a marketing win. Of course, with more interest and feedback, the product and message can be honed. So, maybe your feedback will help the creator, but there are better ways to communicate your opinion. Don't want to be "harsh"? Then, don't be. No need for the side commentary about cults, mumbo-jumbo, and terrible marketing. Those phrases contributed nothing to your otherwise potentially useful feedback. But, they may be discouraging early words for someone who's just poured a lot into a project.

roldie 11y ago

Perhaps you're looking for Percy [0]? Similar functionality unless I'm missing something, but more focused on the CI use case than CMS. [0] - https://news.ycombinator.com/item?id=9624673 https://news.ycombinator.com/item?id=9624673