search

nextcloud / server

☁️ Nextcloud server, a safe home for all your data
https://nextcloud.com
GNU Affero General Public License v3.0
27.35k stars 4.06k forks source link

Propagate software name through meta HTML tags properly #39875

Open Quix0r opened 1 year ago

Quix0r commented 1 year ago

Is your feature request related to a problem? Please describe. Currently, Nextcloud does expose its name over /status.php which is very nextcloud-specific, not many software do it and maybe others have different purpose for it. Also scanning for x-nextcloud-foo in HTTP headers isn't always an option as then special code needs to be added to check that header. Sometimes it best to read the software's name nextcloud directly.

As discussed over there the software's name should be propagated at least in generic meta tags like <meta name="generator" content="Nextcloud x.y" /> or the full set of <meta property="og:*" content="foo" /> fields. Also other non-federating software like hugo and tons of web software more does this.

Describe the solution you'd like Add said <meta /> tags to the HTML "base" template. They shouldn't add much overload to the total HTML output.

Describe alternatives you've considered I guess there are not much good alternatives, as discussed in community forum /.well-known/nodeinfo should only be reachable when Nextcloud Social is installed.

Additional context The issue here is, that some people change the software's name to really fancy names (I have a list of ~360 candidates) which makes it harder to know that nextcloud is behind it. og:platform is really common to be set to the software's name.

joshtrichards commented 1 year ago

Hi @Quix0r - As a user (or the admin) of a Nextcloud instance, what problem would this enhancement solve for me?

Quix0r commented 1 year ago

It isn't for the end user, just for those who write spiders (bots).

joshtrichards commented 1 year ago

Fair enough.

I don't personally see the need for this in the core software. It doesn't seem to solve a problem for the NC user base important enough for inclusion.

Adding this through a tiny app, however, might be an option. And if an admin wants this functionality for their environment, they'd install said app (just like if they wanted /.well-known/nodeinfo to be available they'd simply install/enable one of the apps that uses it).