buoy

i really wish someone at buoy would stop this from happening automatically

🔍 ensdata.net ✦ 🖼️ pugson.net/rfe ✦ 𝙽𝙾𝚆: design engineer @family ✦ 𝙿𝚁𝙴𝚅: @rainbow 🌈 ✦ 𝙱𝚄𝙸𝙻𝙳𝙸𝙽𝙶: @vision

suggestions:
- buoy, limit to user label (these all look like spam users given its copy and pasta)

- buoy, offer option to send notif digest 3x a day instead of with each one (user can turn on in settings)

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

building farcaster | surfing @ venice, ca | eating @ gjusta / gjelina | “lucky me, lucky mud” 🤠

Can we also just have snapchain default to remove spammy casts from the grpc streams? I don’t know a single valid use case for that. Add a flag or env to activate it because 99% of developers would just want spammy casts off @v

🗽based; 

building skeet.build 🟠;
building @buoy 🛟; 
building check.supply 🏦;

Farcaster Development Boutique @ https://dTech.vision 💜 in love with tech 🤓decentralization, fitness and oldschool rap 😎

I mean in general that screenshot is obvious :D

> Spam is subjective

look at the screenshot brother

Spam is subjective

But waypoint @christopher can do filtering for you

Or you do on consumption of the events

Just use waypoint. It’s built in the streaming client.

We’ll start adding in our labels and support others contributing their labels.