Chebucto Regional Softball Club

@rimu @tchambers @julian

Neat.

@smitten_ Check it out

@smitten_ Do you know what is the status of Fedlilinks? Has it been abandoned?
FEP-07d7 was withdrawn, and other proposals have even less support than these two.

@SoniEx2 @julian @rimu @activitypub

@julian Fedilinks website lists 3 MastoAPI clients, but the list is incomplete. I saw Fedilinks being mentioned in changelogs of other clients too.

There was also an Akkoma PR, it was closed by the author: https://akkoma.dev/AkkomaGang/akkoma/pulls/589. I don't quite understand the reasoning, perhaps @smitten could clarify.

@rimu

web+ap, which was proposed by Fedilink authors. To my knowledge, it is the most widely adopted proposal

Fedi Links

(web.archive.org)

(the main site seems to be offline now)

cc @SoniEx2

@julian FEP-171b has its own way to backfill, also via context, but it is a collection of activities (such as Create).
I am currently trying to figure out how to make Containers compatible with NodeBB and others.

@julian

>Contexts can provide a thorough, comprehensive way to backfill an entire conversation. This is the biggest step we can take towards tackling the “fediverse is quiet” problem.

Sure, context is useful for backfilling, but is it the biggest step? I don't think so.

With FEP-1b12 or Containers, conversations are synced by default, so there is no need for backfilling. This is more efficient too: you don't need to retrieve context periodically to get an up-to-date view.