You don’t think the creators should get paid? Do you know how much effort goes into making quality videos?

Ironically it’s probably because so many of the slop videos try and copy their style. However I would have thought YouTube would be more proactive with a channel with 25M subs.

Hmm I see nothing - I guess the posts don’t federate back to .ml?

I joined the .ml server because it was the dev server. Looking at the communities I subscribe to most are on other servers. Occasionally people ascribe beliefs to me based on my home server but so far I haven’t bothered looking for a new home.

When I first joined there were a bunch of popular instances that closed down so choosing a non-dev server seemed like a bit of a gamble. Same with mastodon servers.

We also have the very catch all of “disturbing the peace”. Some friends of mine got done with that because the police had been called despite no actual crime being committed. They were eventually “bound over” for a year which is basically a deferred fine to encourage you not to do anything that attracts the police’s attention.

On the other hand it’s legitimately one of the wonders of the digital world. A communally edited source of knowledge free for all to access. While it’s good to scrutinise foundations and how they are run I’ve not seen anyone propose a better solution so far. The data is freely licensed so forking is possible but it’s not really the technical details that make Wikipedia the resource it is today.

Debian for the stable base flatpak/snap/src for the bleeding edge apps.

Sure, you own a little bit more of it with every mortgage payment.

I guess it depends if you have a maximum number of kids your planning on. But a family of four is pretty likely to stay put for at least 10 years which should be long enough to iron out any short term fluctuations in the market. I’m not overly worried by the slight dip in valuation since I bought my last house because a) I have somewhere for my family to live that is secure and b) whenever we do eventually sell the capital will cover the next house.

My old bosses dacha sounded nice until he pointed out how cold it could get in the winter as it was essentially only heated by a stove. I guess it’s nice for a summer getaway from the big city - a bit better than a tent.

I think the two principle arguements he’s making are open weights allow for misaligned models and these models are using distillation to more efficiently train.

I don’t really care about the distillation point - it seems it’s just hoovering up the internet with extra steps. It’s really up to Anthropic to deal with by enforcing their ToS. Sauce for the goose etc…

I can see the argument about alignment but it’s not a new problem. In the FLOSS world we generally don’t put restrictions on use on the code we release even if it might get used for bad stuff. It certainly wouldn’t hurt for the authorities to test open models to find out where the guardrails are but ultimately rather than banning the tech you need to enforce the law against the people that use the tech to do bad stuff.

If you can get your reproducer in a one liner, e.g:

cd builds/bisect && make clean && make -j(nproc) && make run-failing-test

then it’s super easy to pass that to /bin/sh -c “…as above…” to feed to the git bisect command

My first professional job was writing FORTH for fruit machines. I’d played with it a bit before on the Jupiter Ace we had which sadly never really took off despite being more elegant than the ZX81.

What do you need/use that you find in modern editors that you can’t get in something like Emacs? While there are AI integrations for Emacs they are all optional.

Mine are all GPLv3 or forks of other repos and they are listed. I’m sanguine because the license allows for study and if it’s good enough for humans I don’t see why it’s not for clankers.

I mean scientists have been going on about global warming for some time now and no one seemed to listen to them then. Not sure why they are turning to scientists now.

I’ve long been off the critical path because as a tech lead I have a lot more random stuff (and meetings) to deal with. I’ve been able to vibe code some non-production stuff like scripts to unify feature lists across JIRA, specs and the upstream docs which has helped free up time to hand craft more code on production.

I don’t care too much about the quality or maintainability of those scripts as long as they make my life a bit easier. I do care about the maintainability of the production code base.

The last big update to my git workflow was when I discovered --update-refs as it makes maintaining a stack of feature branches much easier. So far I really only have one “main” dev branch and then peel off the sub-branches at they need merging upstream.

However I shall have to investigate how the history commands are exposed in magit. I can see it being useful if you have long held branches that take a while to upstream but are useful to have in your trees.

Just an early example of AI psychosis

In QEMU all of our CI environments are replicable locally as docker/podman images. However usually flaky CI is due to races exposed on overloaded runners so I often also run make -j(nproc) at the same time to simulate that. A retry script is also useful to get an idea of how stable a test is. Having sanitizer builds can also help.