Only reason why launch was delayed last time was textageddon! Assuming there isnt a comparably severe bug lurking somewhere, I'll update the readme/about page, and post to several places including hn/reddit/etc at 09:00 EST.
Only thing that is left is user blocking, and permanent post hiding (and maybe post/comment saving), and most of this functionality already exists on backend.
One feature I'd really like added would have been diminishing returns on /i/all posts: If a sub already has a post that's on the /i/all, subsequent posts from that sub will have added "weights" on the amount of upvotes needed to reach /i/all again until a certain amount of time has passed.
This prevents one sub from "dominating" the site and allows more variety. I understand that we might have to come up with an algorithm, but hopefully you'll keep this in mind when ieddit launches.
I think it's an issue caused by 7s and 1s. They really do look 100% identical sometimes.
I'll consider switching to a different captcha library, which certainly won't be recaptcha due to how tor/vpn users are discriminated against (and the data it collects...).
It's because this youtube URL is using a format my parser doesn't know how to handle, it'll be a quick fix.
The thumbnail thing is strange.
Thumbnails won't show up for a bit after creating a new post, because the server has to send a request, and process it, separately. If I forced the server to wait on the request to finish, load times could be several seconds long, or more, because I cannot control how requests are handled on the other end.
If it STILL doesn't display for a few seconds, odds are it couldn
Only thing that is left is user blocking, and permanent post hiding (and maybe post/comment saving), and most of this functionality already exists on backend.
See ya then