graphprotocol / graphprotocol/hypergraph

Roadmap

Open
#331 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
22
Forks
12
PR merge metrics
No merged PRs in 30d

Description

Hypergraph Framework

Geo Apps Integration

High level roadmap third party integration Roadmap

  • Figure out App registry
  • Rework Invitations with all our lessons learned
  • Fix all open issues in Schema handling
  • Restructure CRDT syncing using Keyhive with 1 CRDT doc per entity instead of 1 per space
  • Settle on sync server architecture (federation?)
  • Add permission functionality to Connect app
  • Re-evaluate group key management (XMPT vs Beekem vs Lockboxes) based on all the lessones/requirement learned
  • Typesync improvements
  • Re-evaluate security ideally even a Security audit?
  • File handling (maybe post 1.0?)
  • Real-time awareness features (maybe post 1.0?)

Prioritised Issues

Non-breaking
Breaking Changes

Typesync

create-hypergraph

Connect

  • Implement loading indicators while the signing processes @benface
  • Implement new design @benface
  • Selection of spaces (public) @nikgraf (in the sync server we need store the info which app has access to which space)
  • Delegation of space creation (private)
  • Delegation of space creation (public)
  • Remove an app from a space
  • Verify app + domain -> public knowledge graph?

Sync Server

Schema Browser future? https://schema-browser.vercel.app/

  • regenerate schema

Overall Specification

Docs

Repository Infrastructure

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the roadmap sections and the linked issues and pull request, especially the Geo Apps Integration, Typesync, Connect, Sync Server, Docs, and Repository Infrastructure entries. This issue is complete only when the roadmap's priorities and status are made specific and actionable, but no file, test, or single change is identified here.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.