It’s kind of a chicken and the egg problem though, that happens on any new place, so it’s tough to sell them on that unless they already like what’s being talked about. I think it’s probably better to stick to the fundamentals of the fediverse and what makes it better than a centralized platform. In this phase of Lemmy’s popularity we need people that stick around and build communities, and they can only really be enticed to do that based on the merits of the platform.

While I’m not particularly fond of using AI for any kind of truthful information, this post reeks of the classic “Quit having fun!” meme. Your value judgement of AI is no more valid than anyone elses, and honestly in my opinion, very misdirected and anger fueled.

It’s in everyone’s best interest for AI content to be honestly declared. You are almost certainly already consuming AI content from somewhere without knowing it because angry hate mobs have conditioned people to just lie and obfuscate their AI usage to avoid being the target of hate. And if not, you will eventually due to the power of the technology, as the entire creative industry is already silently integrating it, as everyone with an open mind knows, but the benefit of honesty towards closed minded angry people is none, and that situation is a shame.

Good AI usage is impossible to detect, and we should encourage honesty in regards to it.

Yeah and honestly, this is largely a reasonable standard for anyone running an email server. If you don’t have SPF, DKIM and DMARC, basically anyone can spoof your emails and you’d be none the wiser. It also makes spam much harder to send without well, sacrificing IP addresses to the many spam lists. I wouldn’t be surprised if some people setting up their own mail server were made aware of these things because of being blocked.

I am kind of afraid that if voting becomes more public than it already is, it will lead exactly to more of the kind of “zero-content downvote” accounts mentioned in the ticket. Because some people are just wildly irrational when it comes to touchy subjects, and aint nobody got time to spend an eternity with them dismantling their beliefs so they understand the nuance you see that they don’t (If they even let you). So it kind of incentivizes people to create an account like that to ensure a crazy person doesn’t latch on to the account you’re trying to have normal discussions with.

But I understand that they can technically already do this if they wanted to. So perhaps it will be fine as long as we fight against vote viewing being weaponized as a community.

First: They did actually end up removing this and making it configurable, check the bottom of the page. In a vacuum, the idea to stop cut-and-clear racists and trolls from using Lemmy is not something that’s too controversial. Sure, they are being hard asses about changing their mind and allowing instance owners to configure it themselves (and I’m glad they changed their mind). But there’s a big overlap between passionate and opinionated people, so they have to be at times to ensure a project doesn’t devolve into something they can’t put your passion into anymore.

Second: I mean… what do you expect? In the issue above they actively encourage people to make their own fork of Lemmy and run that if they don’t like something from the base version of Lemmy, so I kind of would assume they do as they preach. Instance owners also have the option to block communities without defederation. Lemmy.ml is basically their home instance. If anything this is a reason not to make an account on lemmy.ml, but as long as that doesn’t leak into the source code of Lemmy, who cares?

It’s because the current version has nothing wrong with it. If the Lemmy devs should choose to sabotage the Lemmy software, you’d be surprised how easily that happens when it pisses off all the instances and their owners. Instances will simply refuse to upgrade. And like most things, eventually some fork will win the race to become the dominant fork and the current Lemmy devs would be essentially disowned. Different forks also doesn’t necessarily mean API breaking changes, so different forks would have no issue communicating (at least for a while).