

If you have a Linux machine, have you tried poking it with file? Alternatively you may try to match the first couple of bytes against the known magic bytes manually. Other than that it’s pretty hard to say for sure without the file itself.


If you have a Linux machine, have you tried poking it with file? Alternatively you may try to match the first couple of bytes against the known magic bytes manually. Other than that it’s pretty hard to say for sure without the file itself.


Bitcoin uses two rounds of SHA256 if I recall correctly.


SHA1 has a fairly even distribution, it produces 160 bit digests, so each possible variation of a chunk will have a roughly 2-160 probability to hit your hash. Now assuming you have some insane computing device that can do an exahash per hour (that’s 1018 hashes, a lot more than any modern hardware can do), finding one would take around 1.7E+26 years. Now the funniest part. Assuming your chunk is 32KiB large (practically nobody uses such small chunks today, so it’s the best-case scenario), there are 2^(32×210×23)/2160 possible variations of the chunk that would produce your exact hash. That’s roughly 1.1E+78865 fitting chunks with only one being correct. And it takes you 1.7E+26 years to get to just one of them.
absolutely could be brute forced
Yea, I wouldn’t say that.


Picard mentioned in the other comment is great. If you want a more manual approach, on a Linux machine you can use exiftool to extract the metadata and then use that information to do whatever, e.g. organise them by folders.
$ exiftool -j 救世主.ogg
[{
"SourceFile": "救世主.ogg",
"FileName": "救世主.ogg",
"FileSize": "3.4 MB",
"FileType": "OPUS",
"FileTypeExtension": "opus",
"MIMEType": "audio/ogg",
"OpusVersion": 1,
"AudioChannels": 2,
"SampleRate": 48000,
"OutputGain": 1,
"Vendor": "Lavf60.9.100",
"PictureType": "Front Cover",
"PictureMIMEType": "image/jpeg",
"PictureDescription": "",
"PictureWidth": 0,
"PictureHeight": 0,
"PictureBitsPerPixel": 0,
"PictureIndexedColors": 0,
"PictureLength": 102126,
"Picture": "(Binary data 102126 bytes, use -b option to extract)",
"Totaldiscs": 1,
"Genre": "J-POP",
"Encoder": "Lavf60.9.100",
"Releasetype": "single",
"Album": "救世主",
"Language": "jpn",
"Date": "2023-05-07",
"Title": "救世主",
"Totaltracks": 1,
"Artist": "月詠み",
"Duration": "00:03:20.868000000",
"TrackNumber": 1,
"Tracktotal": 1,
"Disctotal": 1
}]


I don’t know, but a lot of people in this thread seem to suggest that it’s them not being a native speaker that’s the problem.
In my experience it’s actually the opposite, so many native speakers mess up things like your/you’re, it’s insane. Well, any time something is off about the English grammar on the internet, we blame the American education system.
Sometimes it’s funny, though. Like “for all intensive purposes”.


Your advice is falling on deaf ears, I reckon it’s a sentence prediction tool behind the OP account, not a human.


That’s understandable, pirating is fine, selling pirated content is totally not.
You might try contacting the person who shared those, maybe they’ll still share if you promise not to sell it.


Something like this?


I’m using it as a way to keep track of channels I like, after I find something interesting, the actual playback is handled by yt-dlp + mpv. Because I always build yt-dlp from source, it is pretty much never broken for me.
Hooray to the relentless open source devs beating Google’s puzzle games mere hours after they are released!


Precisely the reason why I’m not using Fcitx, on a touchscreen there is nothing better than flick input for Japanese.


I’ve been using it for a while, haven’t noticed the candidate box margins being weird until you mentioned it.
You can make the font for the candidate box larger to fill the unoccupied space, but that sounds like a bad solution.
It’s developer opened an issue for improving that part of the keyboard not that long ago, probably there is something in the works. You may want to voice your concerns there.
I would try various CLI tools for poking the file, see if maybe it’s some specific page that’s broken and you can drop exactly that page or if splitting it into separate pages and assembling it back would magically fix it.
Worst case you’ll at least understand better what’s wrong with the file.
I know of QPDF and stapler.
If you are going to look for other ones, be sure to find those that are not just wrappers around the ones you already tried.