deadsuperhero@social.wedistribute.org I'm of the opinion that a solid collection of links is the easiest way to get there. FediDevs set out to do that but I think the best approach would be to update ActivityPub.rocks with the links and docs instead. Join the WG for it!! Led by evan@cosocial.ca and j12t@j12t.social

pumpkindrama@reddthat.com NodeBB supports topic based following, because it's a forum and that's literally how it was done way back then. You can follow tags as well.

benpate@mastodon.social honestly whatever you ramble on about is always a good show. Stoked you're presenting!

Yes. When the reply is posted to C, it is sent to A. A then sends as:Announce to C, as well as any other communities that follow it. B seems to be irrelevant here.

silverpill@mitra.social I wasn't aware that there were sections pertaining to context. I'll have to review more closely.

tchambers@indieweb.social this, in a nutshell. The fediverse vid AP can support both A and B, and we can wax poetic about how one is superior to the other but both are legitimate UX decisions by their respective software stacks. I prefer B myself, of course. cc tommi@pan.rent j12t@j12t.social

Thanks! It's something that I personally feel is more performant and future proof for other important things like private discussions (which Mastodon also doesn't support natively yet — mention spamming doesn't count.)

I think the FEP process is overly complicated for what it is, but it's definitely helpful if you have multiple implementors on board. The easiest (but least accessible) solution is to document something on your own site, but that lacks the social proof that a finalized FEP has. Just some food for thought I'm looking to create an FEP for cross posting and would love to get the entire threadiverse dev community involved.