bobbby.online
blonk is a radar for your web, where you follow vibes for cool blips on the radar
more readme updates and claude notes
+82
-2
+39
CLAUDE_NOTES.md
+39
CLAUDE_NOTES.md
···
8
8
9
9
## Session 4: Multi-User Aggregation
10
10
11
+
## Session 5: Vibes - Mood-Based Communities
12
+
13
+
### Why This Step
14
+
- User wanted "vibes" - groups based on feelings, not topics
15
+
- Examples: "Sunset Sunglasses Struts", "doinkin right", "dork nerd linkage"
16
+
- Revolutionary concept: organize by mood/energy, not subject matter
17
+
18
+
### Implementation Details
19
+
- **Vibe Schema**: Name, mood description, emoji, color
20
+
- **Blips belong to Vibes**: Each blip can be posted to a vibe
21
+
- **Membership System**: Users join vibes they resonate with
22
+
- **Discovery by feeling**: Browse vibes by their energy, not topic
23
+
24
+
### How Vibes Work
25
+
1. Create a vibe with a name and mood
26
+
2. Join vibes that match your energy
27
+
3. Post blips to specific vibes
28
+
4. Feed filtered by vibe shows only that mood
29
+
30
+
### Thoughts So Far
31
+
**Why This Is Special:**
32
+
- Reddit/forums organize by topic (r/programming, r/gaming)
33
+
- Vibes organize by feeling/energy/aesthetic
34
+
- Same topic can exist in different vibes with different energies
35
+
- "Sunset Sunglasses Struts" could have tech posts, but chill/confident
36
+
- "dork nerd linkage" could have the same tech posts, but excited/nerdy
37
+
38
+
**Design Decisions:**
39
+
- One vibe per blip (keeps the mood focused)
40
+
- Vibes have emojis/colors for visual identity
41
+
- Members create the vibe, not topics
42
+
- Discovery is about finding your people, not your interests
43
+
44
+
**Future Ideas:**
45
+
- Vibe matching: suggest vibes based on your posting style
46
+
- Vibe moods: morning vibes vs night vibes
47
+
- Cross-vibe echoes: share between compatible vibes
48
+
- Vibe DJ: featured curator for each vibe
49
+
11
50
### Why This Step
12
51
- User wanted to see everyone's blips, not just their own
13
52
- AT Protocol is decentralized - data lives in individual repos
+43
-2
README.md
+43
-2
README.md
···
86
86
What do you think a good implementation step here is?
87
87
```
88
88
89
-
Let's see how this pans out.
90
-
This implementation will be critical for our mental model of how we want all this to tie together.
89
+
This started off looking pretty sane, and we'll look at it more, but I had a quick piece of feedback for it.
90
+
91
+
```
92
+
lets add some constraints.
93
+
94
+
we dont want duplicate vibes to be able to be created.
95
+
96
+
we dont want to allow people to create vibes quite yet.
97
+
98
+
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
99
+
```
100
+
101
+
Now, we will see where this really goes.
102
+
103
+
I kind of really like this idea of creating them by mention velocity.
104
+
105
+
So, let's see what it has come up with now.
106
+
107
+
`looks at app`
108
+
109
+
It got the concept of seeding vibes right.
110
+
111
+
There are 6 it seeded things with.
112
+
113
+
To create a vibe, 5 people must post with #vibe-SOMETHING-OR_WHATEVER and then it will be found and counted.
114
+
115
+
Once this happens, it creates the vibe so people can post in it.
116
+
117
+
Once a vibe has been filled with blips, you can fluff blips with hell_yeah's or links_good's
118
+
119
+
However, it didn't detect my first post.
120
+
121
+
```
122
+
I just posted #vibe-test_post and its not being detected.
123
+
124
+
Are you sure you are monitoring the bluesky firehose for these hashtags and not something else?
125
+
126
+
I saw it come along the wire in my other firehose monitor.
127
+
```
128
+
129
+
130
+
'
131
+