[GH-ISSUE #132] limit hosts per user #123

New issue

Closed

opened 2026-02-26 09:35:50 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 09:35:50 +03:00

Owner

Originally created by @elnappo on GitHub (Jan 17, 2014).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/132

should we be able to limit hosts per user? Maybe also to prevent "spam". This could be an option on a domain only applies for non owner users. But what if a user whats more hosts than this limit, how can we implement this?

Your thoughts & ideas?

Originally created by @elnappo on GitHub (Jan 17, 2014). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/132 should we be able to limit hosts per user? Maybe also to prevent "spam". This could be an option on a domain only applies for non owner users. But what if a user whats more hosts than this limit, how can we implement this? Your thoughts & ideas?

kerem closed this issue

2026-02-26 09:35:50 +03:00

kerem commented

2026-02-26 09:35:51 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Jan 17, 2014):

i don't think there should be some specific limit.

but of course the site admin can delete user accounts (with domains) if it is considered abuse.

@ThomasWaldmann commented on GitHub (Jan 17, 2014): i don't think there should be some specific limit. but of course the site admin can delete user accounts (with domains) if it is considered abuse.

kerem commented

2026-02-26 09:35:51 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (May 28, 2014):

I am closing this for now (see previous comment) as "not needed". We can reopen in case we find a good reason to do it and a good way to determine the specific number of hosts that should be allowed per user.

@ThomasWaldmann commented on GitHub (May 28, 2014): I am closing this for now (see previous comment) as "not needed". We can reopen in case we find a good reason to do it and a good way to determine the specific number of hosts that should be allowed per user.

kerem referenced this issue

2026-02-26 10:31:18 +03:00

[PR #123] [MERGED] fixed non valid html in overview, added colspan #393