9 ms·

Brilliant advice. I've have been on the exact journey you described - the idea that won't leave me alone (probably 6 years old now), Googled early on to see if

by dfex 7y ago

Brilliant advice. I've have been on the exact journey you described - the idea that won't leave me alone (probably 6 years old now), Googled early on to see if anyone else had built it yet; found two existing companies pursuing the same thing, but in two different ways that don't quite match my own. I've been sitting on the idea for the last two or three years (it still won't leave me alone), and it has now evolved significantly. Fortunately, due to a rare moment of foresight, I've been keeping a journal capturing thoughts around the idea as I've had them, so I've now got a really nice record of the original concept, iterations, evolutions and adjacencies. The best part though, is that I have a record of the excitement that this idea gives me (re-kindled every time I read it), which is a great pick-me-up when the self-doubt takes hold. I am now entering my last months of employment as I ready myself to jump in and make it real!

mrb 7y ago
As an angel investor, I'm curious. If you need seed funding, email me :) My contact info is on zorinaq.com
- robertoestivill 7y ago
  May I suggest investing in an SSL certificate for your website? I find it really hard to really trust if that's your contact information ;)
  - Const-me 7y ago
    Not OP, but I don’t have certificate on my personal web site either, and I don’t think I need one. > find it really hard to really trust if that's your contact information Because Google implemented warning in their web browser, and you comply without understanding their reasons? SSL is most useful for credit cards processing. SSL makes some sense for e-mails and chat messages, also for authentication. SSL is useless for static content. I think Google did that for money, just sold the security story really well. They’re smart people, they can’t possibly be unaware of certificates being useless for majority of the web. Here’s the reasons. Increases entry barrier, centralizing internet even more. For-profit internet companies have zero issues paying for certificates, it’s part of their business. It raises barrier for ordinary people. Also creates more incentive for placing ads on their web sites to reduce costs. Guess who earns most profits from internet ads? Also, SSL breaks caching proxies by design. This opens market for technically inferior google AMP. Technically inferior, because proxies are closer to users, 20 years ago most office buildings had a caching proxy like Squid or MS ISA Server. Also, there’s unintended consequence, users learning to ignore SSL errors and proceed anyway. People processing credit cards usually know what they do, take security seriously and SSL errors there often means what it’s supposed to mean, warns about potential hacks. People implementing SSL just to shut up the google browser don’t need security, they care much less and screw up much more often.
    - mijoharas 7y ago
      > Increases entry barrier, centralizing internet even more. For-profit internet companies have zero issues paying for certificates, it’s part of their business. It raises barrier for ordinary people. Also creates more incentive for placing ads on their web sites to reduce costs. Guess who earns most profits from internet ads? Lets encrypt is one obvious thing to mention here, besides removing the cost barrier to entry it really is quite simple to set up.
      - Const-me 7y ago
        > it really is quite simple to set up I haven’t tried but I think it’s only simple is you’re willing to manually renew every 90 days. I’m not willing to. Automatic renewals are only simple for popular environments like LAMP, my web server runs Windows server with IIS and old school asp.net. I can run arbitrary native code on that server, but I don’t have GUI access to that machine. But even if it would be super-easy and automated for 100% web servers, that’s still introducing a dependency to a third-party service, for no value for audience of my web site. Just shutting up a web browser that I don’t even use myself is not a good reason, IMO.
        signalsmith 7y ago
        > [...] manually renew every 90 days That's the opposite of the design goals - Let's Encrypt is designed to be automatable. They set the expiry to 90 days precisely because they want you to automate the renewal.
        collinmanderson 7y ago
        It's probably not as nice as linux, but there are a lot of options for Windows / IIS https://letsencrypt.org/docs/client-options/#windows-iis https://letsencrypt.org/docs/client-options/#windows-iis
      - reidjs 7y ago
        It can actually be quite difficult to set up if you have a non standard configuration.
- dfex 7y ago
  Thank you for your offer. One of the advantages of holding on to this idea for so long is that it's given me time to save a bit of a runway. Hopefully the fabled Product/Market fit materialises before this runs out :)

by dfex 7y ago

mrb 7y ago

As an angel investor, I'm curious. If you need seed funding, email me :) My contact info is on zorinaq.com

robertoestivill 7y ago
May I suggest investing in an SSL certificate for your website? I find it really hard to really trust if that's your contact information ;)
- Const-me 7y ago
  Not OP, but I don’t have certificate on my personal web site either, and I don’t think I need one. > find it really hard to really trust if that's your contact information Because Google implemented warning in their web browser, and you comply without understanding their reasons? SSL is most useful for credit cards processing. SSL makes some sense for e-mails and chat messages, also for authentication. SSL is useless for static content. I think Google did that for money, just sold the security story really well. They’re smart people, they can’t possibly be unaware of certificates being useless for majority of the web. Here’s the reasons. Increases entry barrier, centralizing internet even more. For-profit internet companies have zero issues paying for certificates, it’s part of their business. It raises barrier for ordinary people. Also creates more incentive for placing ads on their web sites to reduce costs. Guess who earns most profits from internet ads? Also, SSL breaks caching proxies by design. This opens market for technically inferior google AMP. Technically inferior, because proxies are closer to users, 20 years ago most office buildings had a caching proxy like Squid or MS ISA Server. Also, there’s unintended consequence, users learning to ignore SSL errors and proceed anyway. People processing credit cards usually know what they do, take security seriously and SSL errors there often means what it’s supposed to mean, warns about potential hacks. People implementing SSL just to shut up the google browser don’t need security, they care much less and screw up much more often.
  - mijoharas 7y ago
    > Increases entry barrier, centralizing internet even more. For-profit internet companies have zero issues paying for certificates, it’s part of their business. It raises barrier for ordinary people. Also creates more incentive for placing ads on their web sites to reduce costs. Guess who earns most profits from internet ads? Lets encrypt is one obvious thing to mention here, besides removing the cost barrier to entry it really is quite simple to set up.
    - Const-me 7y ago
      > it really is quite simple to set up I haven’t tried but I think it’s only simple is you’re willing to manually renew every 90 days. I’m not willing to. Automatic renewals are only simple for popular environments like LAMP, my web server runs Windows server with IIS and old school asp.net. I can run arbitrary native code on that server, but I don’t have GUI access to that machine. But even if it would be super-easy and automated for 100% web servers, that’s still introducing a dependency to a third-party service, for no value for audience of my web site. Just shutting up a web browser that I don’t even use myself is not a good reason, IMO.
      - signalsmith 7y ago
        > [...] manually renew every 90 days That's the opposite of the design goals - Let's Encrypt is designed to be automatable. They set the expiry to 90 days precisely because they want you to automate the renewal.
      - collinmanderson 7y ago
        It's probably not as nice as linux, but there are a lot of options for Windows / IIS https://letsencrypt.org/docs/client-options/#windows-iis https://letsencrypt.org/docs/client-options/#windows-iis
    - reidjs 7y ago
      It can actually be quite difficult to set up if you have a non standard configuration.
dfex 7y ago
Thank you for your offer. One of the advantages of holding on to this idea for so long is that it's given me time to save a bit of a runway. Hopefully the fabled Product/Market fit materialises before this runs out :)