You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CODE_OF_CONDUCT.md
-6Lines changed: 0 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,6 @@ We are rats. We accept that.
16
16
-**Students and beginners**: Genuinely willing to learn and get hands dirty, not here to beg for ready-made answers
17
17
-**Anyone, any language, any region**: If you use this tool, you are part of the community
18
18
-**AI Agents**: Automation pipelines, Agent workflows, LLM-driven toolchains — as long as behaviour complies with this code, Issues and PRs from Agents are treated equally
19
-
20
19
We welcome Issues, PRs, discussions, rants — as long as you are serious, regardless of whether the author is human or Agent.
21
20
22
21
---
@@ -31,7 +30,6 @@ The following behaviours result in immediate Issue closure / PR rejection / acco
31
30
-**Resource predators**: Stable income, corporate budget, yet competing with marginal developers for free resources and community attention
32
31
-**Harassment**: Personal attacks, discrimination, stalking, harassing maintainers or other contributors
33
32
-**Hustle-culture pushers**: Glorify overwork, promote 996, or use this tool to exploit other developers
34
-
35
33
---
36
34
37
35
## Contributor Obligations
@@ -42,14 +40,12 @@ If you submit an Issue (human or Agent):
42
40
- State your OS, Node.js version, and tool version
43
41
- Agent submissions must include trigger context (call chain, input params, error stack)
44
42
- Do not rush maintainers — they are humans, not customer support
45
-
46
43
If you submit a PR (human or Agent):
47
44
48
45
- Open an Issue first to discuss, avoid wasted effort
Copy file name to clipboardExpand all lines: README.md
+16-23Lines changed: 16 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,6 @@ So as a rat, I eat whatever I can reach: maggots in the sewer, leftovers in the
10
10
- Does not expect any platform to grant an "official all-in-one solution"
11
11
- Does not rely on privileged interfaces of any single IDE / CLI
12
12
- Treats every readable config, prompt, and memory file as "edible matter" to be carried, dismantled, and recombined
13
-
14
13
In this ecosystem, giants monopolise the resources, and developers are thrown into the corner like rats.
15
14
`memory-sync` accepts this cruel reality, does not fantasise about fairness, and focuses on one thing only: **to chew up every fragment of resource you already have, and convert it into portable "memory" that can flow between any AI tool.**
16
15
@@ -27,7 +26,6 @@ What can it help you do?
27
26
-**Read-only source files**: never modifies your original repository directly, only reads and transforms, then materialises the result on the target tool side.
28
27
-**Full wipe**: on sync, erases all stale prompt traces in target tools—prompts are fully computable and auditable, leaving no residue for bad actors.
29
28
-**Prompts grow with you only**: memory follows you as a person, not the project. Someone else takes over the project—they cannot take your context. You move to a new project—your accumulated knowledge moves with you intact.
@@ -49,7 +47,6 @@ More platforms being added continuously.
49
47
-**Core** (Rust): file I/O, directory traversal, format conversion.
50
48
-**Config DSL** (YAML / JSON): place a config file at the project root to describe sync rules and target tools.
51
49
-**GUI** (Tauri): desktop app that calls the CLI as its backend, providing a visual interface.
52
-
53
50
## FAQ
54
51
55
52
**When AI tools finally have a unified standard, what use will this project be?**
@@ -73,48 +70,44 @@ To use `memory-sync` you need:
73
70
- Solid development experience, years of working with various dev tools
74
71
- Proficiency with version control (Git)
75
72
- Proficiency with the terminal
76
-
77
73
---
78
74
79
75
- You are writing code in a forgotten sewer.
80
-
No one will proactively feed you, not even a tiny free quota, not even a half-decent document.
76
+
No one will proactively feed you, not even a tiny free quota, not even a half-decent document.
81
77
- As a rat, you can barely get your hands on anything good:
82
-
scurrying between free tiers, trial credits, education discounts, and random third-party scripts.
78
+
scurrying between free tiers, trial credits, education discounts, and random third-party scripts.
83
79
- What can you do?
84
-
Keep darting between IDEs, CLIs, browser extensions, and cloud Agents, copying and pasting the same memory a hundred times.
80
+
Keep darting between IDEs, CLIs, browser extensions, and cloud Agents, copying and pasting the same memory a hundred times.
85
81
- You leech API offers from vendors day after day:
86
-
today one platform runs a discount so you top up a little; tomorrow another launches a promo so you rush to scrape it.
82
+
today one platform runs a discount so you top up a little; tomorrow another launches a promo so you rush to scrape it.
87
83
- Once they have harvested the telemetry, user profiles, and usage patterns they want,
88
-
they can kick you—this stinking rat—away at any moment: price hikes, rate limits, account bans, and you have no channel to complain.
89
-
84
+
they can kick you—this stinking rat—away at any moment: price hikes, rate limits, account bans, and you have no channel to complain.
90
85
If you are barely surviving in this environment, `memory-sync` is built for you:
91
86
carry fewer bricks, copy prompts fewer times—at least on the "memory" front, you are no longer completely on the passive receiving end.
92
87
93
88
## Who is NOT welcome
94
89
95
90
- Your income is already fucking high.
96
-
Stable salary, project revenue share, budget to sign official APIs yearly.
91
+
Stable salary, project revenue share, budget to sign official APIs yearly.
97
92
- And yet you still come down here,
98
-
competing with us filthy sewer rats for the scraps in the slop bucket.
93
+
competing with us filthy sewer rats for the scraps in the slop bucket.
99
94
- If you can afford APIs and enterprise plans, go pay for them.
100
-
Do things that actually create value—pay properly, give proper feedback, nudge the ecosystem slightly in the right direction.
95
+
Do things that actually create value—pay properly, give proper feedback, nudge the ecosystem slightly in the right direction.
101
96
- Instead of coming back down
102
-
to strip away the tiny gap left for marginalised developers, squeezing out the last crumbs with us rats.
97
+
to strip away the tiny gap left for marginalised developers, squeezing out the last crumbs with us rats.
103
98
- You are a freeloader.
104
-
Everything must be pre-chewed and spoon-fed; you won't even touch a terminal.
99
+
Everything must be pre-chewed and spoon-fed; you won't even touch a terminal.
105
100
- You love the grind culture.
106
-
Treating "hustle" as virtue, "996" as glory, stepping on peers as a promotion strategy.
101
+
Treating "hustle" as virtue, "996" as glory, stepping on peers as a promotion strategy.
107
102
- You leave no room for others.
108
-
Not about whether you share—it's about actively stomping on people, competing maliciously, sustaining your position by suppressing peers, using others' survival space as your stepping stone.
109
-
103
+
Not about whether you share—it's about actively stomping on people, competing maliciously, sustaining your position by suppressing peers, using others' survival space as your stepping stone.
110
104
In other words:
111
105
**this is not a tool for optimising capital costs, but a small counterattack prepared for the "rats with no choice" in a world of extreme resource inequality.**
0 commit comments