Kogasa

Before I blocked the instance I had nothing but miserable interactions with Hexbear users, and it had nothing to do with political opinions.

Mesa is usually pretty quick to update, it’s just that stable distros won’t update mesa all that quickly. I assume most of them have some way to install a newer mesa from a community repo or something.

Docker desktop is a GUI frontend for docker

Semantic embeddings are a thing. LLMs “work with tokens” but they associate them with semantic models internally. You can externalize it via semantic embeddings so that the same semantic models can be shared between LLMs.

Chrome takes so much longer than the kernel somehow. There’s also the occasional package that makes you build single-threaded because nobody has fixed some race condition in the build process.

Literally just install GNOME

Nothing wrong with it, it’s just boring. Fish shell has some new features that make it nice to use. So does zsh. Tab completions, history navigation, plugins and such.

Step 1: Install a Wayland compositor of your choice Step 2:

Swapping CPU manufacturers entirely? I’d just start my kernel config fresh. Pull up the old one next to a new (default ) one and go down line by line. Odds are there are at most a few flags that would need to be changed, but it’s a good chance to reevaluate your previous decisions too.

It makes a HUGE difference in compile time. Which only matters if you’re building your own kernel anyway. It’s a solution for its own problem.

I think it’s a good learning experience though. There is genuinely a lot of stuff in there that you can easily, safely remove, and reading up on all the less obvious flags is fun.

It’s dynamic :)

scan qr code

ERROR_SXIFKK_INV_MEM_0

troubleshooting link is just a jpg of a frowny face

Fair point. I would say on a personal level that GitHub actions is quite nice to use, especially with the marketplace. But I’d be surprised if switching version controls also entailed a CI/CD change for Mozilla, so I can’t think of a good reason.

You’re quite the lunatic. I’m obviously not defending GitHub PRs, or saying Mozilla should or should not use them. I said “we are not open to PRs at this time” is not the same as “we will be open to PRs in the future.” The truth of that statement has absolutely nothing to do with whether or not Mozilla is, in fact, open to using PRs in the future. But there’s no point in telling you that, because you’re clearly unhinged. Have a good life.

How does the opinion of your supposed internal contact at mozilla affect the basic English interpretation of the public announcement?

Okay? Is this supposed to change something?

No. They’re just not publicly saying it’s off the table. Whether they’re entertaining it internally is a totally different question.

I’m only a native English speaker, so guess I could be interpreting it wrong.

You should try being a native English reader.

What it means is “they will not be accepting pull requests at this time.” Whether or not they are open to changing this in the future is not specified. They have not specifically stated that this is off the table, nor have they stated this is their intent.

That is not what that means

Reviewing PRs costs money/time