Would like a public test account to play around with it. Don't feel like signing up.
Show HN: I built an open source event-management system
21–30 of 32 posts
Re: Show HN: I built an open source event-management system
#22Why on earth is this on front page?
Because someone submitted it to HN, and then the HN community found it interesting enough to vote it up.
Re: Show HN: I built an open source event-management system
#23Earlier quoted context omitted.
Isn't this exactly what he explained? The user has a easy toggle on their dashboard to rotate credentials - and if he needs a hand with it, contact their support for some help.
I think the parents question was why they wait for the customer to do something instead of blocking/rotating the compromised credentials once they became aware of their existence. E.g. I remember reading that Amazon even scans Github for AWS credentials proactively now, since this happened all the time.
Obviously they don't want to break their customer's production system without asking.
Re: Show HN: I built an open source event-management system
#24Earlier quoted context omitted.
I think the parents question was why they wait for the customer to do something instead of blocking/rotating the compromised credentials once they became aware of their existence. E.g. I remember reading that Amazon even scans Github for AWS credentials proactively now, since this happened all the time.
Obviously they don't want to break their customer's production system without asking.
True. It should be in the TOS that exposed api keys are subject to being revoked to prevent abuse. At least for certain services, and certain types of tokens.
Re: Show HN: I built an open source event-management system
#25Great stuff, Iyanu. You just need to perfect the UI.
I suggest the OP watch this as an example of improving UI, "Refactoring UI: Bad About":
Re: Show HN: I built an open source event-management system
#26Attention! Do not sign up!
Everyone's information is public on there with autoincrementing ID's. I am not sure if this is intended, but I didn't realize my information would be public.
Re: Show HN: I built an open source event-management system
#27Minor bug report: Edit your profile. Upload a non-image file. Enjoy the backtrace. (Only discovered because uploading an image seems to be mandatory..)
Only after signup too :|
Re: Show HN: I built an open source event-management system
#28Looks like you committed a .env file previously with some semi-private details contained within it, plus you’ve hardcoded some Cloudinary API credentials. You may want to rotate them before they’re abused by someone. Edit: oh and some database credentials & getstream.io api credentials
If anyone wants to keep secrets in a repo, git-crypt is your friend: https://www.agwa.name/projects/git-crypt/
Albeit I havent made any effort to try to fix it - its a bit hard to compile on Windows.
Re: Show HN: I built an open source event-management system
#29Earlier quoted context omitted.
Old commits are still showing the credentials. Recommend following this guide to erase your .env from all commits. https://help.github.com/articles/removing-sensitive-data-fro...
It's too late now in any case. Removing them is cute, but in terms of security credentials can only be rotated now. Removing them doesn't help when someone has already pulled that history previously.
You should still do it for future references
Re: Show HN: I built an open source event-management system
#30Why on earth is this on front page?
Because people can show their side projects here. You might be really advanced and not impressed, that's fine. There's always that set of folks who are never impressed. I wish to see more Show HN. I like to see more folks building and less talking.