Drops: backups, forks, stars, comments, embedding issue #280 closed: completed andymccall opened this 15 days ago · 0 comments

Follow-up to issue #279 (Drops, first version). Backups first: backups list repositories through db::repos::list, which leaves drops out, so drops are not backed up today; and a restore would need to keep repositories.kind and title. Then: fork a drop (into your own drops), star, comments, embedding a drop in another page, rate limits beyond the per-change size limits.