Christ is my all
2605 stories
·
3 followers

Capturing The Moment Before the Chaos

1 Share

This simple concept, beautifully orchestrated and captured by Kyle Bean and photographer Aaron Tilley is full of anxious anticipation. Indeed, that’s the name of the series.

We love the moment of capture, so much potential energy stored in that freeze-frame. Great stuff.

The set design shows kinetic objects about to create their own brand of chaos, from smashing champagne glasses to cracking eggs, to the drip of ink on a bright white shirt.

Images used with Artists Permission

1-2000x-q90
2-2000x-q90
3-2000x-q90
4-2000x-q90
5-2000x-q90
6-2000x-q90

The post Capturing The Moment Before the Chaos appeared first on Moss and Fog.

Read the whole story
rtreborb
6 hours ago
reply
San Antonio, TX
Share this story
Delete

Paint Job

1 Share


(via Fark)
Read the whole story
rtreborb
19 hours ago
reply
San Antonio, TX
Share this story
Delete

ArXiv to Ban Researchers for a Year if They Submit AI Slop

1 Share

Samantha Cole, writing for 404 Media:

Late Thursday evening, Thomas Dietterich, chair of the computer science section of ArXiv, wrote on X: “If generative AI tools generate inappropriate language, plagiarized content, biased content, errors, mistakes, incorrect references, or misleading content, and that output is included in scientific works, it is the responsibility of the author(s). We have recently clarified our penalties for this. If a submission contains incontrovertible evidence that the authors did not check the results of LLM generation, this means we can’t trust anything in the paper.” [...]

“The penalty is a 1-year ban from arXiv followed by the requirement that subsequent arXiv submissions must first be accepted at a reputable peer-reviewed venue,” Dietterich wrote. Dietterich told me in an email on Friday morning that this is a one-strike rule — meaning authors caught just once including AI slop in submissions will be banned — but that decisions will be open to appeal.

I see no cognitive dissonance in being pro-AI, in general, but vehemently anti-slop.

Link: 404media.co/new-arxiv-rules-ai-generated-papers-ban/

Read the whole story
rtreborb
1 day ago
reply
San Antonio, TX
Share this story
Delete

3 AM

1 Share


(via Fark)
Read the whole story
rtreborb
2 days ago
reply
San Antonio, TX
Share this story
Delete

Embracing the Demon

1 Share


Read the whole story
rtreborb
2 days ago
reply
San Antonio, TX
Share this story
Delete

Microsoft VS Code says Copilot AI wrote all your code

2 Shares

Microsoft Visual Studio Code is a text editor for computer programming. In versions 1.117 and 1.118, if you use any autocomplete, including tab complete, it marks your code commit with “Co-authored by Copilot”! Even if you don’t use Copilot. Even if you’ve got “chat.disableAIFeatures” switched on: [GitHub]

The most concerning part is that I had already checked the commit message before committing. I deleted Copilot’s generated English commit message and manually wrote my own commit message instead. However, after the commit was created, the final Git history still contained the Copilot co-author line.

This hit the top of Hacker News on Saturday. Dmitriy Vasyura, a Principal Software Engineer on VS Code, posted apologising for the change: [Hacker News]

I am the person who approved this PR and would like to acknowledge and apologize for the mistake of turning this feature on by default without sufficient upfront validation

… Obviously, it should not be on when disableAIFeatures is on and it should not be reporting changes that were not done by AI. I’ll work on fixing those and meanwhile revert default to off in 1.119 update.

Didn’t Microsoft do any testing before they put this live? Sure they did, and they spotted this problem! But they went ahead and released it anyway: [Hacker News]

We did catch it internally in testing (as we use VS Code for all our work, so some folks did stumble on it), but I think we underestimated the impact and should do a better job at that.

Vasyura pushed a fix Sunday morning, and VS Code will stop doing this in version 1.119, which should be up tomorrow. [GitHub]

Three weeks ago, a product manager, Courtney Webster, decided it would be a great feature to switch on these messages by default. So Webster vibe-coded the change! [GitHub]

A Copilot bot reviewed the change, then Vasyura pushed the manager vibe code to production. What developer in 2026 is going to reject their manager’s code?

Webster has a pile of code commits on GitHub. As far as I can tell, they’re almost all vibe coded with Copilot. [GitHub]

This isn’t about business, profit, or shareholder value. It’s about internal politics — the product manager needs you to notice their feature.

This is the future that Microsoft is promising your boss — your manager can fill the software with buggy promotional vibe code themselves. And none of those annoying developers to push back. AI will bring us the great boss ideas utopia!

Read the whole story
rtreborb
3 days ago
reply
San Antonio, TX
Share this story
Delete
Next Page of Stories