d@nny mc² @hipsterelectron@circumstances.run
Quiet public

i especially think "git forge over git itself" is a hard problem bc git forges are email and git is git circumstances.run/@hipsterelec

d@nny disc@ mc² (@hipsterelectron@circumstances.run)

@lynn@a.bloodyno.se @boo_@im-in.space i think making forge UX go through a web browser is a way to avoid solving the problem but doing forges through the version control layer is a complex UI and backend problem so nobody's done it yet. but it would help to address the issue that people are involving a web frontend to perform actions that could be done via API so the web frontend can't easily be separated from the backend and LLM scraping then affects availability

circumstances.run · GSV Sleeper Service

d@nny mc² @hipsterelectron@circumstances.run
Quiet public

i previously attempted to do this circumstances.run/@hipsterelec but have since realized long after the fact that doing it through git was a massive constraint and have now tentatively split up the problem into three separate components of:

(1) represent forge operations as messages distinct from any forge frontend or backend, so they can be generated by any forge and consumed by any frontend (e.g. text editor/IDE as well as browser)

(2) design a set of forge operations to represent the full breadth of how users wish to communicate around code (different projects use forges differently—how can the protocol address all the types of review styles? can/should the protocol encourage certain review flows instead of leaving user behavior to the frontend?)

(3) design a representation of identity and interaction content which can be federated across servers like fedi, so i can interact with a forge (e.g. make a PR that a project can easily consume) without making an account on the project's forge server

d@nny disc@ mc² (@hipsterelectron@circumstances.run)

@lynn@a.bloodyno.se @boo_@im-in.space i have a project which did this https://github.com/cosmicexplorer/ping-pong along with way too many other things. there are emacs interfaces for individual forges but no work towards a standardized protocol afaict. i'm stealing the idea of stuffing it in git-notes from google's git-appraise—git notes is fine as a backend but it completely fails to solve the actual problem of what info you send to federate a forge. it also imposes some constraints from the use of git notes which are sometimes appropriate but may not be the right way to handle forge interactions (both as a logical model and as a method of communicating updates)

circumstances.run · GSV Sleeper Service

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://circumstances.run/users/hipsterelectron/statuses/114439185067283998 on your instance and quote it. (Note that quoting is not supported in Mastodon.)