Runs live, versioned Python application objects on one VM, with a suite of apps: projects, notes, tasks, files and more.

0 downloads

dbbasic-object-server/packages/app-feed/dbbasic-package.json
Download zip
Clone
Clone with git
git clone https://gitstable.com/git/askrobots/dbbasic-object-server.git
HTTPS
https://gitstable.com/git/askrobots/dbbasic-object-server.git
SSH
ssh://git@gitstable.com:2222/askrobots/dbbasic-object-server.git

Cloning needs no sign-in. Pushing over HTTPS asks for your username and an access token. SSH needs your key under SSH keys.

danq9 signup: the person chooses the password and name on the confirm page 83c7aa6 2 weeks, 5 days ago History
dbbasic-package.json · 2.2 KB · 35 lines
1{
2 "id": "app-feed",
3 "name": "Feed",
4 "version": "0.1.0",
5 "description": "64 - Feed: a personalized read over the follow graph. For a signed-in viewer, shows recent PUBLIC content authored by the accounts they follow, newest-first -- \"follows\" becomes a filter, not a dead boolean (plan/vocabulary/64-feed-spec.md). Owns no collection and no schema of its own: it is a pure permission-gated composition of two existing filtered reads (58), both riding the caller's own session through _internal_request -- `follows` (who does the viewer follow) and any collection that opts in via a `blocks.feed` schema key (app-articles' `articles` is the worked example, wired in this same slice; see its schema for the shape). No new access path is opened anywhere: every source read goes through the real /collections/{c}/records permission gate as the viewer's own identity, so a followed account's private rows can never enter the feed -- following only changes which already-PUBLIC rows get selected in (object_server.py's _handle_feed carries the full argument). Served at /feed by the single-segment site-object convention (/feed -> site_feed), same as site_dashboard (/dashboard) and site_activity (/activity) -- no site_routes record is seeded or required. The JSON composition itself lives at GET /api/feed (mirroring /api/activity's split between a bare page path and an /api/ data path, since both /feed page and /feed data can't share one literal route in this dispatch); the page here is presentation only, fetching that endpoint client-side with the visitor's own session. v1 is fan-out-on-read only, per the spec; the materialized `feed_items` collection and its fan-out HANDLES object are designed there but not built in this package.",
6 "compatibility": {
7 "dbbasic_object_server": ">=0.1.0"
8 },
9 "dependencies": [],
10 "objects": [
11 {
12 "id": "site_feed",
13 "path": "objects/site/feed.py"
14 }
15 ],
16 "schemas": [],
17 "permissions": [
18 {
19 "path": "permissions/rules.json"
20 }
21 ],
22 "seed": [],
23 "migrations": [],
24 "nav": [
25 {
26 "id": "feed",
27 "label": "Feed",
28 "path": "/feed",
29 "blurb": "Recent public posts from the accounts you follow",
30 "surface": "member",
31 "group": "Publishing",
32 "order": 220
33 }
34 ]
35}