Re: SOLVED - Re: follow-up: searching a directory sub-tree.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 3/31/25 10:45 PM, Jeffrey Walton wrote:
On Tue, Apr 1, 2025 at 12:31 AM Samuel Sieb <samuel@xxxxxxxx> wrote:

On 3/31/25 7:00 PM, Jeffrey Walton wrote:
On Mon, Mar 31, 2025 at 9:56 PM Tim via users
<users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Tim:
For one like https://www.youtube.com/watch?v=-ob9LHPEaKY you can type
ob9LHPEaKY into the YouTube search gadget and it will find that clip.
And for https://www.youtube.com/watch?v=D-_qS_3KXBA typing just this
_qS_3KXBA bit into the search gadget works.

Go Canes:
If you put the full 11-character "key" in double-quotes in the youtube
search field it should work.

"-ob9LHPEaKY" worked (11 chars), but "D-_qS_3KXBA" (11 chars) didn't,
though "-_qS_3KXBA" (10 chars) does.

$ echo -n '-ob9LHPEaKY' | base64 -d
base64: invalid input

$ echo -n 'D-_qS_3KXBA' | base64 -d
base64: invalid input

$ echo -n '-_qS_3KXBA' | base64 -d
base64: invalid input

It's "web-safe" base64, so you have to translate two characters.  It
should also have a "=" at the end to make it 12 characters, but the
decoder seems to accept it anyway.  However, you're only going to get 7
bytes of binary data.  It's not something readable.

echo -n '-ob9LHPEaKY' | tr _- /+ | base64 -d | od -tx1
0000000 fb fa 92 ff 72 97 04

It sounds like you are talking about the Base64 URL encoder from
<http://tools.ietf.org/html/rfc4648#section-5>. The character
repertoire includes minus ('-') and underscore ('_').

The original Base64 encoder from
<http://tools.ietf.org/html/rfc4648#section-4> uses plus ('+') and
slash ('/').

I forgot that it was actually in the RFC. I found the info in various locations including the Mozilla docs. That's what the "tr" command in the chain is for. It converts the URL friendly characters back to the official base64 characters.

--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux