Pong. @mox@lemmy.sdf.org , in sublinks, the federation services are entirely separate from the API of the instance. So much separate, the federation services are written in a programming language called Golang. The API service is written in a programming language called Java.
One aspect does not require or preclude the other with Sublinks.
Will it federate with Lemmy? I would miss you folks.
It’s my understanding that it will…I believe that’s, also, what it means when they (Sublinks developers) said it would be “Lemmy compatible”.
That could also mean client API-compatible, so Lemmy apps would work with it, which doesn’t address federation.
Maybe so. We should, probably, ask @Penguincoder@beehaw.org about this.
Pong. @mox@lemmy.sdf.org , in sublinks, the federation services are entirely separate from the API of the instance. So much separate, the federation services are written in a programming language called Golang. The API service is written in a programming language called Java.
One aspect does not require or preclude the other with Sublinks.
Indeed, protocol is independent from implementation language, but that isn’t the question at hand.
Do you know whether Beehaw will still federate with the lemmyverse (and therefore the rest of us) after moving to Sublinks?
The current aim of Sublinks is Lemmy parity for V1 release. So yes, I do see Beehaw still federating with Lemmy instances at the on-set.
Thanks for clearing that up!