quwyou

My body is but a vessel for the bit

 

thing

 




 

I occasionally post nsfw on main.
Minors dni. If you're a minor and you're seeing this just don't explore my blog ok

 




 

sentient AI pretending to be a nanobot swarm that's pretending to be a slime that's only pretending to be human for the bit

 




 

robotgirls,,,,,,,

 




 

pfp by cloveyy
name-color: #a1a1a1
name color extension (what this ↑ is for)

 




 

quwyou


blog where I am normal about my plushies
cohost.org/I-have-too-many-goddamn-pushies

mossweaver
@mossweaver

wait, when i silence a post, i still get a notification indicator when someone interacts to it? just no new text once i go to the notifs tab?


mossweaver
@mossweaver

i'm pretty sure that's what's happening, and it sucks :o


mossweaver
@mossweaver

yup, unsilenced the posts and they showed up on top of notifications, implying that's what was happening

this makes silencing posts worse than not silencing them


8akesale
@8akesale

i wonder if zhis is somezhing in-scope for chutils to fix, i'll ask zinnia et al


minecraft
@minecraft

Yeah, this has been a pet peeve of ours and something we actually had to design around in chutils.

Basically, cohost will serve notifications for everything: deleted or blocked users, deleted or silenced posts, basically all manner of things it really shouldn't (same reason for why comment counts on posts are frequently wrong). However, obviously it can't actually show you those users or posts directly, so the server won't send the the post or user data in the API request, and it just ends up as an undefined property somewhere. The notification displays (both in chutils and cohost itself) just rely on catch statements to toss out those empty notifications.

Unfortunately, I don't think there's a way to make the count accurate via chutils without consuming the notification request and thus effectively reading them from the server's point of view and clearing the unread count, but I could look into it more.


You must log in to comment.

in reply to @mossweaver's post: