Kissaki

joined 3 years ago
MODERATOR OF
[–] Kissaki@programming.dev 4 points 11 hours ago (3 children)

No

https://github.com/LemmyNet/lemmy/issues/1872#issuecomment-958943903

Changing the username will break many aspects of federation. For other instances you will look like a completely new user, so you wont be able to edit or delete any old posts/comments. I really dont think its worth all the trouble when you can simply create a new account.

[–] Kissaki@programming.dev 2 points 11 hours ago

The developer used AI and it introduced bugs and that was bad for people.

Was it the AI that introduced bugs, or them, while working with AI there or in other parts?
Would the bugs not have occurred if they made the changes without AI?
Would they have made any changes without AI? Would we be better off without changes for security robustness?

You make it sound like a direct correlation. Having read their response, that seems like an assumption without reasonable foundation.

Changes always have a risk of introducing bugs.
I'm no friend of using AI without the necessariy expertise, but from their response, they seem to have taken a very thorough, reasonable approach, and they seem to have the expertise to do so.

[–] Kissaki@programming.dev 4 points 1 day ago (1 children)

I don't know the degree to that, but bugs do happen occasionally either way as long as there are changes. In the article, they explain why the changes are necessary. Prioritizing security over no-change-stability seems reasonable and warranted.

[–] Kissaki@programming.dev 1 points 1 day ago

This reasoning assumes any LLM-assisted change is faulty, right?

The linked article doesn't make me concerned. They seem to have the expertise, seem to apply due diligence and good practice around (selectively) using LLM.

Can people not directly involved in and working on the project assess the risks well? Do we not have to depend on author and project leadership expertise just like we had to before with any parts of development, management, and tool and infrastructure use?

I haven't looked up the original communication or drama, but I assume communication could have been much better. Maybe the commits didn't say much about the reasoning and due diligence that they describe in this article? Other than that, how can you make a better judgment about the changes than them without taking a thorough look and assessment?

[–] Kissaki@programming.dev 3 points 1 day ago* (last edited 1 day ago)

Have you read the linked article? They explain how they used AI. It's not like AI produced the code and that's it.

They also explain about this version and the next minor version.

[–] Kissaki@programming.dev 8 points 1 day ago (4 children)

In your eyes, is all AI-produced text and code slop? Or did you check on the Python tests they designed and implemented with the help of AI, and after analysis of that, you came to the conclusion that it's slop (as in nonsensical, incoherent, faulty, or similar)?

[–] Kissaki@programming.dev 6 points 1 day ago (3 children)

Is that your assumption given that they're using AI? Because it's not at all what I have taken away from their article.

Is "not properly maintained anymore" your interpretation of them using AI? Or what do you base that on?

[–] Kissaki@programming.dev 6 points 2 days ago (2 children)

I didn't get that feeling at all. They didn't make any such claims or used such wordings which I often see elsewhere.

[–] Kissaki@programming.dev 75 points 2 days ago (14 children)

Also, nobody actually knows if human intelligence is just finer grained stochastic prediction as well.

An interesting but valid argument. It doesn't make AI better than it is, but any human contribution and change can and often is also faulty. People have gaps of knowledge, sometimes unwarranted confidence, other times lack of care, or just miss things. It's not like we're comparing the perfect human vs faulty AI.

If you don’t mind the security risk then you can of course use an older release.

I haven't read the original rage/drama but I can imagine if from other drama instances.

This post is certainly a good, founded response.

There's some valid concerns in AI usage, but unwarranted or inappropriate harsh criticism when it's an established trusted developer and engineer - if we assumed good practice before then we could assume continued good practice. Maybe LLM is one point of increasing skepticism, but criticism should be open, respectful, and fair.

They invested a lot of time and effort into a public good project. In that context, they deserve at least respectful and non-worst-assumptuous criticism.

[–] Kissaki@programming.dev 1 points 3 days ago

the original 2FA gets thoroughly bypassed in the process

arstechnica reports that 2FA protects you, also KrebsOnSecurity

On May 31, the pseudonymous open source intelligence researcher ZachXBT posted on X about how “the Meta AI support is garbage and has lots of access perms which allowed you to reset passwords to any user without 2FA and did not verify who you are.”

ambiguous formualtion, can be read both ways; but much more explicit:

The hackers reported their exploit failing against any accounts that had enabled multifactor authentication (MFA), including the “least robust form of MFA that Instagram offers” in the form of one-time codes sent through SMS, according to KrebsOnSecurity.

Securing your various online accounts means taking full advantage of the most secure form of multi-factor authentication (MFA) offered (such as a passkey or security key). In this case, even using the least robust form of MFA that Instagram offers — a one-time code sent via SMS — likely would have blocked the exploit: The hackers who released the video on Telegram said their exploit failed to work against any accounts that had MFA enabled.

[–] Kissaki@programming.dev 1 points 3 days ago* (last edited 3 days ago)

Inspected, looks like even hidden-behind elements receive matrix transformation updates.

Presumably, skipping those could increase performance? But maybe it's not possible with this approach. I haven't checked deeply. I guess it's infeasible.

The browser's compositor handles the 3D layering.

[–] Kissaki@programming.dev 2 points 3 days ago

But someone should!

 

s&box, from the creator of the popular Source Engine sandbox Garry's Mod, released three days ago. s&box is based on the Source 2 engine, and not only a sandbox but a game development and publishing platform, including publishing on Steam.

The news post one day after release openly covers the mixed ratings, public finances, doubling their play fund that pays creators, and public roadmap.

I was surprised to see they openly and transparently publish day-by-day finances.

The public performance stats are interesting too.

Refreshing. I wish more publishers would do these kinds of things with deliberate open communication and transparency.

Their metrics pages:

 

Syntax Highlighting

Edit v2 adds the Lightweight Syntax Highlighter. It has a ~40kB footprint for a dozen languages plus runtime, barely grows with each language added, and runs at >100MB/s.

The highlighter is based on a simple programming language that combines regular expressions with explicit control flow. It's designed such that the runtime can be easily ported to other languages, including JavaScript.

From 1.2.1 to 2.0.0, the edit binary size increased from 267 to 330 kB for win exe and 217 to 300 kB for linux binary.

What is edit? README intro:

A simple editor for simple needs.

This editor pays homage to the classic MS-DOS Editor, but with a modern interface and input controls similar to VS Code. The goal is to provide an accessible editor that even users largely unfamiliar with terminals can easily use.

 

Corridor Digital released an open-source greenscreen keyer/extractor, powered by AI, usable on consumer GPUs.

The video covers what happened after their initial release, community and professional responses, interviews with professionals about what can be improved, and finally a practical test/example in Davinci (Video Editor).

 

Explores how the Lean programming language handles 2 + 2 = 4, which other programming languages collapse into a bool, but Lean considers a Proposition, and requires Proof.

How does provably correct programming look? This article seems to give a good introduction and example.

 

Explores how the Lean programming language handles 2 + 2 = 4, which other programming languages collapse into a bool, but Lean considers a Proposition, and requires Proof.

How does provably correct programming look? This article seems to give a good introduction and example.

 

Pike is a dynamic programming language with a syntax similar to Java and C. It is simple to learn, does not require long compilation passes and has powerful built-in data types allowing simple and really fast data manipulation.

int getDex()
{
  int oldDex = Dex;
  Dex = 0;
  return oldDex;
}

private void
show_user(int|string id, void|string full_name)
{
  write("Id: " + id + "\n");
  if (full_name)
    write("Full name: " + full_name + "\n");
}
 

The Go 1.18 release introduced generics and with that a number of new features, including type parameters, type constraints, and new concepts such as type sets. It also introduced the notion of a core type. While the former provide concrete new functionality, a core type is an abstract construct that was introduced for expediency and to simplify dealing with generic operands (operands whose types are type parameters). In the Go compiler, code that in the past relied on the underlying type of an operand, now instead had to call a function computing the operand’s core type. In the language spec, in many places we just needed to replace “underlying type” with “core type”. What’s not to like?

Quite a few things, as it turns out! To understand how we got here, it’s useful to briefly revisit how type parameters and type constraints work.

For the Go 1.25 release (August 2025) we decided to remove the notion of core types from the language spec in favor of explicit (and equivalent!) prose where needed. This has multiple benefits: …

 

However, there are some important features that WinSock just doesn’t expose. […]

Rust’s current async ecosystem is built atop a particularly cursed concept. It’s an unstable, undocumented Windows feature. It’s the lynchpin of not only the Rust ecosystem, but the JavaScript one as well. It’s controversial. It’s efficient. […] Without it, it’s unlikely that the async ecosystem would exist in its current form. It’s called \Device\Afd, and I’m tired of no one talking about it.

 

However, there are some important features that WinSock just doesn’t expose. […]

Rust’s current async ecosystem is built atop a particularly cursed concept. It’s an unstable, undocumented Windows feature. It’s the lynchpin of not only the Rust ecosystem, but the JavaScript one as well. It’s controversial. It’s efficient. […] Without it, it’s unlikely that the async ecosystem would exist in its current form. It’s called \Device\Afd, and I’m tired of no one talking about it.

view more: next ›