sr229
commented
4 years ago The primary aim of Project Aya is to evaluate technologies that were mostly overlooked by boorus. Boorus are mostly done with no future-proofing in mind (ie, they're mostly monolithic in nature, relies on vendor-specific storage (S3 for example) ) and is more costly to deploy in a sense you actually need to set up the way it was meant to be set up.
Project Aya focuses more on these basic paradigms when I first conceptualized it:
- a booru should be simple to manage, contribute data to, and deploy. We shouldn't need complex system administration knowledge to run one (apart from needing database admin knowledge). The idea is you can run a image board by just having your own logo and running some simple set up steps.
- a booru should be modern - I believe that the reason that a large percentage of the web is still legacy is because we keep coding legacy to keep in touch with computers from 2005 or so. We're in 2020, we shouldn't bother with legacy from 2001. That's why we're working on using standards like WebP and Serverless to make Aya what it is today. We already have a handful of sites using more modern solutions like JAMStack. Aya is no different in pursuing a modernized web.
The project is more than a gimmick, its more of a love letter that image boards like philomena we're not modern enough.
If you want to contribute closely to us and know more about the project, our Discord will be open very soon once Aya launches. For now, we're still in early stages but we do encourage contributions, we already have UI design for it (It took me some months to finalize its look), but if you can't wait for the launch and would like to have a open line of communication with us, let me know over at my email which is linked on my GitHub profile.
Thanks!
There are other booru engines that are on Github
Is it possible to poke through the code to identify other features?