(#zbsrabq) @mckinley This is true actually and you are 100% right

(#zbsrabq) I'm worried that Yarn will become just another ActivityPub frontend. This integration threatens to split the community in two. Users of Twtxt clients without ActivityPub support won't want to follow Yarn users because they'll be engaged in conversations that are inaccessible to standard Twtxt clients. It will only force the split deeper if ActivityPub is an option to be toggled by users or pod operators.

(#zbsrabq) @prologic I see: I was speaking in the end user's perspective tho, I suppose those concerns only really affect the pod owner? And, if that is the case, giving a pod owner the ability to toggle AP integration on/off us probably good enough to mitigate those concerns?

(#zbsrabq) @prologic I see: I was speaking in the end user's perspective tho, I suppose those concerns only really affect the pod owner? And, if that is the case, giving a pod owner the ability to toggle AP integration on/off us probably good enough to mitigate those concerns?

(#zbsrabq) > It is optional as well - so if one does not want it - just not turn that feature on. If we decide that the benefits outweigh the risks and accept that differences (even though we'll do our best to bridge the gaps) -- we'll have to make "Enabling" / "Disabling" an **actual** thing. being an experimental feature flag is not enough, feature flags are designed to be short-lived until promoted, or decided against. The question then becomes more along the lines of: - Do we want a toggle for Activity Pub at the Pod level? (I assume yes) - Do we want a toggle for Activity Pub discovery at the User level?

(#zbsrabq) _And mostly whether it’s even a good idea at al, and if we should continue or not?_ I think that activitypub in yarn is a great feature! And also one of the easier ones to set up and get going. And as I said last week - I think it's a important features - and will drive adoption. It is optional as well - so if one does not want it - just not turn that feature on. I personally was missing the fact that I could not easily follow others before you added activitypub, but now I can choose to follow them, which is great.

(#zbsrabq) In other words, choosing to follow an actor does not follow the same model as Yarn/Twtxt does, where we then decide to "fetch" their feed. In fact it's the other way around, you end up telling server X that you're interested in actor Y, and servers X will then "push" stuff back to you. You can see how this can lead to some of the infamous DoS behaviours that can occur in the wild 🤣

(#zbsrabq) @marado Well, the reality is that you cannot actually control this too well. Because of the push model of Activity Pub you have to a) trust that the servers you are interacting with are both correct and not malicious and b) have to send `Undo+Follow` activities to actors you no longer want to follow (missing right now) Problem that I've found in practise however is that even for a tiny pod (used for development) I'm seeing interacting with servers I never interacted with (ever).

(#zbsrabq) @prologic to be fair, I don't really see a difference here: with the integration, users still only see the feeds they choose to read (either as a twtxt or AP), right? Or this is more a problem of the integration making the network "grow too fast"?

(#zbsrabq) @prologic to be fair, I don't really see a difference here: with the integration, users still only see the feeds they choose to read (either as a twtxt or AP), right? Or this is more a problem of the integration making the network "grow too fast"?