Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

Gli ultimi otto messaggi ricevuti dalla Federazione
  • @smallcircles @steve please comment on the issue!

    read more

  • @smallcircles @steve I know what an "event bus" is but I don't think it applies here. Usually it means a global data structure that attached processes can add events to and read events from. We don't have that in ActivityPub.

    I think it's fair to say that activities are like events.

    I also like the use cases and primer.

    read more

  • @evan @steve

    The way I see it, this has the wrong stakeholder name of "ActivityPub API client developer" i.e. spec implementer, and a Home Feed is something I may want as a "Solution developer" stakeholder. In other words that library or SDK that offers me the Social API should allow me to model that.

    The user story was also brought up by Mastodon, a Microblogging solution built on top of AP (ideally).

    read more

  • @steve @smallcircles I also agree that having a separate "home timeline" and "notifications timeline" makes sense. There's an open user story for that:

    https://github.com/swicg/activitypub-api/issues/21

    read more

  • @steve @smallcircles

    That said, I think it would be great to have reverse chronological ordered collections of objects created by the actor.

    It would be nice to use `streams` like `endpoints`, as an object, and define properties like `notes`, `images`, `places` and so on off of it.

    Unfortunately the loose definition and lack of examples for `streams` makes it hard to use. It's probably better just to define them as top-level properties of the actor.

    read more

  • @evan @steve

    > I think it's fair to call the outbox the actor's 'feed'?

    The actor's event bus in a pure event based approach. 😃

    Does that break AP? Current fediverse?
    Can AP be considered an event-driven architecture of sorts (or restrained as such in a solution design)?

    I really like the Motivating use cases section of the AS specs, and the primer that sits on the W3C wiki to that. Those might be further formalized so they are applied consistently.

    read more

  • @steve @smallcircles I also agree that activities are more primary than content objects like notes and images in ActivityPub. That is by design and reflected in the name of the data format, API and federation protocol.

    read more

  • @steve @smallcircles The `inbox` and `outbox` are both sequences ordered by time. I think that should meet your requirements for a 'timeline'?

    I think it's fair to call the outbox the actor's 'feed'? It is a feed of all their activities.

    read more
Post suggeriti