Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[wierd]

No no Methyl, you need to send that image through ROT13.

(Though in this case, it should probably rotate more-- say, ROT64, or ROT32.  Some whole power of 2 at least.)

[Egan_BW]

Who knew that uwuification could create something visually appealing?

[King Zultan]

If you look at that last picture you can kind of see parts of the original image.

[methylatedspirit]

No no Methyl, you need to send that image through ROT13.

(Though in this case, it should probably rotate more-- say, ROT64, or ROT32.  Some whole power of 2 at least.)

I don't think ROT-over-whole-byte is a thing, at least not as a prepackaged program in the Ubuntu repos. What I can do is Base64 encode -> ROT13 -> Base64 decode. This is the command you need (you'll need rot13 from hxtools):

Code: [Select]

base64 aurora.raw | rot13 | base64 -i -d > aurora-base64-rot13-dec.raw

And that yields:

Spoiler (click to show/hide)

It's not very interesting without the Base64 conversion:

Code: [Select]

cat aurora.raw | rot13 > aurora-rot13.raw

Spoiler (click to show/hide)

[wierd]

...

I need to make a shellscript that takes an input byte, then randomly does one of the following to it, after picking a random number to decide, then outputs the result.

Reverse the bitfield
Rotate the bitfield 1/4
Rotate the bitfield 1/2
Rotate the bitfield 3/4
Replace the byte with a randomly generated one
switch every other bit with the small-end one adjacent
switch every 3rd bit with the small-end one adjacent
switch every 4th bit with the small-end one
ignore the input byte, and return the last processed byte again

The results should be all over the place that way, but still be based heavily on the input stream. (and be non reversible. )

It would be pretty simple--  Accept an input byte from standard input, store it in a variable-- generate a random number between 1 and 9-- decide what to do using that value, then return the appropriate byte on standard output.

Call it DataMangle.sh or something.

[methylatedspirit]

-snip-

Why not just straight C (or Python, I suppose)? This feels like something that would get optimized quite well by a compiler, though I have no clue why I'm saying that. I'm sure even the Python interpreter would do marginally faster here than in Bash.

[wierd]

More easily shared; no extra toolchain.

[methylatedspirit]

I guess. But then you'll be screwing out the Windows users in the crowd (at least those who don't have WSL or Cygwin). The argument against C is fine (have you seen how gigantic MSVC is?), the one against Python less so (< 100 MB, and that's a ridiculous upper bound). Python would be cross-platform by default, assuming you stuck to the standard library and carefully picked out portable external libs. I can't imagine shell scripts being particularly fun to read or debug, but you're the genius here.

[Maximum Spin]

I guess. But then you'll be screwing out the Windows users in the crowd (at least those who don't have WSL or Cygwin). The argument against C is fine (have you seen how gigantic MSVC is?), the one against Python less so (< 100 MB, and that's a ridiculous upper bound). Python would be cross-platform by default, assuming you stuck to the standard library and carefully picked out portable external libs. I can't imagine shell scripts being particularly fun to read or debug, but you're the genius here.

Python is also awful.

[methylatedspirit]

May I know why you think it's awful? I thought it's a pretty good language myself, but keep in mind I really only use it for one-off scripting and stuff like that. Nothing performance-critical, always instances where I could afford to waste CPU time and RAM.

And in that case, which language would you prefer, then?

[McTraveller]

Why would you download MSVC? There are much smaller, lighter C/C++ toolchains you can get.  I personally use just the GCC part of MinGW (64-bit) and it you can get a fairly small package for that if you just get the binary, headers, and standard library binaries (it's much bigger if you get the source, of course).

(There is also the added benefit of not supporting Microsoft, but your mileage may vary on that sentiment.)

[bloop_bleep]

MSVC is a meme. Such a weird freaking compiler. Don't use it if it isn't wanted by your project. Just use MinGW.

[methylatedspirit]

Doesn't MSVC produce slower binaries than Clang/LLVM at -O3, nevermind GCC? Like, Clang's under a BSD-style license, the source is right there on GitHub (which M$ own), Microsoft could at least just look at what they did to get faster binaries, but I think they're suffering from not-invented-here syndrome. All they'd have to do is slap a copy of Clang's license onto their software. Right where the EULA is, where no-one will read it.

Edit: Installed the MinGW toolchain for Rust and set that as default. Bye-bye, MSVC!

[Frumple]

I flushed in embarrassment again. Did she have to point that out in front of everyone!? Locking eyes with her, I drew my knife, bunched my hair up, and in one sharp move cut it pixie-short, like hers.

[*Ding!* Congratulations! [Pretty] has reached level 94!].

 

Still staring at her, I dropped it in the fire.

“No!”

“Not the fire!”

“Arrrrrrgh!”

Small bits of flaming hair went everywhere. Whoops.

[Rolan7]

As Slowbeef and pals finish off finish off Visual Novel Book Club Season 4: Danganronpa V3, they fell into an extended Steamed Hams text adventure bit.

Timestamped, but don't listen past the bit if you don't want Danganronpa V3 spoilers.  It's pretty great and spoilers do mess with the experience.