I thought you were a little harsh, but after looking further I don't disagree.

It's way too early for this to be in HN.

Gotta be a good thing, extra points.

Nobody asked

good

https://developers.stoat.chat/developing/contrib ``` Please do not open PRs generated with LLMs. ```

And how is it bad?

Read: write your PR. It doesn't say "do not contribute code touched by LLM".

It asks to take accountability for the thing you submit.

Technical output written by LLM is often very hard to read due to the ticks, fillers, fluff and idiosyncrasies. Even with rules or guidance.

This contribution rule ensures crap will be edited out and only the valuable content submitted. Cleaned up LLM code can be very valuable.

What was the stat? Was it 85% or 95% of LLM generated PRs are trash that should be ignored?

Developer gets it.

Unfortunately Chatto is not accepting contributions

You didn't deny anything he said

If you think long and hard about it you'll see I did.

But if you must you can call me a moderately progressive Marxist.

This is a techie shit posting forum not a court of law, calm your tits down

> it's literally a feature that cannot be found with GUIs Yes, it can.

Cursor has this, and there are others that can attach to ssh or open their UI via a tunnel or web interface.

SSH is mighty convenient though, so I am not necessarily saying your point is incorrect.

Did you even check what hash they are using?

SHA-256. Did you? My point isn't constrained to this exact service, though. My point is that the XKCD-style passphrase is in general not secure. If you make a habit of using it, assuming that the service in question will take care of securing it super duper safely on your behalf, you will get bitten when a service doesn't do this.

If character class constraints are enforced then that password becomes incredibly strong though - e.g. require a capital, and special characters and a number.

Plenty of sentence passwords meet that but now the probability space has exploded.

No need to announce

Why these animations in the github README? why? It just made understanding anything more difficult

We made this for X audience initially but got a lot of praise for it on reddit, so decided to put in the README. Sorry it made it more difficult for you.

That's fine, then there is no need to lie like you did.