Lets add complete documentation to everything here.

Now, remember the core concepts.

Blonk is a place to find blips on the radar of your web, with a focus on vibes.

Vibes are vibes that flow with a given 'post' which is a blip. Vibes have blips on the radar. Blips on the radar
have grooves which either look_good or shit_rips.

We submit blips to vibes to get grooves for community engagement.

The radar page is the "frontpage" across all the most popular vibes.

The community gets seeded with hot_posts by watching the firehose

Vibes are created with community action by posting #vibe-your_vibe and are created once they hit a mass.

The goal of this project is to get people using it and interactive.

I thought of a critical flaw. Our posts that we are looking for replies to are totally fresh. We should actually
be sweeping chronologically to check these posts and then enrich them in a processed manner. Let's start building
out that pipeline. It will be a GenServer called HotPostSweeper that sweeps out our hot posts. We will need to
make a hot_posts table and schema, and then save all the metadata needed for them (the entire record) if they do
in fact have a link. Every 10th one. And then every 10 minutes we grab 25 links and check the replies. A link gets
checked for replies 10 times total. The checks are counted on the record. The sweeper will also auto-delete any
link that has hit 10 checks or is older than 1 day. This ensures no weird table growth there.

If we find a post with 5 or more replies, then we will have the sweeper create a blip on the hot_bsky vibe.

Does this make sense?

its failing to detect emerging vibes and we have no server logs indicating this.

that is troublesome.

we need to hash out if this firehose is even working and you are just making willy error handlers that cover important flaws in the system.

Why is it using a search to find the vibes? We should be consuming the entire firehose!

I just posted #vibe-test_post and its not being detected.

Are you sure you are monitoring the bluesky firehose for these hashtags and not something else?

I saw it come along the wire in my other firehose monitor.

lets add some constraints.
we dont want duplicate vibes to be able to be created.
we dont want to allow people to create vibes quite yet.
We are going to make a system where instead if enough people skeet a vibe as a #hashtag then we will create one if a certain threshold is hit via the firehose if they match a special form (#vibe-YOUR_VIBE) and make sure vibes must be something like YOUR_VIBE or your_vibe or YOURVIBE but not YOUR VIBE and make sure thats enforced both react client/server/atproto client level

lets just drop in react, we will need it later anyways.
let's be adults about it. make sure to use the latest, and to do whatever dan abramov would do.
He's pretty good.

Add in a basic webpage

It runs on localhost:3000

We have a classic del.icio.us look and have added some tagging features.

There is a /submit page to submit a blip

You can also filter by tag now.

Claude has added some extra fluff, let's see what needs redlined.

Let's get a system set up so that we can have a real webpage for this?

We don't want to clone the look of reddit.
We want this to feel more like the old website del.icio.us with some fun modern twists, I think.
Would you happen to have any memories of del.icio.us from the early 2000s that you can draw from here for inspiration?

Let's get a system set up so that we can have a real webpage for this?

We don't want to clone the look of reddit.
We want this to feel more like the old website del.icio.us with some fun modern twists, I think.
Would you happen to have any memories of del.icio.us from the early 2000s that you can draw from here for inspiration?

Explain everything you just made to me, thoroughly

I want to make my first atproto application.

I have no idea what I am doing.

The idea is we will start with a reddit clone.

What do we do?