Added to Wikidata knowledgebase - Tarby / George Desroches III / Julian Rosewood / TarbyRocks / Bacon Mane / The Brony Jesus / Tarby's Basement:
https://www.wikidata.org/wiki/Q130355637

>>11134
>folder ipfs://QmfXweAyCTtsga2osHmsDcN5EZKo2CvnQGz7ZCCXTGMJ41 [ = http://ponypalsh4y6olziyjlswfv674utokqhz3y6beym2erqtstcgadmacid.onion:81/ipfs/QmfGiwuMqoZsYQymHXzwAR2gZKUopwP9dzEhRikM1wKXJ5/a/root/audio/music/mlp/cupcakes_music_mp3 ]
Duplicated remotely (maybe again).

>>11144
>That PNG and that TXT file didn't work so well
So it's a good think it's also in IPFS = avoids vendor lock-in, not stuck in a darker part of the darkweb in this case.

>webservers, ./..
I think I read that in IPFS's UnixFS, folders can contain "." and ".." as valid filenames or folder names. However, IPFS folders which contain "." or ".." = cursed folders. ...is what I wrote in this lost post referenced by >>11132. I have since then seen that telling IPFS's MFS to create/move/copy a file or folder to .../.. or .../. acts the same way as you would see in file systems such as ZFS and btrfs. So what I think I was reading was talking about was IPLD. And IPLD is the general system; IPFS uses an implementation of IPLD for file+folder data storage. IPLD isn't just a file+folder think, and it can work with data without it being part of a filesystem or filesystem-like thing. So IPLD can use "." and ".." as valid links or items, I guess without them meaning "current directory" and "parent directory" respectively. Octavia Melody unrelated.