This thread is for @"RX14" and myself to release regular (hopefully) updates about where we're at with 2lewd.
Feel free to discuss updates posted in this thread here.
Also, we have a discord channel named #changelog, you can occasionally see us push code changes and see what's going on in that regard. Although at the moment we're mostly planning things, so the channel is eerily quiet. But will pick up shortly.
Updates so far.
10 Jan 2017 - Oppai & Ketsu
Oppai & Ketsu
10 January 2017
We've decided to shelve progress on our first version of 2lewd; we were running into some pitfalls and have come up with a better way of going about things.
2lewd is now split into two components:
Oppai
Oppai will be 2lewd's glorious frontend. Powered by Node.js and Vue.js, it'll be pulling content from Ketsu and rendering it in the browser.
Ketsu
Ketsu will be 2lewd's well rounded backend. Using Crystal and PostgreSQL, Ketsu will provide a public RESTful API for 2lewd; giving Oppai (and any other third party) endpoints to retreive data from.
It's a fairly different direction to what we were playing with before, but in our opinion, it's definitely a better direction.
There are advantages and disadvantages to doing it this way, here are a few of them.
Advantages
Should be insanely fast
Will be easier to provide realtime updates to threads, alerts, and other data
Will be slick af to use
It'll be a hell of a lot easier to develop in the long run
Third party tools could be easily developed; looking at you Equinox, with your CLI Lewd.
RX and I can work on Oppai & Ketsu independently, meaning more gets done, quicker. Any lewd fanfics about this will result in a ban.
Disadvantages
non-JS users may be limited to a read only version of the site.
will basically be saying "fuck you" to anyone that uses an IE version older than IE 9. (Arguably a good thing)
Overall, we're pretty happy with the direction we're heading in, and hope to have this done eventually. We're sorry that this has taken so long, but it's fairly difficult to find time to work on developing when RX studies and I work full time.
API Planning
31 January 2017
We've started planning out the structure of 2lewd's API (ketsu). So far we've written up most of the routes that we'll be implementing and have started to document them.
Image no longer available
You can read the documentation (so far) here, or even help contribute to the documentation here.
rx making progress Image no longer available
Image no longer available
Progress
1 May 2017
We have some sexy screenshots to show you!
These screenshots are rendered using data from the backend API, that is not just a HTML mockup.
I've been working pretty consistently on 2lewd now, fitting in bits when I have the time. Progress is now steady, instead of happening in bursts. You can follow progress in the #changelog channel in discord. This has the advantage of me being able to keep my "flow" and ideas of what needs to be done next, keeping me motivated. We hope to have an initial alpha playground up in the next few months, this will be populated with data imported from lewd.sx (to allow testing the importer), but wiped and re-imported every midnight so as to make sure any "real" activity stays off the alpha.
Discussion thread: https://lewd.sx/t/2lewd-discussion-thread
