Roadmap 0.11, My objects: private library objects and family files (Track PO)

PO.1 Library: private objects that only their owner can see ("My objects")

  • Feature
  • Built · in the lab
  • BimCraft

Asked on Discord 2026-11-18: bring family (.rfa) libraries into BimCraft so they act like Library objects, private to their owner. Built: a third Library visibility, private (migration 155). A private object is an ordinary library item (versions, item.json, preview), so apps place, swap and update it like any item; only its owner and staff can see or fetch it. It is in no public list, count, search, feed or sitemap, is published at once (nobody else sees it, so nobody reviews it), announced to nobody, and cannot be forked by others. No license to choose and no right-to-share tick: nothing is shared. Service LibraryPrivate, API /api/v1/library/my-items (list, keep, new version, remove; nothing hard-deleted). Each kept object goes through the same converter as an uploaded item (format checks, our own preview drawing). Closed to everyone but staff and lab testers until .env LIBRARY_PRIVATE=1. Limits for now: 500 objects an account, 8 MB each, 300 saves an hour (first numbers, see PO.6). Tests: bin/test-library-private.php (41, rolled back): owner sees it; another account and a visitor get 404 for the item, its file and its preview; not in browse, counts, makers, sitemap, feed or notifications. bin/test-library.php still 355 of 355.

Add a comment

Community comments

No comments yet

Add detail as we go: how you would use it, files or steps that show the problem, what other programs do. The team reads every comment.

Sign in or create a free account to add a comment.