You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
Checklist
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.The text was updated successfully, but these errors were encountered: