is there any plan to keep contributing various fixes/improvements that the Chapo devs implemented to upstream Lemmy? Or you all just in wholesale fuck it mode? Even deprioritized, there's probably code they can use/learn from to help
what're the plans regarding federation? Does TS have libs for handling ActivityPub, or you all starting to work on your own?
I'll give some tldr answers here but if you check my comment history on this post theres more involved answers-
1 - Some of us personally have/still and will continue to contribute upstream. The amount of code we share probably isnt as much as it seems, upstream sometimes requests frequent changes to what we do so it's never been as simple as "pull request it" and we have several proposals on their github still that are in various progress states. Ideally the rewrite makes it easier for this to happen- it will be quicker to implement an idea in Typescript, vet it against a large lemmy instance (ours) and propose it upstream or rewrite it in Rust, than it would be to write it in rust "our way" then have to rewrite it again anyways.
2 - Federation is still a core goal. There are some TS libs but none we've carefully vetted. For the initial "v1" state we might end up working on our own because Lemmy's websockets kind of tightly tie into how they use apub and we already have to port the ws code there
Ok, rad. That's basically what I was hoping to read (and actually reading the original post on something bigger than my phone, I can see where my questions were basically answered).
Some of us personally have/still and will continue to contribute upstream
This is really good to see and probably helps with the image of the community that you're not just cutting and running from upstream.
Federation is still a core goal
I'm really eager to see where this ends up. I've been following AP for a bit now and get how it mostly works for "simpler" things like micro/blogging services like Mastodon/Pleroma, but am really curious how Lemmy/Chapo fits into that (also, I'm dumb - so I have that working against me)
Excited to see where this goes.
I guess I've got two questions
is there any plan to keep contributing various fixes/improvements that the Chapo devs implemented to upstream Lemmy? Or you all just in wholesale fuck it mode? Even deprioritized, there's probably code they can use/learn from to help
what're the plans regarding federation? Does TS have libs for handling ActivityPub, or you all starting to work on your own?
I'll give some tldr answers here but if you check my comment history on this post theres more involved answers-
1 - Some of us personally have/still and will continue to contribute upstream. The amount of code we share probably isnt as much as it seems, upstream sometimes requests frequent changes to what we do so it's never been as simple as "pull request it" and we have several proposals on their github still that are in various progress states. Ideally the rewrite makes it easier for this to happen- it will be quicker to implement an idea in Typescript, vet it against a large lemmy instance (ours) and propose it upstream or rewrite it in Rust, than it would be to write it in rust "our way" then have to rewrite it again anyways.
2 - Federation is still a core goal. There are some TS libs but none we've carefully vetted. For the initial "v1" state we might end up working on our own because Lemmy's websockets kind of tightly tie into how they use apub and we already have to port the ws code there
Ok, rad. That's basically what I was hoping to read (and actually reading the original post on something bigger than my phone, I can see where my questions were basically answered).
This is really good to see and probably helps with the image of the community that you're not just cutting and running from upstream.
I'm really eager to see where this ends up. I've been following AP for a bit now and get how it mostly works for "simpler" things like micro/blogging services like Mastodon/Pleroma, but am really curious how Lemmy/Chapo fits into that (also, I'm dumb - so I have that working against me)