Gli ultimi otto messaggi ricevuti dalla Federazione
-
@evan@cosocial.ca okay, I'll see you there!
-
@deadsuperhero @general @julian yeah, I think custom timelines are great. Some good issues in here on the topic:
-
@deadsuperhero imho, building out c2s will allow new projects to bootstrap the front end, and focus on new application domains, or support multiple activity/object types.
-
@deadsuperhero I don’t necessarily think we need the big players. Especially where those projects have stated their intent to stick to micro, or photo -blogging, with limited interop.
-
On the other hand, however... If the ActivityPub API were used in an S2S context, enabling something like NodeBB to send activities on behalf of a Mastodon user, then it wouldn't matter that there is no GET /timeline, because all you need is POST /outbox and the Mastodon API handles their end.
Vice versa, NodeBB would use its own API to render a /world feed.
-
@julian@activitypub.space @general@activitypub.space @evan@cosocial.ca Again, this is sort of why I'm advocating for supporting timelines as a concept in the ActivityPub API. Instead of repeatedly parsing the inbox, we could do exactly what you're saying with some kind of representation of a timeline. Even if it's just plain old algorithmic time-sort.
-
Does the inbox have to map to a timeline, specifically? Mastodon called this out as being difficult to do because you would have to real-time parse the inbox every time you wanted to load the timeline.
Of course one could always reduce the inbox into a single timeline and serve that instead, but then we're braching out with our own proprietary APIs again.
Is that ok?
-
@evan@cosocial.ca Yeah, I mostly agree with this. It's just that the buy-in is a little bit of a chicken and egg problem. You need servers to adopt it, but you need a compelling first mover. Bonfire, maybe?
The spec definitely needs love, too. I think one of the harder things is building a timeline out of inbox activities. I feel like maybe a future version of the API could specify timelines somehow, whether it's an endpoint or some kind of basic query? Maybe there's even a way to implement alternative timelines at that level?
These are all just guesses on my part, but I feel like this could be a gateway to universal custom feeds.
