@pfefferle In the trackbacks.

@pfefferle -- it's not a trackback because whole threads can develop.

be careful about these decisions because they will be hard to undo and may determine the character of the product.

i chose "wait for the reader," which makes me very much want to know what the reader will look like and how can we bridge it into the rss world which is where my new reader is running.

also feedland runs in that world too of course. you could be the hub for activitypub, not just a client.

@davew @pfefferle

> it's not a trackback because whole threads can develop.

Could you expand on that? What about whole threads developing prevents it from being a trackback?

@obenland @davew UI issues!

@obenland @pfefferle

i have to think about this some more.

trackback is something i never liked in the blogosphere, because it was instantly a spam thing.

i remember the first time i saw that happening, i realized this isn't going to work.

i have a different model for discourse.

but i do like "likes" -- so that's a voluntary trackback -- and that makes more sense.

i guess i'm more confused about this today than i was the other day when I wrote that comment.

@davew @pfefferle Ha! Yeah, it's a mind bender alright!

At least the Spam aspect shouldn't be a concern with all the back-and-forth to even allow quote posts.

The way I look at it is integrating an ActivityPub concept with a blogging concept that's already familiar to WP users.