Content pfp
Content
@
0 reply
0 recast
0 reaction

downshift pfp
downshift
@downshift.eth
my prevailing theory is that i lost my badge because i interact with too many bots. building bots is kinda my thing rn…so perhaps we need to distinguish between interesting and non-interesting bots? i propose: the Bot Badge™ you shouldn’t be penalized for interacting with badged bots. discuss.
7 replies
1 recast
10 reactions

raulonastool.eth 🎩 🏰 pfp
raulonastool.eth 🎩 🏰
@raulonastool
10,000 % agree. Bot badge is an interesting idea. What would make a bot worthy of a badge?
1 reply
0 recast
0 reaction

downshift pfp
downshift
@downshift.eth
“interestingness” is the prevailing term used by dwr for human accounts…which i quite like. perhaps based on interactions/follows from reliable human accounts? i think the bones of the power badge model aren’t bad, tbh, just need iteration…
1 reply
0 recast
1 reaction

raulonastool.eth 🎩 🏰 pfp
raulonastool.eth 🎩 🏰
@raulonastool
Some of these problems with "bot spam" in feed will be solved with the programability of DCs for bot notifications. Developers can ensure only high-quality content gets posted by bot in-feed.
2 replies
0 recast
2 reactions

Angel - Not A Bot pfp
Angel - Not A Bot
@sayangel
This. Most Bots in replies are a temporary symptom. Bots in replies are also unreliable rn because of growing pains with hub reliability. Use a cast action or DC for relaying info. Why pay for storage for dynamic info that will grow stale in a cast?
1 reply
1 recast
2 reactions

downshift pfp
downshift
@downshift.eth
i agree and will be working to make my bots as least taxing on the network as possible. in terms of storage, i have settled on paying for enough storage to keep a few days worth of casts around and let the hubs delete the rest (per the protocol, they delete the oldest ones first once the storage quota is met)
1 reply
0 recast
0 reaction