I fear that I led you off a bit, because you're no more referencing/considering the first block of numbers. Remeber "It looked somehow familiar". The first solution is not required for the second. This does not mean, that you can/should ignore part one.
so, the only one that uses a single "character set" is the last one. There's nothing common to all of them, or even to any two of them, that can be attributed to anything more than coincidence.
Closest I get is:
█░░█░███░█░░░░░█░███░░░█░░░░░███░███░█░█░░░██░░█
░░░░░░░█░░░█░█░░░░█░░░██░░█░░█░█░█░█░█░█░░░██░░█
░░░█░██░░░█░░█░█░░█░░█░░░██░░░██░░██░█░█░░█░░███
░░██░█░█░░█░░░█░░░███░░░░██░░█░░░█░█░██░░░░██░░█
(there may be other character sets, but I don't think so - also, I don't know what might be considered 'extended' wrt georgian or armenian or korean the way that the latin and cyrillic ones are extended. I'm doing this all by eyeballing it)
I think the first line becomes this when all the non-english characters are translated: yuddaeaauthrасvehrnlkaetnrngjnoatingbuoawmonoceaoеarinogjjхthelhebjsрeraaduareisthaattitisapy
Jon - but pretty sure we shouldn't be converting any of this, anyways, from what he said earlier. Just trying to figure out what he meant by looking at the first part, since that's what we did to solve that part. --- other than the scrambled letters
The only other thing I could think of was trying to change those letters into numbers, using the phone - but we'd only be converting the first half of the numberset
korean, georgian, and armenian are (effectively) unique, but cyrillic and latin could be a lot of things, especially with the 'extended' characters. and there aren't any languages (that I know of, at least) that use all of the extended latin characters in the puzzle.
(some native american languages are written with extended latin characters, but chances are slim that knowledge of native american languages is necessary for this puzzle, unless our boy @JonathanAllan is an ethnographer playing a hella mean trick on us)
Having independently worked out how to solve the cube a long long time ago, I would say it is definitely possible without a prescribed algorithm or plain luck. The only thing one really needs to understand is commutators and, speaking from experience, one does not need to be shown the idea to rea...
(I resisted the urge to write "in a galaxy far far away")
but I was under the impression we were still talking about, effectively, grown adults who already knew how to solve one "correctly" trying to essentially create their own algorithm
And they used variable.translation - I asked why not use variable.translation.translation.translation.translation.translation for as much good as that did
Question: Can I put a (non expiring) bounty on real world "Unsolved Mysteries" questions to try to make people working on them or at least share their ideas?
This is a list of unofficial, deadline-less (hence not searchable) bounties offered by users on various challenges on the main site.
Disclaimer: There is no guarantee that the user will award the bounty for you in case you fulfill its requirement. Especially if the user isn't an active member an...
Can't we show this bounties aside the question? I did know of this. I think that this won't make people work on the questions, if they don't find this very meta post.
Yeah, my only real usage of it was to create a design-time view provider (that included support for unity) so that the viewmodels could be seen during design time in their containers, which isn't possible with prism's default setup, due to the AutoWireViewModel.
Yeah, I use prism to help make viewmodel classes that you can bind to views with, but thats about it. I don't really use unity unless it was already built into the app i'm working on, otherwise I roll my own dependency injection (since my apps are usually small)
Heck, I keep getting an error stating that it can't find any of the classes that are being used in the xaml (though it builds and executes correctly), and the only solution is to change the program from x64<->x86, rebuild, and switch it back, and rebuild again
I keep having to do that every few hours, when the xaml viewer stops working.