@steveSteve Bate frankly I disagree with this point. Servers should be simple. We need to move away from the paradigm of custom purpose ActivityPub servers that Mastodon pushed where the client and server are the same service.

Timelines should be orthogonal to the ActivityPub specification and, in my opinion, kept well away from it.

What's the benefit for my client application to know what your server's preferred timeline representation is?

Let's not go down the path where everything looks like a nail because we really like hammers.

@smallcircles🫧 socialcoding.. @evanEvan Prodromou

@mariusormarius @smallcircles🫧 socialcoding.. @evanEvan Prodromou I think you read something other than what I wrote. πŸ˜€. I’m describing *user-defined* timelines where the heavy lifting is done in a server. That server would be (or could be) *general purpose* and not specific to an activity domain. I definitely wasn’t suggesting a monolithic, tightly-coupled client/server architecture. I want my timeline definitions to be portable and interoperable.

0

If you have a fediverse account, you can quote this note from your own instance. Search https://social.technoetic.com/users/steve/statuses/116103229394994026 on your instance and quote it. (Note that quoting is not supported in Mastodon.)