I pay for their product and its totally worth. It was $10 for the longest time and much like everything in the last few years has increased price to what it is actually worth. To be honest $20 a year is still stupid cheap and worth it to keep them developing the product. Bitwarden is also one of the few password managers that hasn’t had a user data breach.
Fair enough. The other thing is if people hate it and want it banned on an ethical perspective, what if the AI used was selfhosted and self trained on ethically obtained data? There is no way for the end user to tell.
You shouldn’t worry about all the what ifs, you deal with the now and adjust as things change. This is a lemmy community not a government law.
Oh man don’t look at some of my earlier repos while I was learning then.
We allow it on our large subreddits on reddit. What we do is use a bot to filter repos that are less than 3 months old.
People who vibe code slop just want to share their thing and then abandon it. A limit like that or even 6 months will kill majority of this sort of low effort crap. Most of these people just let Claude or whatever sign the repo as well, another easy way to catch slop.
Developers that develop and only use AI as a tool build great products still as they review all their code.
A blanket ban is just going to make people be more sneaky.
I’m a big fan, its just such a great open source tool and it comes with full BPMN2.0 support out of the box.
Correct, if we have something included in a contract we already have there is little reason for us to procure a FOSS tool and maintain a security understanding of said tool and maintain versions.
Organisation of 60K. Job is far too senior, lucrative and actually very enjoyable to consider moving over a puerile thing.
doxygen
There is zero chance for getting this approved to use in our Enterprise.
We have an existing tool that can do this without assessing another tool.
I say irrational because clearly there is a bias here and not an experience being referenced.
That’s completely irrational but you do you. Maintaining documentation is one of the best and safest uses for LLMs in coding - devs generally write bad documentation because they don’t want to do it.
I do run a local instance but what I do is then replicate certain repos out to Github and Codeberg. (The ones I like to keep public)
I also have lots of scripts I find handy but would never share. I just need a safe third party to host it.
Codeberg doesn’t allow you to use AI with your repos. Even if it is just writing your docs for you.
Radicle is decentralised though!
VSCode and Pycharm do it all for me. You can turn all that shit off.
I think I might move to VSCodium, hail libre!
Agree but their stance on LLM content is a big put off for me. I don’t share my scripts and things I write with AI but I like to keep them all together.
And it concerns me that Codeberg is the guiding hand for the forjejo project.
LazyLibrarian x2 instances, 1 for audiobooks and 1 for comics and ebooks. Nothing else needed, it uses Prowlarr to check all indexers.
I have a script that converts everything to epub, even epubs to ensure characters are utf8.
Because Codeberg is its own charity type thing they have a cohort of users that vote on decisions made and you cannot even see how they came to that decision because that area is restricted to them. Presumably they might not federate at all.
Yeah I stopped putting anything on codeberg and finished moving to sourcehut after they announced this. I’m stuck with Github due to work but policing whatever random repos I have and want source control is a bit of a dick move.
I have a local forjejo which replicates certain repos to Codeberg and others to Github. Now I have to adjust my integration.
I set up Backblaze for my Synology NAS’ and while I check to make sure it is working I’ve never had to touch it otherwise.
When nothing (no a/c, washer, work PCs off, etc) is running my house power draw is about 500-800w. So my battery keeps things going until the next day.
Edit: just checked and whole house is 350W this evening.