Display

ta180m

Sat, 20 Aug 2022 14:50:47 -0700 from mastodon

I wrote a blog post about various #forge #federation myths: https://ta180m.exozy.me/posts/forge-federation-myths/

As usual, feel free to ask me questions about forge or #Gitea federation!

Hélène

Tue, 23 Aug 2022 08:23:49 -0700 from pleroma

@ta180m hello! i do have a few questions!
will you be using mostly Forge-specific activity types or will you use ActivityStreams core vocabulary? (i'm asking to know if it would be possible to interact from microblogging-related instance software (Mastodon, Pleroma, etc), for example to create or comment on issues, things like that)

ta180m

Tue, 23 Aug 2022 08:39:29 -0700 from mastodon

@Hélène we'll be using mixture of ForgeFed types and core AS types. We plan on having features like commenting on an issue with a Mastodon account, but currently Mastodon violates the AP spec by ignoring any ForgeFed types: https://github.com/mastodon/mastodon/issues/18806

Wed, 24 Aug 2022 13:42:04 -0700

Methinks you should read the spec again. Implementations are free to ignore extensions they don't know about. The spec actually recommends that if you wish to provide an extension type such as a "Frumble" that can gracefully devolve into and be displayed as a "Note" you identify it as a [ "Note", "Frumble" ]. Some projects will try and display this. If you do this backward and call it a [ "Frumble", "Note" ] or just call it a "Frumble", and we have no idea what a Frumble represents, we've every right to throw it into the bitbucket.

ta180m

Wed, 24 Aug 2022 14:58:34 -0700 from mastodon

@mike @Hélène Thanks for the correction. I'm actually not working on Gitea-Mastodon interoperability right now, and it was someone else that told me Mastodon was the problem and supposedly violating the spec. Also, Mastodon and go-ap (the AP library Gitea is using) both don't support type arrays, so that complicates any solution involving type arrays.