How hard would it be to set up a backend payment service to receive $$ for gifts?
Show HN: Open-sourcing my wedding website on my first anniversary
201–208 of 208 posts
Re: Show HN: Open-sourcing my wedding website on my first anniversary
#202Nice to see a fellow Odiya trending on HN. :)
Re: Show HN: Open-sourcing my wedding website on my first anniversary
#203Congrats! Thanks to this I made happy mood from morning.
Re: Show HN: Open-sourcing my wedding website on my first anniversary
#204Re: Show HN: Open-sourcing my wedding website on my first anniversary
#205Earlier quoted context omitted.
I don't think we do it "to impress", but rather to "not disappoint".
That's even worse. I was giving them more credit but maybe you're right. The wedding industry thrives by sowing the idea of a perfect and unique wedding into the minds of little girls and later some man will come along and fulfil that dream.
There is so much you wouldn't do for yourself but do for the ones you love. That doesn't make it insane or just to not disappoint. You do it because it makes you happy to see them happy. If you would do the same if you were alone is not the thing that matters here.
Re: Show HN: Open-sourcing my wedding website on my first anniversary
#206Adorable. My best to you both.
Re: Show HN: Open-sourcing my wedding website on my first anniversary
#207Hey I'm trying to RSVP but it's rejecting my invite code :-( Dude, excellent work on that site by the way. It's incredible, really.
Re: Show HN: Open-sourcing my wedding website on my first anniversary
#208Earlier quoted context omitted.
Yes, I found it extremely helpful too. You can only RSVP if you have the invite code. If you don't then you can't RSVP. You can store the code in a particular box in the sheet and then your google script can validate the code entered by the guest.
You are checking the invite code in the browser side js. That doesn't keep any tech-savvy user from registering even without code. Is this correct?
However, due to timing constraints, I couldn't do this and instead used a simple encryption algorithm to have the hacker at least put in some effort to know the invite code :)
I will raise an issue on github for this.