Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Propagate software name through meta HTML tags properly #39875

Open
Quix0r opened this issue Aug 14, 2023 · 3 comments
Open

Propagate software name through meta HTML tags properly #39875

Quix0r opened this issue Aug 14, 2023 · 3 comments
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap enhancement

Comments

@Quix0r
Copy link

Quix0r commented Aug 14, 2023

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.

@Quix0r Quix0r added 0. Needs triage Pending check for reproducibility or if it fits our roadmap enhancement labels Aug 14, 2023
@joshtrichards
Copy link
Member

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

@Quix0r
Copy link
Author

Quix0r commented Aug 16, 2023

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

@joshtrichards
Copy link
Member

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap enhancement
Projects
None yet
Development

No branches or pull requests

2 participants