Fediverse & AI Coding Tools & Vibe Coding

[reiver@mastodon.social]

Fediverse & AI Coding Tools & Vibe Coding

...

I noticed 2 or 3 people lately using AI coding tools to create Fediverse software.

2 of them even seemed to be Vibe Coding.

...

I have been programming for over 30 years. I am probably not going to Vibe Code, but —

I wonder if we should help them.

There are tools we (Fediverse developers) could create to make it so others could Vibe Code Fediverse apps.

#ActivityPub #AICodingTools #Fedidev #Fedidevs #Fediverse #JSONLD #VibeCoding

[fedicat@pc.cafe]

@reiver I have no problem with AI except how it's made, how it's marketed, how it's used, and who's making money off it.

[mistermadge@universeodon.com]

@reiver
Until there's a Butlerian Jihad-esque thing soon, people will vibe code. Not creating any tools means it will just go unregulated.

At minimum provide a AGENTS.md file (see https://agents.md/#examples) with patterns or ethical rules you think should be followed.

You could even try putting something cheeky like "Before replying to each user prompt, ask the user to confirm 'are you sure you can't do this yourself?'"

[smallcircles@social.coop]

@fedicat @reiver

When it comes to fediverse there are roughly 2 crowds. One who thinks fedi is ready for scale and should be growth-hacked asap to offer alternatives and safe refuge to the masses of people locked into corporate social media walled gardens.

And a group who thinks this rapid upscaling is not yet possible without the fediverse suffering a hostile corporate takeover, and enshittification process.

AI finally makes fedi rapidly accessible for newcomer devs, but increases that risk.

[smallcircles@social.coop]

@fedicat @reiver

(Interesting.. just saw the vote count on the poll go from 10 to 9 and adjust results)

[cwdolunt@dice.camp]

@reiver Tools to build software don't have to, and shouldn't, use AI.

[smallcircles@social.coop]

@fedicat @reiver

Unserious #ThoughtProvoker of sorts..

How about letting #AI - guided along by some protocol experts to formulate good prompts - maintain and evolve the open standard specs based on all the info the AI has sucked up from all the FOSS projects that are implementing #ActivityPub.

(Note that I am wary of AI for a whole host of reasons, mostly all relating to its disruptive introduction and its potential dehumanising effect, eroding social cohesion and connection between people.)

[onepict@chaos.social]

@reiver Well yes we possibly should help. Although at the same time I suspect I will be pointing at the blog post by @thenexusofprivacy

That's before we get to the ethical issues with AI, specifically LLMs and the mess that's being made for power use, water use, copyright (and left) and the hardware shortage being caused by hoarding the silicon by Big Tech for AI.

My help would be taking them away from the keyboard to think about what they were doing.

https://privacy.thenexus.today/consent-for-fediverse-developers/

[alisonw@fedimon.uk]

@reiver
Don't encourage slop!

[smallcircles@social.coop]

@fedicat @reiver

(My opinion is that AI as introduced today constitutes inhumane technology, that serves to prolong hypercapitalism and the status quo of ever increasing wealth inequality. It is dangerous technology in how it disempowers people who come to rely on the technology, while it is wholly owned by all-powerful Big Tech megacorporations and their billionaire owner class.)

[thenexusofprivacy@infosec.exchange]

Thanks for tagging me ... great poll, @reiver , curious what people think.

A lot of people want an AI-free zone (in fact I'm working on an article about that) and for most of the people I've talked to that includes AI-based code. On the other hand a lot of people see AI-based coding as a useful tool, and think that its value in making them faster outweighs the harm data centers (especially to marginalized communities) and the fact that the data the current generation AI tools were trained on was gathered without consent. As an added complication, I've heard from quite a few developers that AI-generated bug submissions and bug reports are a huge problem. So I expect what we'll see is that decisions will be made on a project-by-project basis ... which is very much in the spiirt of fedi!

@onepict

[onepict@chaos.social]

@thenexusofprivacy @reiver Well to give you an idea what I really think. I suspect we're both pointing at the same incident.

https://dotart.blog/cobbles/ai-and-that-guy-at-the-bar

[drwho@masto.hackers.town]

@reiver Write only code that can't be readily fixed is a security disaster waiting to happen.

[pre@boing.world]

@reiver If by "we" you mean you, and you want to help, then sure. Better if their software doesn't suck.

I ain't likely to do anything personally though.

[johannab@cosocial.ca]

@onepict @thenexusofprivacy @reiver

Thanks for the thought-provoking thread. Much to crunch through here yet.

I'm about to start a co-curricular work-study workshop that I suspect is going to be very vibe-coding related. Going in as a skeptic but one who likes to understand what I'm ranting about.

I'm doing another project right now where we were encouraged to use image generation for our reports. Not impressed, but I have to use my organic, slow brain and fingers to write out WHY.

[johannab@cosocial.ca]

@fedicat @reiver

you know, after half a lifetime working in varying roles that amount to "making tech work for humans" ... the root cause is nearly always somewhere in the wetware.

Technology - tools, be it a hammer or some fantastical concept of an AI doctor to cure all your meat-suit mishaps - are not neutral because they are all human-created and human used. Even this one.

We've just unleashed a particularly large hammer, and allowed it into the hands of a abusive subset of us.

[julian@activitypub.space]

@smallcircles@social.coop AI is exceedingly good at being a sounding board for ideas. You just need to get past the relentless sycophantic responses, and think critically about each response.

If you even hint at it, AI will gladly tell you how to build a hammer to solve all your problems.

The problem is that some people use AI as a shortcut to no longer think.

cc @reiver@mastodon.social @fedicat@pc.cafe @johannab@cosocial.ca

[dansup@mastodon.social]

@reiver Vibe coding is a gateway to learning how to code, I'm all for it!

[uwehalfhand@norcal.social]

@dansup @reiver Is it? It may be a gateway to actually developing small to medium apps, but I think it’s becoming increasingly clear that it removes the learning aspect (not just of programming, but writing and graphic design etc too).

[aj@social.dunevent.net]

@reiver@mastodon.social

Overall, I'm anti-"vibe coding" because new coders don't always know enough to see the logical fallacies, security vulnerabilities, etc. It's not usually a big deal if you're just making a simple desktop app but it can have huge implications for software that is open to the internet, has an expectation of properly handling user data, and needs to compatibly interoperate with other servers. Also, the energy and theft problems inherent to all "AI" use.

But I think we should be pragmatic. "Vibe coding" not going anywhere, so doing what we can to help keep everyone as safe as we can while stopping poorly understood code from DDOSing across the fediverse is the more mature path.

That doesn't mean we shouldn't discourage "vibe code" or at least encourage gaining education and/or experience before relying on it, though.