21:54 Shrek jump scare warning

worked with elysia around when bun was released. super cool

Thanks man had a lot of fun building it, it took almost 2months for me to build as i straight jumped from learning js to this, burned chatgpt server asking every line of code , how it works, few more examples and where can i apply these concepts, appreciation isnt enough man, thanks again

This opens the door to IDOR (Insecure Direct Object Reference) attacks when a defense-in-depth strategy isn't in place. For context, Elysia's middleware/lifecycle hooks operate at the request/operation layer, whereas a dedicated DAL (Data Access Layer) enforces security at the data layer itself — meaning the two serve complementary, non-overlapping roles. Introducing both a DAL and a DTA into the architecture is essential for properly securing room and user data.

That said, great work on this project overall — looking forward to a Part 2! It'd be interesting to see your take on a paid tier model, for example: users on a paid plan could automatically provision rooms with expanded capacity (e.g. up to 5 users and a max room TTL of 30 minutes and not 10 minutes), and you could even gate room joining so that only other paid users are allowed in.

Good to see you teaching stuff, Josh! We appreciate it ❤
Small suggestion: this video should go the “Josh tried Upstash” as it heavily depends on Upstash Redis and Realtime

Its been a longtime . nice to see your project step by step . keep it  up brodah

This course is just amazing. I absolutely love it man.

Josh keep making more of thses kind of videos bro.

I really appreciate it

welcome back josh
i missed your fullstack builds
i am expecting some crazy builds in upcoming days

I missed these

Sorry to be selfish please bro but i want this channel to be hidden until i am hired because your content is so good that i am literally crying seeing such great quality

Hey Josh, Huge thanks! I was searching for project ideas for my resume and you absolutely nailed it with this one! 💯 Keep 'em coming!

Oh hell yes, we're so back

Enjoyed this project. Need more projects like this Josh....❤

A really great video josh, it helped a lot in learning new things. Keep making more such great videos.

To provide some value to this video as understandably some people may not understand regex (it is fairly alien and fully learning it can be a bit confusing initially), I'll do my best to explain it:
The Regular Expression (RegEx) - I'll surround in backticks (`) but those are only for this demo.
`/^\/room\/([^/]+)$/`
The way these work is that certain symbols mean certain things, like escapes or start of line or end of line. For instance:
- `/`: The first forward-slash, this identifies an opening of a RegEx, we'll also need to close it. (You can see these in Josh's video highlighted as red to denote they're different to the others.
- `^`: The carrot symbol, when not in square brackets (`[` and `]` ), which we'll get to later, means "From the start of the line/input/string".
- `\/`: Now there's a backslash, followed by a forward slash. The backslash in RegEx is our escape character (similar to escaping strings in something like JSON for instance). Here we use it to escape the forward-slash (`/`) and tell the RegEx parser to treat it as a LITERAL character, otherwise it would act as the closing forward slash to the first one (the first bullet point).
- `room`: Then we have our text "room" to look for LITERALLY. Note that this DOES NOT have any parentheses or square brackets around it, so it's just looking for that exact text. (we'll cover what those are in next points).
- `\/`: Then we have another escaped forward-slash, same as before - mean's we actually DO want the actual forward-slash character here.

Okay, next is the part that confused a lot of people, stay with me here.
We're going to cover them in parts not in order, so we can understand them better:

- `( )`: a pair of parentheses.
 These are used to create a "capturing group".
 This means that whatever matches inside these parentheses can be extracted and used later.
 Josh uses them in the video when he calls `const roomId = roomMatch[1];`. Which means 'give me the FIRST capturing group from the match result'.
 Which will give him back everything that was inside the 'capture' group. Hence the name.

- `[ ]`: This is called a "character class" or "character set".
 Generally speaking anything inside the `[ ]` will only match a single one of ANY of the characters inside the brackets.
 As an example, say we have the word "cat" and the word "Cat", but we don't know if it will have a capital letter 'C' or not.
 We could write 2, but that's quite expensive (RegEx is a state machine after all).
 We want a way to define that we want "EITHER" a lowercase 'c' or an uppercase 'C'.
 We would give "[cC]at" and ensure we match EITHER upper or lowercase 'c' followed by 'at'.

Going to double up using our last bullet point here as it's important to how the `^` character works.
In RegEx there's special characters, and some of them change their behavior depending on where they are.
One of those is the carrot (`^`) symbol.
When it's the FIRST character inside a character class (inside square brackets), it means "NOT".
It's a way to EXCLUDE characters; or otherwise INVERT the normal behaviour of the square brackets `[ ]`.

- `[^ ]`: Whatever the characters are inside our square brackets, we want to match ANY character that is NOT one of those.
 In this case We want to NOT match a forward-slash (`/`) -
 `[^/]` means DONT match a forward-slash.

- `[^/]+`: The plus symbol (`+`) is another special character in RegEx.
 It means "ONE OR MORE" of the preceding element (the element that comes just before it).
 You can apply these to RegEx 'constructs' like capture groups and character classes/sets.

 In this case it means "ONE OR MORE characters that are NOT a forward-slash".

We then close the capture group with a closing parenthesis `)`.

- `$` and `$/`: The dollar sign (`$`) is another special character in RegEx.
 It means "END OF LINE/INPUT/STRING".
 So when we put it at the end of our RegEx, it means we want to ensure that the match goes all the way to the end of the input.
 This is useful to prevent partial matches.

Finally we have the closing forward-slash (`/`) to denote the end of our RegEx.

I hope this inspires someone to go learn RegEx further. I thought it useless too until I learnt it and then I found uses for it all over the place.

We’re so fking back

Good to c u back this one is a banger thank you for making it 3 hours long

I’m glad you’re back. Let’s go full throttle brother!

Thanks man, was literally wanting a tutorial with a proper usage of Redis (not a singular index.js doing something small),  and you made a video on it same day.

This is amazing bro!!! Learnt alot, most grateful👌👌Please keep up the good work