Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Many mistakes were made by Lovable that they could be berated for but on a more positive note, there is a lesson for us all: if you're doing something that you're worried about being problematic (e.g: creating a large volume of GitHub repositories) reaching out is a good thing but it is important to understand who you are reaching out to. GitHub is a huge organization, front-line support is not likely to have intimate knowledge of how exactly the acceptable usage policy is enforced nor the permission to make agreements. The key when reaching out is to find someone who has authority on the subject. Ideally, GitHub's front-line support would have escalated to the appropriate person/team but that isn't always possible (maybe they don't know who, maybe they're having a bad day and forgot). If the answer you get seems too convenient, it is probably not correct.


If I reach out and they can’t direct me to the right solution, that doesn’t seem like something I need to continue to solve for them. Seems too onerous.


If it is the critical path for your project or worse for your job, seems like that’s just due diligence.

> Seems to onerous.

I would only say that about a non-critical personal project.


Fair points




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: