@smallcircles🫧 socialcoding.. To follow up on the discussion from yesterday, 
@evanEvan Prodromou has created a proposal for another kind of “event stream” that is not necessarily associated with *any* AP collection type (see Example 1). This is more aligned with my mental model of an event feed/stream, where a timeline^1 is the history of the feed after optional filtering and content materialization. (^1 However, the terms are often used interchangeably in the Fedi.)
@steveSteve Bate @evanEvan Prodromou
Oh, that is very interesting. I will queue this up for inclusion in the delightful fediverse development curated list.
#Datastar may be a great library to check out here, and goes further in #hypermedia approach, where #HTMX considers itself feature-complete. Datastar uses #SSE to keep the connection to the client open. The client-side JS lib that is needed is super small. In datastar apps most of the business logic lives in the backend, and it lends itself very well for #EventSourcing. The original author/co-maintainer uses it with #NATS which also serves as the event store.
If you have a fediverse account, you can quote this note from your own instance. Search https://social.coop/users/smallcircles/statuses/116108868048351727 on your instance and quote it. (Note that quoting is not supported in Mastodon.)