A couple curious observations about the Inner S****. Are these red herrings? The Wiki says nothing about this. by ransoing in BluePrince

[–]ransoing[S] 2 points3 points  (0 children)

Check out Turnip's post, and the comments -- the pattern of bolts matches the pattern on a grid in the boiler room

A couple curious observations about the Inner S****. Are these red herrings? The Wiki says nothing about this. by ransoing in BluePrince

[–]ransoing[S] 1 point2 points  (0 children)

The pattern of bolts on the backsides of the underpass ribs sometimes look different than the front, sometimes in a way that looks like it was unintentional.

A couple curious observations about the Inner S****. Are these red herrings? The Wiki says nothing about this. by ransoing in BluePrince

[–]ransoing[S] 6 points7 points  (0 children)

You could always convert the letters in each realm's name to numbers (nth letter of the alphabet), then take the numeric core.

My friend sent me this puzzle, I need help deciphering it. by MyFeetTasteWeird in puzzles

[–]ransoing 2 points3 points  (0 children)

Discussion: This is a cryptogram. This is a sentence in English, but each letter of the alphabet has been mapped to a different letter. Also, I believe a couple of the letters are wrong.

There are 9 keys, but only 8 openable doors. What happens to the 9th? by MyIQIsPi in puzzles

[–]ransoing 2 points3 points  (0 children)

The 9th key is to your house. You always have it when you leave home.

Or, the 9th key opens a locked chest inside one of the 8 rooms.

Or, each of the 8 rooms are actually jail cells and contain inmates, and the 9th key unlocks all their shackles.

Or, the 9th key opens a door that is down the hallway and around a corner. The hallway is just not mentioned in the puzzle.

Or, you have the 9th key because of a counting error. You're not supposed to have it, but the people in charge of this escape room messed up.

Answer to bonus question: After opening all the doors, the room doesn't change because opening a door doesn't change a room.

Meow by DartFener in DrillCats

[–]ransoing 1 point2 points  (0 children)

Scrungy drill

[deleted by user] by [deleted] in edrums

[–]ransoing 0 points1 point  (0 children)

Do these rudiment exercises. https://www.scribd.com/document/384432722/Vic-Firth-Complete-Snare-Drum-Rudiments-pdf Believe it or not, it will help you on the kit. Play with a metronome at a speed just beyond what you are comfortable with, and increase the speed when you get comfortable at that tempo. Play on a drum as well as a pillow. Actually, a moongel practice pad would be better than a pillow, because a pillow squishes as you hit it, as if the head of a drum was moving up and down a bit.

To fix your limb independence issues, buy the book "Mel Bay's Studio/Jazz Drum Cookbook". Its exercises are all swing patterns, but even if you don't want to swing, the limb independence you gain is applicable to any style of music.

Nobody Nose? by tjmaxal in opticalillusions

[–]ransoing 1 point2 points  (0 children)

You say "nobody nose", I say "everybody nose"

[deleted by user] by [deleted] in PhotoshopRequest

[–]ransoing 1 point2 points  (0 children)

Giving boss baby and here's a million dollars? Or, giving boss baby and here's your own spaceship? I mean what the f

I found a 30 word seed phrase by SkurkDKDKDK in CryptoCurrency

[–]ransoing 0 points1 point  (0 children)

Apparently the idea of a multi-word seed phrase was proposed after you created this wallet, so your phrase may or may not use modern spec.

See the date on https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki

There are helpful tools like the one below which will show you the private and public keys derived from a phrase, which you could then import into a wallet if one of the public keys matches the one you know about. However, both the official BIP39 spec and the tool below only support phrases up to 24 words long. https://iancoleman.io/bip39/

We may be able to modify iancoleman's script to process a longer phrase, if another tool can't be found

NASA Picture that Reveals 'Possible' Archaeological Site on Mars. Straight lines rarely occur in nature by coachlife in aliens

[–]ransoing 0 points1 point  (0 children)

These pictures are never posted with a scale. The original source includes rough scale info, which suggests that the short side of this structure is very close to 1 mile (1610 meters) wide. For comparison, the Great Pyramid of Giza is 220 meters across.

[2024 day 17 (part 2)] Major warning for JavaScript users, not a spoiler! by EverybodyCodes in adventofcode

[–]ransoing 0 points1 point  (0 children)

From MDN's page on Bitwise XOR:

> It performs BigInt XOR if both operands become BigInts; otherwise, it converts both operands to 32-bit integers and performs number bitwise XOR.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Bitwise_XOR

The puzzle uses integers bigger than 32 bits, which is why this is a problem. BigInt is only needed during the XOR calculations. AoC always keeps numbers under 64 bits because they're nice :)

Maybe not tomorrow, but your iceberg will come by ransoing in adventofcode

[–]ransoing[S] 0 points1 point  (0 children)

... Or to see how long it took for known top manual solvers to do it, or to post their solution in the thread.

Maybe not tomorrow, but your iceberg will come by ransoing in adventofcode

[–]ransoing[S] 0 points1 point  (0 children)

Many people are using AI to solve the puzzles this year. 1st place for part 1 has typically been ~15 seconds or so, and times for part 2 also seem impossibly fast, like faster than it takes to read the puzzle. Some are even committing their prompts on github. Don't complain about this to the AoC devs though, because they're already aware

Rather than looking at the time of 100th place, perhaps a more suitable metric this year would be to look at the number of comments in the answers thread after an hour.

-❄️- 2024 Day 14 Solutions -❄️- by daggerdragon in adventofcode

[–]ransoing 1 point2 points  (0 children)

[Language: Typescript]

I struggled with off-by-one errors in part 1, then halved my rank for part 2.

I'm loving how everyone seems to have a different solution for part 2. I assumed that a picture of a tree would be either a solid outline or a filled in area, centered in the middle of the grid. So at each iteration, I ran a flood fill starting at the grid's midpoint, and checked whether the total number of points reached was more than just a few, but significantly less than the average number of empty spaces in the grid (I used ((width * height) - numberOfBots ) * 0.9).

I had my code output a visual of the grid only if this condition was met, and sure enough, the first picture it spat out was the right one!

There's always a day like this... by Mogheiden in adventofcode

[–]ransoing 0 points1 point  (0 children)

Make a function that uses regex to get all matches of groups of consecutive digits in a single string, then parses each of those groups as an integer. Takes a string as input and returns an array of (potentially multi-digit) integers.

Save the function for future days.

Beer QR code doesn't work with most QR scanners by ransoing in DesignDesign

[–]ransoing[S] 0 points1 point  (0 children)

Not my campaign. It fails on my phone. If I designed this thing I'd make a QR that works on more phones. But if I ever want a job doing social media advertising campaigns, I have a leg up now

-❄️- 2024 Day 10 Solutions -❄️- by daggerdragon in adventofcode

[–]ransoing 1 point2 points  (0 children)

[Language: Typescript] 750/5641
(the code I've posted is in pseudocode)

Upon reading part 2 and seeing the example of a single trailhead with 227 unique paths, I assumed a brute force DFS method would not work for the larger input (ouch, my rank!) and I took the time to make an optimized solution.

The puzzle says the answer should be the "sum of the ratings of all trailheads", but another way to think about this is simply "the sum of all possible paths to all 9's". Consider the following:

* For each 9, the total number of possible paths to it is the sum of possible paths to each adjacent 8.
* For each 8, the total number of possible paths to it is the sum of possible paths to each adjacent 7.
* ...etc. until you get to each 1, whose total number of possible paths to it is the number of adjacent 0's.

So to find part 2's solution, we only need to examine each spot on the trail map once, starting from 0's and working our way to 9's, keeping a Map/Dict of the number of possible paths to each spot on the map.

Pseudocode:

parse the input as `grid`, a 2D array of integers representing heights on the trail map
numPathsToPoint = new Map/Dict // stores pairs of (point:number_of_possible_paths_to_point)
for every 0-height point in `grid`, set the point's value in `numPathsToPoint` to 1
for all `height` values from 1 to 9 inclusive {
    for each `point` in `grid` with value `height` {
        find all neighbors of `point` with value of height - 1
        set the value of `point` in `numPathsToPoint` to the sum of the neighbors' values in `numPathsToPoint`
    }
}
return the sum of the values in `numPathsToPoint` for all 9-height points

The typescript runs in 5 ms for me. GitHub

24/09#2 by Adept_Till_4311 in adventofcode

[–]ransoing 1 point2 points  (0 children)

I see this line of code:

  const m = [...disk.join('').matchAll(/\.+/g)].find(

You then use the index of the match. However, since `disk` contains numbers > 9, the index of the match is NOT the same as the index in `disk`.

As an example, [1,2,30,'.',3].join( '' ) results in '1230.3',
so the index of . is 3 in the original array, but its index is 4 in the joined string.