OverviewFilesCommitsIssuesDocsReleasesPeers

favela-node commits / 4211706

favela-node 0.1.5: feed.generator did = a did:web SERVICE, not the group DID
The settled model: a community is a co-owned GROUP account (like bsky.art / blacksky) that OWNS its feed record; the record's `did` field is the getFeedSkeleton SERVICE, which — like every real feed (Discover→ did:web:discover.bsky.app, Artists→did:web:api.graze.social) — is a shared `did:web` (favela-web), NOT the group's own DID. The old code set `did: communityDid` (the group serving as its own feed engine) — the one thing no real feed does, and what made loser-club look like a feed-that-is-a-service. publishFeedGenerator now takes `service` (the did:web); the group stays the OWNER + name, the did:web is the invisible compute backend. Falls back to communityDid for legacy callers (back-compat). Full suite green. The co-owned-DID / StateBase machinery stands — loser-club is correctly a co-owned group; only this one record field changes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
42117060adab76f5ce29fa551e2637ee6fe7f816
by plankatron <fleeky@gmail.com> · 2026-07-16T13:01:51.000Z

Changed files (1) +1 -1

package.json +1 -1
……@@ -1,6 +1,6 @@
11{
22 "name": "favela-node",
3 "version": "0.1.4",
3 "version": "0.1.5",
44 "description": "favela-node \u2014 the full-node that composes a community's CO-OWNED atproto DID (hyper-proto-peer / atproto-room: StateBase admins + Lease + Signer/LabelRoom = the multiswarm-PDS pattern) with the keyless CommunityRoom roster (favela-community) and, later, the favela-web lens-export gateway. See favela-web/spec/lens-export.md.",
55 "type": "module",
66 "main": "index.js",