(#hzwqlla) @ocdtrekkie Yes, I think you're right. That didn't click for me at first, but I think I get it now.

(#hzwqlla) @prologic ohh I see. I think the difference between the two hadn't quite clicked. So in that case why wouldn't it be possible to have an ActivityPub bridge that forced yarn semantics (so to speak)? If someone sent you a reply via ActivityPub you wouldn't see it on yarn unless you followed their feed?

(#hzwqlla) @abucci I think you are talking the user side while @prologic is talking protocol side, and that means you're talking about wildly different things.

(#hzwqlla) The more I continue on this journey, the more I'm finding myself in a position where my original instincts of integrating with a "push"-based social network like Activity Pub was and is a bad idea. You just simply cannot control shit™ 😱

@prologic It seems to me this distinction is pedantic and mostly at the server level. I have a mastodon account and I have no impression that I am being forced to read things I don't want to read. I follow the people I want to follow, I mute or block the people I don't ever want to see. It's almost exactly the same reading experience as I have on yarn--different people and content obviously, but very similar functionally speaking. I think there are other issues that are of more concern. I'd argue that mastodon gives you as an end user significantly better control over what you see than yarn does. You can mute by keyword, for instance--if you don't want to see posts about "ChatGPT" anymore, you mute that word and poof! those posts are gone. You can block individuals, or entire instances. You can mute hashtags. You can set timed mutes/blocks, for instance muting a person for 1 hour or 1 day and then having that mute or block automatically reversed. Once you learn how to use those tools, the chance you'll ever see a post you don't want to see is pretty low unless you're being actively harassed or you wade into the "federated timeline". I can't speak to the administrator tools since I've never set up an instance and played with them. Anyway, my mastodon account feels pretty slow to me, and I feel like I'm in full control of what I see--nothing at all like being shouted at. yarn, as it is, seems ripe for abuse if there's ever a large influx of potentially malicious users, because it does not have fine-grained end-user tools like these. What would you, as an end user, do if someone stood up a yarn pod full of assholes who all collectively decided to twt at you all day every day? What would your options be to stop that, which would very much feel like being shouted at? At the administrator level, I had to drop the OS and block a range of IP addresses to keep spam users from continually registering on my pod, for instance; yarn only gave me the option to manually delete them one-by-one as they popped up.

(#hzwqlla) @ocdtrekkie How in your experience (or can you bring in any experts) is this even fucking possible?! 🤔 😳

(#hzwqlla) @prologic right, right, that is concerning.

(#hzwqlla) @prologic Interesting. I think I interacted with that user today?

(#hzwqlla) @abucci What do you mean by "pedantic" exactly? > What would you, as an end user, do if someone stood up a yarn pod full of assholes who all collectively decided to twt at you all day every day? Right now (without Activity Pub) I wouldn't know. It wouldn't hurt me, I don't follow those "assholes", I don't have to. I don't pull their feed(s). However (which is the point ) if I have Activity Pub integrated and turned on, I have no choice now. Those same "assholes" can send me shit all day, every day, and there isn't anything I can do about it. My options then become to administratively block them at the server or OS level. What if I don't have administrative control?

(#hzwqlla) @abucci As an example of the type of problem I'm seeing (even at small scale, and it's only been a few weeks of things working): My pod has been posted this `Create+Note` from an Activity Pub actor that no-one here seems to follow: ``` $ bat https://twtxt.net/api/v1/debug/db "Token:$YARND_TOKEN" | jq -r '. | map_values(@base64d) | {Key: .key, Value: .value | fromjson} | .Value.Following | select(. != null) | .[]' | sort -u | grep -i VaporMarxPlus | wc -l 0 ``` From This is terrible 🤦‍♂️ I don't trust the protocol at this point.