Re:Show HN: Pay-per-minute video/audio calls with WebRTC
by danieka on Saturday January 20, 2018 @08:22AM
(#16193234)
Yes, that's good feedback, thank you. As you noted we don't ban any names. It sounds like a good idea to block "special names".
Re:Show HN: Pay-per-minute video/audio calls with WebRTC
by detaro on Saturday January 20, 2018 @08:34AM
(#16193266)
https://github.com/shouldbee/reserved-usernames is a list that could be a good starting point
Re:Show HN: Pay-per-minute video/audio calls with WebRTC
by chrisweekly on Saturday January 20, 2018 @09:54AM
(#16193530)
Interesting resource.
I was surprised to see "m" as the only single-letter reserved name. Would've guessed at least "v" as well.
Re:Show HN: Pay-per-minute video/audio calls with WebRTC
by BatFastard on Saturday January 20, 2018 @10:03AM
(#16193556)
Why 'm' and 'v' ?
I haven’t tried circumventing the client-side restrictions on which characters are allowed at all, but the content shown at pages like https://eagledial.com/robots.txt makes me wonder. I don’t imagine it lets me put just anything into the page, so it’s probably not an attack vector (e.g. being able to register .well-known/acme-challenge things and get a TLS certificate for the domain, or convincing Google that you own the site via a site verification page at /google*.html), but something to think about and be careful of.
All of your “Follow Us” links have an empty href.
Angular favicon.ico.