buoy

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

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

Working on updating our spammy fids and adding pro users after the snap chain updates

🗽based; 

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

ty. i got over 70 of these today 😵‍💫

Ok just updated it with https://github.com/warpcast/labels/blob/main/spam.jsonl

Let’s see how it does

checked this updated label, and still see spammy users (just from the pugson screenshot), e.g.
{"provider": 9152, "type": {"target": "user", "fid": 500449}, "label_type": "spam", "label_value": 2, "timestamp": 1746237255}

or {"provider": 9152, "type": {"target": "user", "fid": 548688}, "label_type": "spam", "label_value": 2, "timestamp": 1746237258}

turns out spam labels might need another update to double check if their X accounts are suspended!