povoq@slrpnk.net

Current blades are made from fiber reninforced plastic, which is hard to recycle.

But I agree that the recycling wood part of it is largly PR and to attract government funding.

Relatively easy local production could be quite an advantage though.

Seems not too bad. It does boot with mainline Linux and the vendor releases patches for recent kernel versions, which is much better than most ARM SoCs.

Cool, let us know how it goes and maybe also see if the power consumption has improved with more recent kernel versions.

Seems indeed relatively good value for money, but how is the mainline Linux kernel support for that SoC?

It’s fairly easy indeed and works well: joinjabber.org/tutorials/service/unifiedpush/

It’s not prejudice if it is objectively true 🤷

Most LLM users don’t try to hide it and the commit pattern is a result of the LLM assisted workflow, thus without losing the perseived benefits of using LLMs it can not be easily hidden. And the pattern isn’t only about when but also what. You might be oblivious to it, but the pattern is very clear and not possible to mistake with regular code writing patterns in an overall project. It is harder to spot in individual smaller PRs though, but that isn’t what Codeberg’s new policy is targeting.

And anyways, this isn’t a question of “wrong-think”, but simply of Codeberg not wanting to be associated with such low quality, likely copyright violating and resource hogging projects. The LLM using people have plenty of other code forges to use, so it is really a non-issue 🤷

No need to asdume that. Just by using LLM to assist with code writing, the human in the loop changes their commit pattern.

Sorry but you are clearly delusional. There is no magic involved, just being able to look at the structure of the code and the pattern of the commits. It’s fairly easy in fact.

Are you trying to make some point? Because, yes they can.

There are plenty of other public git forges you can migrate your LLM assisted projects to 🤷

You might not be able to tell, but the signs something is LLM generated are pretty obvious to more experienced programmers.

Yes, that is what the term “derivative work” referrs to.

Indeed, this ruling says nothing about something being a derivative work, all it says is that AI generated works can not create new copyright claims, which is totally sensible and non-controversial.

Looks like the bad HN commenter takes are leaking 😑

Those comments on HN are hilarious 😅 That site really works as a parody of bad tech bro takes if you ignore that most of them are sadly dead serious.

Apparently not:

We have a no-AI contributions policy. This is because, generally speaking, LLMs generate code that, while may work, is poorly organised and difficult to maintain.

They seem to have moved the client into the main repo.

I guess it could be useful to discover and download open-source and drm-free freeware games.

So this would allow you to self-host a library of open-source games and have people connect to it with their Steam like clients to always have the latest version installed and so on?

Getting relatively non-technical people to install the correct versions for multiplayer games is a real pain without something doing it for them like with Steam.

Super lightweight, and a fixed IP is not necessary, but yes you need to expose it somehow if you actually want to use it outside your home.

Definitly missing an XMPP server 😅

snikket.org works well with XMPP under the hood.

Not yet, no. There is some preliminary work merged, but it doesn’t seem like it will fully arrive soon.

This tutorial seems to work for basic Iocaine, but the Nam-Shub of Enki part is failing here.

Also somehow Iocane works for other websites here, but in front of Lemmy it currently fails. Not sure why.