Time for our third, albeit slightly belated, community update!
In October, we...
As of 10th November, Waterfall has 26,832 users, 45,732 blogs, and 246,403 posts.
Things have slowed down on the new user front - that's to be expected, given we've not done any extra marketing lately and we've been slower with updates. We'll be remedying that soon!
Coming in the next week or so, depending on testing results, will be the tagging and queue overhauls. Ideally these'd be launched seperately, but practically, because the queue overhaul plays off the new tagging system and the tagging system would need to update posts already in the queue, they'll be released together instead.
Queues pose an interesting challenge, since the way they're stored is being changed entirely to how it really should have been in the first place if I didn't decide to implement the system in two hours at 3am. The three options are to delete everything in the queue, forcibly post everything that's in the queue, or move everything into the new system but set every blog's queue frequency to 0. We ended up picking the latter since no content is lost that way, and - as a sign that we need better documentation - a third of all posts in the queue are on blogs that have a queue frequency set to 0 anyway.
Setting every blog's queue frequency to 0 is likely to be the best option based on that, and then everyone can re-adjust their settings based on the new features.
We're not entirely sure if any other new features will make it into the next update, but we're hoping to get it out in the next few days. After that, there'll be a few QoL patches - options for disabling anon asks and allowing logged out users to send messages are one - before we add the next big feature, which will likely be the CM, at long last.
For the site's UI, we're still drafting the revised version and our designer is on vacation right now, so stay tuned for that!
We're also playing with some algorithms to improve blog recommendations. We're not sure which one we'll pick yet, but we've narrowed it down to four.
Oh right heads up: Next patch will start collecting your timezone at login/when you set your queue posting parameters to make sure the "post between x and y o'clock" stuff works properly
You'll also be able to manually set it, but just a heads up that it's a little more data we'll need to start storing on you
my entire fucking face when I find out i-am-a-fish has a patreon and people are actually giving them a hundred fucking dollars for running that blog
my entire fucking inferiority complex when we never even broke 20 bucks a month on patreon for running the entirety of waterfall
Might have to roll the queue overhaul out at the same time as the tag overhaul becaause actually it turns out it'd be harder than it's worth to seperate them
I also want to keep up the illusion that this shit takes ages to do instead of me twatting about for 20 minutes and it being finished like Pillowfort and Tumblr do to justify their entry fee and ineptitude respectively
have y'all seen that post on tumblr about zillenial culture? well something else that some people have mentioned is the switch that everyone did from regular box tvs to flat screen tvs, but if you were poor like i was you saw everyone else slowly buy flat screen tvs first and then eventually your fam was able to afford one
this except mine never got a new tv and just watches netflix on a big pc screen instead
Next two overhauls will be Queue and tags
Tags is half written from the rewrite thankfully, we just gotta slide it in and do a conversion on what we already have. Queues shouldn't be too difficult to do either. The real question is, will I remember to do one of them when I wake up?
Queues and tags will probably come at the same time because HHHHHHHHHHHHHHHHHHHHHHH
I also need to figure out how to get stuff currently in the queue over to the new system...
About 1/3 of posts currently in the queue are on blogs with a queue frequency set to 0
Considering changing tack on development and going back to incremental updates. Probably easier and better to do than one giant rewrite, as well as having less downtime...
You COULD argue that this means I've written wasted code, but I'd disagree on that - it was at least a good learning experience, and most of what's written will be useful for the API as well, since that more or less requires the kind of code written there. Plus it'll eventually be on the main site anyway, it's just a bit much to do a full rewrite while I'm still the only staff member who can put more than half hour a day into the site.