3 ms·
It also has a pretty fundamental design flaw: issue /PR comments belong to the server where the commenter is hosted, not to the repo. I’m sure they will find a
by jeremyjh 3mo ago
It also has a pretty fundamental design flaw: issue /PR comments belong to the server where the commenter is hosted, not to the repo. I’m sure they will find a workaround but finding that reduced confidence they actually understand the problem they are solving.
- nerdypepper 3mo agothis is changing very soon :) see knot2[0] for some initial experiments: https://tangled.org/oyster.cafe/knot2 https://tangled.org/oyster.cafe/knot2 > As time goes on we are re-assessing the idea of users owning what is "collaborative data" (issues, PRs, etc.) on their PDSes - soon may come the day that an issue also lives on the knot as a source of truth, with an accompanying pointer record on user PDS to attest that it's theirs
- icy 3mo agoWe’re solving for this very issue. Issues & pulls will belong to the repo, backed by a “COB” (collaborative object) system.