Of course.

Moderators can ban people for whatever reason they like, there isn’t really a way to prevent that. An instance owner could make a rule against it, but you couldn’t enforce it on other instances of course. The remedy to bad moderation is to make a different community.

The FuckAI thing does kinda make sense, though. If I wanted to make a community that focused on [thing], I would not really want input from people who avidly post on the Fuck[thing] community. That lacks precision of course, so I’d be open to appeals from people who posted in Fuck[thing] but don’t actually hate [thing].

Accidental downvoting (esp on mobile) is pretty easy

Isn’t it? It’s not so uncommon for me to see a post that I had evidently downvoted without noticing.

Haha, this thread has turned into an excuse to share ones hobbies and interests eh? I won’t be tempted!

Are you drunk?

I kinda miss living in St Louis

Wow, that’s a lot of upvotes

Same here! I started with Lycoris back in 2003, I’m very experienced with many different distros. The universal blue distros (Aurora, Bazzite) are my preference these days. You get the benefits of the atomic host and they aren’t actually restrictive at all once you get comfortable using containers for software that you can’t easily install with flatpak or brew.

It’s a good question, and it has a definitive answer: Distrobox.

https://docs.bazzite.gg/Installing_and_Managing_Software/Distrobox/

You can also run applications from within the container. I have a Debian based container (but you can use whatever you prefer, I just happened to find a guide for getting jetbrains IDEs working well with a Debian one) with the Jetbrains suite installed and all of the development tools I need.

Since getting comfortable using distrobox, I prefer to use it for dev environments even when I’m not using an atomic distro. It doesn’t add any additional friction.

I just suggest that people join .world (unless I know the person I’m talking to will best fit a different instance) and not worry about it. Once they understand how it works, they can make an account on a different instance if they want. There’s no need to overthink it.

I love everyone!

It looks fine on this instance. Maybe it’s a .world media storage thing going on.

I don’t begrudge Cosmic or anything, it’s just not what I want. I’m glad it exists.

KDE 4 was the TRULY bad release, if I recall correctly. It was a massive change from 3 and reduction in features and stability. I actually noped back over to Windows for a while as a result. I remember 5 being a welcome return to form comparatively.

EDIT: From the wikipedia Article on KDE4, oof:

KDE 4.0 was released in January 2008. Linux.com described the reaction from users as a “revolt”, writing that the backlash KDE 4.0 received was on a scale that was unprecedented for a FOSS project. Although it was a developer’s release, several distributions made the KDE 4.0 desktop environment available to their users without specifying that it was an experimental option. openSUSE released a more polished KDE 4 option while other distributions “released packages that simply [didn’t] work,” according to project leader Aaron Seigo. As a result, many users complained about the loss of features and stability. A number of KDE developers, including project leader Aaron Seigo, were targeted for abuse by outlets like Linux Hater’s Blog. Several KDE developers stepped back from the public scrutiny.[36]

A script that shows a modal box or whatever when something fails to load as expected need not spy on you to function, but maybe I’m reading into a funny post more than I should be.

As far as code quality and reliability goes for mature projects like KDE and Linux, I trust the maintainers to know what they are doing. I have no place second-guessing them. If they think LLM usage disclosures are useful I believe them, if they feel otherwise I accept that as well. To me as an end user, it makes no difference. I’m not going to stop using Linux or KDE over LLM-assisted code contributions either way.

As far as copyright-ability, I could be convinced here. I’m not a legal expert at all, but it seems pretty speculative. I did read your first link, which is interesting. The legal risks as I understand them are:

A judge somewhere might say “This long-lived project has recently merged some patches which, to some unspecified and unknowable degree, involved LLM usage and therefore the GPL license indicated for this project is no longer valid. Therefore, the project is now Public Domain and it may be used and modified without releasing the changes.” Seems unlikely to me, but who really knows?

and probably much more likely:

A patch is accepted that replicates copyrighted code exactly, putting an unwitting maintainer in jeopardy. I looked around for examples of open source project maintainers being sued for this sort of infringement out of curiosity, but I really couldn’t find any. If this happens, I bet it’s typically handled outside of court with a C&D type situation.

Are there other legal risks I’m missing? I think it’s only a matter of time before some type of consensus for what the implications of the copyright questions are for FLOSS software.

No! Please, reconsider!

Lemmy/Piefed/Etc has a killer feature (or maybe characteristic), but one that only a fraction of users find appealing. Being decentralized makes the network more resistant to many of the problems we see on Reddit and other networks, or at least, reduces their impact.

It’s probably less clear than it should be, but the second sentence in that comment is not really my point of view. I’ll edit it to make that more obvious.

Yeah, same.

As long as general purpose computer devices are widely available, I think you’re right. Which, of course, will mean that “general purpose computers are not fit for for the broad public and should be restricted to a privileged licensed few for your own good.” This possibility is something I worry about.