@inventor @siegi @fediversereport But since the owner/administrator of admin.ch is the government, what better way to certify a new service than to make it a service.admin.ch?
Top-level
@inventor @siegi @fediversereport But since the owner/administrator of admin.ch is the government, what better way to certify a new service than to make it a service.admin.ch? 5 comments
@inventor @siegi @fediversereport So? Are you saying that doing a social.admin.ch subdomain is a good thing? I don't understand your point TBH. @Faket @siegi @fediversereport This is false. Establishing a convention may be a cool idea, but it adds nothing to security or "making anything clear". Subdomains mean nothing in terms of validation of legitimacy. @inventor @siegi @fediversereport Are you suggesting that it's not better to have a [social|mastodon|toot|whatever].admin.ch than any other random root domain? @Faket @siegi @fediversereport It makes no difference. |
@Faket @siegi @fediversereport
It is already certified by the domain. The subdomain is arbitrary and serves no purpose other than being a name for a service/server/something. The end user must only pay attention to the domain and TLS certificate for the purpose of validation of legitimacy.