No, you misunderstood. It’s five "nein"s. As in:
“Is it available now?”
Hope this was a whitrhat effort to fix their mess.
Jesus fucking christ, did Github expose its own fucking Github credentials?
Via having LLMs write and push its own updates, live, to production, where they were immediately scruntinized by… other LLMs doing ‘penstesting’?
We’re gonna run outta honking noses and squirting flowers, the clown show is becoming too immense.
Either that or we’re going to need to quarantine Github, actually make the fucking Blackwall before these things gain not sentience, but roughly the judgement skills of a toddler, armed with nuclear weapons.
Every technology invented is a dual edge sword. Other edge propulses deluge of misinformation, llm hallucinations, brain washing of the masses, and exploit exploit for profit. The better side advances progress in science, well being, availbility of useful knowledge. Like the nuclerbomb, LLM “ai” is currenty in its infancy and is used as a weapon, there is a literal race to who makes the “biggest best” fkn “AI” to dominate the world. Eventually, the over optimistic buble bursts and reality of the flaws and risks will kick in. (Hopefully…)
I posted this 9 months ago, and we are now at somewhere “brain washing of the masses, and exploit exploit for profit”.
Butlerian Jihan when?
This would all be less funny to me if it wasn’t so incredibly broadly predictable.
Last week, some LLM bot commented under one of our issues and it became apparent pretty quickly, that it is a bot. So, I went to report it (incredibly the report menu did say they want reports for bots).
I filled out the reporting form probably five times in total, trying at different times of the day. Every time, I got an error 500 (Internal Server Error) as response.
Later, I checked my mails, and saw that actually two of my reports did go through, meaning I created two tickets on their side.What those mails also said: They’re very sorry, if it takes longer, since they’re currently experiencing a higher number of reports.
Gee, I wonder why.
Nine fives
Four tens
Ooh that’s a good roll, idk if I can beat that… unless you’re bluffing
That’d be terrible
New goal: nine fives of uptime
Woah, now, you’re talking about the premium tier.
The calls were coming from inside the building.
Microslop does it again! But it will take much more than this for people to leave GitHub. Someone will have to start making private repositories public to show that GitHub can’t be trusted for companies to leave. And someone will have to insert malware into GitHub releases from inside the system to make opensource people leave.
As someone who has never really used github (I have for a few minor FOSS contributions… very short touchpoints) but use self hosted git…
… what is github even fucking offering???
From my naive perspective it’s a light touch web ui on git?
I don’t understand what gravity well it provides… what escape velocity is required to bail on it.
From my naive perspective, I’d have as much allegiance to ot as I would be to an ftp server. Not happy? NP, I’ll take 17 minutes to move to 1 of 9999999 other equivalent services, or take 95 minutes to self host a functional equivalent.
There is a lot offered on the enterprise side. My company uses GH Actions for CI/CD, uses GitHub for OAUTH, it hosts our git LFS server, and it’s where the slop lovers in the executive and management offices get their copilot fix. That doesn’t cover half of it really, but it’s a lot more than a git forge. I despise it nonetheless and think all of these use cases have better tools available
And someone will have to insert malware into GitHub releases from inside the system to make opensource people leave.
And even that wouldn’t be enough for some of them, given SourceForge’s continued existence.
You’re unfortunately right. Some people just have picked a side and won’t budge.
Someone will have to start making private repositories public to show that GitHub can’t be trusted for companies to leave.
What if it’s private, but used as training data for copilot, and can only be accessed publicly through prompt injection?
Bad, but not the same, IMO. Microslop could shove it under the rug as a glitch. Oh wait… they would do that in this case too. Yeah, maybe it’d have to be more severe than that, but I don’t know what’s more severe to a private company than getting their IP leaked because of slopcoding.
