Scuttle Golgi #54

Open
opened 2022-08-08 07:37:12 +00:00 by notplants · 2 comments
Owner

based on @boreq comment here %ALlo/17yDR1G2NwuXQ/XCnjjmq6fNpFBb4Ir5p9yr+k=.sha256

here is a sketch of scuttle-golgi as imagine it:

  • sqlite database
  • use diesel ORM to create rust models for the different objects we work with (User, Message, AboutMessage, Relationship etc.)
  • poll/sync method which streams from scuttle-go and populates the scuttle-golgi database as new messages come in

then:

  • we can implement a library of functions in rust on top of this, which query diesel. if we wanted to, this library could even mirror the golgi functions we have already implemented, such that lykin, hermes, peachcloud and the documentation glyph has already made, could be adapted to use scuttle-golgi with minimal adaptation. or we could make entirely new apis if we chose to

notes:

  • I would still wait until scuttle-go is used by planetary before starting this (since it sounds like the apis may still change some until then based on boreq's comment)
  • if we did go this direction, I would consider to at some point rename scuttle-golgi to golgi2 or just golgi, to avoid having multiple libraries that need to be maintained or excessively confusing new developers. on a related note, also wondering how much of the previous roadmap we would still want to invest time into if we chose to go this route

this is written here more as notes to discuss on a call, than as a proposal for feedback

based on @boreq comment here %ALlo/17yDR1G2NwuXQ/XCnjjmq6fNpFBb4Ir5p9yr+k=.sha256 here is a sketch of scuttle-golgi as imagine it: - sqlite database - use diesel ORM to create rust models for the different objects we work with (User, Message, AboutMessage, Relationship etc.) - poll/sync method which streams from scuttle-go and populates the scuttle-golgi database as new messages come in then: - we can implement a library of functions in rust on top of this, which query diesel. if we wanted to, this library could even mirror the golgi functions we have already implemented, such that lykin, hermes, peachcloud and the documentation glyph has already made, could be adapted to use scuttle-golgi with minimal adaptation. or we could make entirely new apis if we chose to notes: - I would still wait until scuttle-go is used by planetary before starting this (since it sounds like the apis may still change some until then based on boreq's comment) - if we did go this direction, I would consider to at some point rename scuttle-golgi to golgi2 or just golgi, to avoid having multiple libraries that need to be maintained or excessively confusing new developers. on a related note, also wondering how much of the [previous roadmap](https://git.coopcloud.tech/golgi-ssb/golgi/issues/37) we would still want to invest time into if we chose to go this route this is written here more as notes to discuss on a call, than as a proposal for feedback
Contributor

I think you can track progress for integrating scuttle-go into Planetary via https://github.com/planetary-social/scuttlego/milestone/1 which should signal it is maturing / getting more reliable / stable etc.

I think you can track progress for integrating `scuttle-go` into Planetary via https://github.com/planetary-social/scuttlego/milestone/1 which should signal it is maturing / getting more reliable / stable etc.
Owner

Also some notes from my call with boreq:

https://hackmd.io/@Ip262E0TThagICNLwYhMfQ/rkgt7SbXj

Also some notes from my call with boreq: https://hackmd.io/@Ip262E0TThagICNLwYhMfQ/rkgt7SbXj
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: golgi-ssb/golgi#54
No description provided.