The new major version of Lemmy is now ready, and we need your help with testing. Most importantly it uses HTTP for API requests now, which is much more efficient than websocket. Additionally Two-factor-auth is supported. There are also countless other improvements and bug fixes.
You can register on any of the following servers to start testing, no approval required. You can post to your hearts content to find out if anything is broken. The test instances only federate with each other to avoid affecting production instances with spam.
If you encounter any bugs that aren't present in 0.17, open an issue and mention in the title that it happened with a release candicate version. Over the next days we will publish new RC versions to fix bugs that will invariably pop up.
Instance admins can try the new version by using Docker images dessalines/lemmy-ui:0.18.0-rc.2 and dessalines/lemmy:0.18.0-rc.1. Make sure that working backups are in place. For production instances its better to wait at least some days for the major issues to be fixed.
Peeps, I am seeing some really worrying trends on https://lemmy.fediverse.observer/list. Many instances are quickly filling up with thousands of spam accounts which will soon be unleashed on the threadiverse. While bots can bypass captchas, they at least limit the simplest scripts. We are going to face this really really soon https://lemmy.dbzer0.com/post/87753
Can we at least add support for disabling VPNs, or using some other captcha solution like recaptcha? IP rate limiting is useless with VPNs, and email verification is more trivially bypassed than the current captchas.
I like the ideas of good captchas or text applications to join. However, using one's IP kinda goes against the idea of privacy. I'd prefer if we find alternatives.
Small instance, open signups, rapidly growing users. On balance, given the issues others are having, it's probably bots creating the accounts.
On my instance if you looked in the database they all had gmail emails and all had the same pattern to the email. We were adding 20 users a day, then suddenly had 100 new accounts in an hour. There was a lot of talk from other instance admins seeing the same thing.
Can we please get the 10K char post limit raised to 50K or even 100K chars in v0.18? Many mods are desperate to get their wikis/guides ported from reddit and this has been a showstopping issue.
Congratulations on the improvements to the protocol and to you both sexy leftist pimps for keeping the FOSS philosophy alive.
On behalf of the Mujican community, I send you a fraternal hug and we reiterate that we are with you in whatever is needed, wherever the fediverse takes us.
A bit off topic, but can something be done about the power mods? I see a few users already forking every subreddit trying to ensure they remain a mod. No user can meaningfully manage 50-100+ communities.
Please consider capping the limit to 20 or less. First-mover advantage is huge, so starting up a community down the road to prevent this consolidation of privileges is likely out of the question.
I think you have the right problem with the wrong answer.
It'd be better if communities could subsume other, worse-moderated communities with the same name in some integrated/organic way.
I mean, I could run c/politics on some server, but if another 20 or 30 instances agree on c/politics that's the winner. If they agree on c/politics because it's the better one and cross-moderates in some way, more power to them.
Navigating to a different page scrolls all the way to the bottom of the page. I assume it’s part of some feature to remember the previous position (i.e., when navigating back), but I don’t think it should apply when using the pagination navigation. I’m on mobile.
I hope that in future versions you will be able to use lemmy without javascript, or at least will be able to read posts without it. I know that everyone uses js monstrosities nowadays, but this seems like a project born out of care and not out of need to ship product under a deadline.
I don't demand for people to drop everything and work on it, just hope that this is kept in mind in future.
frivolous critique, but using Star Trek series names for release candidate testing instances but not having “the next generation” seems like a missed opportunity.