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
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
based on @boreq comment here %ALlo/17yDR1G2NwuXQ/XCnjjmq6fNpFBb4Ir5p9yr+k=.sha256
here is a sketch of scuttle-golgi as imagine it:
then:
notes:
this is written here more as notes to discuss on a call, than as a proposal for feedback
I think you can track progress for integrating
scuttle-gointo Planetary via https://github.com/planetary-social/scuttlego/milestone/1 which should signal it is maturing / getting more reliable / stable etc.Also some notes from my call with boreq:
https://hackmd.io/@Ip262E0TThagICNLwYhMfQ/rkgt7SbXj