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

Can we help webmasters of piped/invidious instances display their message of the day? #32708

Open
3 tasks done
mk-pmb opened this issue Jan 27, 2024 · 0 comments
Open
3 tasks done
Labels

Comments

@mk-pmb
Copy link
Contributor

mk-pmb commented Jan 27, 2024

Checklist

  • I'm asking a question
  • I've looked through the README and FAQ for similar questions
  • I've searched the bugtracker for similar questions including closed ones

Question

For some alternative frontends like piped/invidious, we currently just transform it to the original site's extractor (YouTube in this case). That's a good approach. Nonetheless, I'd like a way for those webmasters to still convey their message of the day, often a request for funding. What would be a good way to do that? Should we just check for an HTML element with class="ytdl-motd" and try to display its text in a console-appropriate way above the download progress? Is there a more standardized way for labeling such kinds of messages? (For maximum compatibility with other kinds of alternative frontends.)

Or maybe we should check for a potential text file like /meta/motd.txt? That way webmasters could craft a message specific to console clients, potentially even specific to the user agent. In case of HTTP 404 the reply could be much shorter and cheaper to render server-side, than the usual HTML page.

@mk-pmb mk-pmb changed the title Can we help admins of piped/invidious instances help display their message of the day? Can we help webmasters of piped/invidious instances display their message of the day? Jan 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant