They’re using svn for sources :( mirrored to GitHub at least.

Damn, for a thief they’re really stomping and dragging (if that’s the right en term) their feet in the test video. Such loud and sandy foot steps.

and include expensive endpoints like git blame, every page of every git log, and every commit in your repository. They do so using random User-Agents from tens of thousands of IP addresses, each one making no more than one HTTP request, trying to blend in with user traffic.

That’s insane. They also mention crawling happening every 6 hours instead of only once. And the vast majority of traffic coming from a few AI companies.

It’s a shame. The US won’t regulate - and certainly not under the current administration. China is unlikely to.

So what can be done? Is this how the internet splits into authorized and not? Or into largely blocked areas? Maybe responses could include errors that humans could identify and ignore but LLMS would not to poison them?

When you think about the economic and environmental cost of this it’s insane. I knew AI is expensive to train and run. But now I have to consider where they leech from for training and live queries too.

That’s what the major part of version numbers is all about! /s

Feature World Lighting: not implemented

Lighting is server side? o.O

I guess because it influences creep spawn or sth?

I love Nushell

When I bash my head into a wall, does that count?

You always forget regex syntax?

I’ve always found it simple to understand and remember. Even over many years and decades, I’ve never had issues reading or writing simple regex syntax (excluding the flags and shorthands) even after long regex breaks.

I consider python a scripting language too.

Neo4j provided database software under the AGPLv3, then tweaked the license, leading to legal battles over forks of the software. The AGPLv3 includes language that says any added restrictions or requirements are removable, meaning someone could just file off Neo4j’s changes to the usage and distribution license, reverting it back to the standard AGPLv3, which the biz has argued and successfully fought against in that California district court.

The issue before the appeals court boils down to the right to remove contractual restrictions added to the terms of the APGL. This right is spelled out in AGPLv3, section 7, paragraph 4: “If the program as you received it, or any part of it, contains a notice stating that it is governed by this license along with a term that is a further restriction, you may remove that term.” Other GPLs contain similar terms.

“Licensed under AGPL but not AGPL”? It’s a named license that people have expectations on. I assume if they had said “licensed under aa modified AGPL license” it would have been fine? Seems reasonable/makes sense.

How does that become “may kill a GPL license”? Key word “a”? (When it’s not one.)

the docs are under documentation, not on the homepage tho

I always pronounced it engine-x (fluent as one word) but never thought of it meaning engine lol

n gin x -> en gin ex -> “enginex” spoken, nginx thought

These scrollbars with issue indicators are becoming more and more fancy

Is this limited to Swift?

Swift Build is a high-level build system based on llbuild with great support for building Swift.

Sounds like this won’t help C++ projects?

The requirements of sold developer license, physical mac hardware, and XCode make it hard to be interested or even feel it worthwhile unless you’re already a mac user.

Cloud build options only get you so far as well.

Where is he getting these stats from?

What do you mean? He’s the room owner. He can see the member count, and the activity.

I thought the same at first, but honestly, there’s probably nothing that warrants impersonation. If it’s a system announcement or change from the host, it should be labeled as such.

Windows is / Windows filesystems are case insensitive too.

On a Linux environment? Mind sharing the usage area?

I learned of those files outside the context of programming. When program or file zip packages contained these random ds store files and I looked up what they are.

Turns out, it’s metadata caching for macOS. Irrelevant and does not belong into [distributed or shared] packages.

/edit: It’s been a long time ago. Looking at it again, I guess it adds folder metadata, so it could be useful when distributing to other macOS. But for other OS, it’s noise. Either way, usually it’s not intentionally included.

Case insensitive handling protects end-users from doing “bad” things and confusion.