this post was submitted on 04 Aug 2023
43 points (100.0% liked)
Beehaw Support
2797 readers
1 users here now
Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.
A brief FAQ for lurkers and new users can be found here.
Our September 2024 financial update is here.
For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Although I do like the idea of having some other information outside of the spoiler, I'm of the opinion that bots should distinguish themselves with the bot flag, and no more. The message should introduce the content, rather than the bot itself, and information about the bot should go in the bot's bio.
Admittedly, I agree with you in making the footprint leaner if it can be helped. The Lemmy UI and best practices working with that would ideally handle flagging the bot and let people make informed decisions from there.
I was trying to strike a balance between keeping it lean and keeping it visible. @rikudou’s concern was that spoiler folding would lead to people missing the bot as they scanned through the comments. At least with how Lemmy UI currently is, I have to concede that I think they have a point. Last I checked on the default Lemmy UI theme at least, the Bot flag is relatively easy to miss scanning through comments. Moderator and Administrator icons are already relatively low-key, but the Bot flag currently uses the more discrete body text color and no outlining. I didn’t even know bots had a name flag until you pointed it out.
It’s a delicate balance between keeping the comment reasonably slim but also reasonably visible. I think I was trying to come up with a solution that works with the limitations as-is, but your recommendation is definitely what we ought to go with in the long-term if we can make it happen. It seems to me like it would be better to solve a fair chunk of this through the UI itself rather than bulking up the copy.