How about email? Form runs on your (anything) -> creates a new email -> you get instant email notifications because it's an email. That's also perfect for MVPs, landing pages, portfolios or any low-volume use case. Why would I want to rely on a middleman or version control software for this? If you know it's a glued-together solution that you'll have to rip apart if your program scales, why make it so complex in the…
How do you send an email from your static page?
Show HN: GitForms – Zero-cost contact forms using GitHub Issues as database
11–20 of 31 posts
Re: Show HN: GitForms – Zero-cost contact forms using GitHub Issues as database
#12GitHub is not Git. This doesn't really have anything to do with Git at all. This shouldn't be called GitForms. The Git trademark policy says they don't want people to name things like this. > you may not use any of the Marks as a syllable in a new word or as part of a portmanteau (e.g., "Gitalicious", "Gitpedia") used as a mark for a third-party product or service https://git-scm.com/about/trademark >
> (e.g., "Gitalicious", "Gitpedia") GitHub, GitLab, Gitorious (now gone)... I agree in general, but I think this ship has sailed a ways out to sea already. I don't think essentially anyone thinks "GitThing" is "git's official Thing".
Re: Show HN: GitForms – Zero-cost contact forms using GitHub Issues as database
#13Your landing page makes a lot of claims that are not true - that the code is 100% mit licensed (it's not) - that this is in any way gdpr compliant (there are literal rules around this) - that your data is encrypted and private (it isn't encrypted? Unless being written in Italian is encryption now?) - that they'll have 99.9% uptime (there is no SLA for vercel hobby tiers) - "No middlemen. No third-party storage. Every…
Re: Show HN: GitForms – Zero-cost contact forms using GitHub Issues as database
#14It seems like you want to make this into some kind of viable business, and I don't mean to dissuade by any means, but this was a three-day project by a perfectly good guy, but one guy, extremely junior, that I was tasked with training on basic networking and systems administration duties. I don't want to speak ill of the man. I liked him a lot, but he was extremely hard to teach, could not seem to understand even the bare basics of how computers and the systems they collectively form when networked operate. But he could make this exact application, on his own, in a matter of days, before LLMs were a thing.
Not saying you can't manage it, but this is like trying to sell people sandwiches. Plenty make businesses doing exactly that, but you either need a captive audience or really good sandwiches, because most of the time anyone who wants one can make it themselves pretty easily.
Re: Show HN: GitForms – Zero-cost contact forms using GitHub Issues as database
#15Re: Show HN: GitForms – Zero-cost contact forms using GitHub Issues as database
#16Re: Show HN: GitForms – Zero-cost contact forms using GitHub Issues as database
#17How about email? Form runs on your (anything) -> creates a new email -> you get instant email notifications because it's an email. That's also perfect for MVPs, landing pages, portfolios or any low-volume use case. Why would I want to rely on a middleman or version control software for this? If you know it's a glued-together solution that you'll have to rip apart if your program scales, why make it so complex in the…
You can utilize any mailing library in your backend to simply send emails or choose API email providers like Resend or Mailgun.
For spam protection, various providers are available, such as Cloudflare and Google.
> why make it so complex in the first place?
You're completely justified in questioning this, and I resonate with you and all the developers who feel the same way.
Re: Show HN: GitForms – Zero-cost contact forms using GitHub Issues as database
#18Glad to see someone executing on this, and I love how descriptive the landing page is.
Re: Show HN: GitForms – Zero-cost contact forms using GitHub Issues as database
#19Earlier quoted context omitted.
> (e.g., "Gitalicious", "Gitpedia") GitHub, GitLab, Gitorious (now gone)... I agree in general, but I think this ship has sailed a ways out to sea already. I don't think essentially anyone thinks "GitThing" is "git's official Thing".
Now that's an oversight! Since the Git project holds the trademark here, they better make sure they do what trademark holders do and have licensing arrangements in place with GitHub and GitLab regarding their use of the trademark. After all, how could anyone even begin to think about the existence of a trademark policy without taking these two obvious examples into account?
But it's a trademark, and trademark law in the USA is pretty constrained by "will an ordinary person likely be confused" and I can only come up with "probably not" counter-examples in enormous quantities (git-lfs? there are tons of git-prefixed things out there). Git™ is just used with git itself, in practice, and I've never seen anything else Git™-branded-and-prefixed by SFC that changes that.
I'm sure there's probably a court case or N that would make this a lot more clear, but it seems like a fairly safe established pattern in the industry, though it's best to respect SFC's request.
Re: Show HN: GitForms – Zero-cost contact forms using GitHub Issues as database
#20How about email? Form runs on your (anything) -> creates a new email -> you get instant email notifications because it's an email. That's also perfect for MVPs, landing pages, portfolios or any low-volume use case. Why would I want to rely on a middleman or version control software for this? If you know it's a glued-together solution that you'll have to rip apart if your program scales, why make it so complex in the…
How do you send an email from your static page?