- name Settled on Mangaloid as project name. Commercial name will be decided upon when the time comes.
- domain Same as above.
- logo /a/ mascot
- licence MIT
- git repo access Core Dev team: compscifag, cynic, Usag, zhetic
- dev teams/areas of responsibility? compscifag, mojo: Instance software, zhetic, Usag: Front-end, qeeble: Testing, cynic: Content
- financing There will be financing
- content policy
- minimum resolution readable
- multiple scanlations Up to instance
- official translations Probably no
- file naming scheme cid/{int, 2 leading zeros}.{ext}
- smut/hentai Up to instance
- space efficient image format Needs more research
- vol covers Space-efficient thumbnails served by instances
- MTLs Up to instance
- pixiv/twitter shorts: Up to instance
- DMCA fingers crossed
- final decision on ipfs We will keep working with it for now
- own forked implementation? No
- who is a node? users with js-ipfs in the browser/instances/others Only instances until we evaluate JS-IPFS
- compensation? Not important
- webtorrent? Dismissed, in favor of IPFS
- need to start collecting and uploading content as soon as possible cynic's area
- record of who is hosting nodes Yes, will be managed by the mangaloid project
- master server? No
- approve db layout Approved
- REST api spec Speced
- submission system? token-based auth, zipped or independent files
- record of who is hosting instances yes
- hosting yes (github pages?)
- authentication and admin access localhost only, until we expand spec to user accounts and perms
- REST api spec Coming soon
- site design guidelines Go crazy