I don’t view free-use models as open-source. Open-source means I can rebuild it from scratch and I can’t because I don’t know what the training data is, or have access to it.

The scale is the difference and who is harmed.

Billion dollar company losing $100. Who cares?!

Billion dollar company stealing from all artists in the world. We care.

Points 2 and 3. Basically make restrictions on normal user accounts which are fine for humans but that will make bots swear and curse.

Unless you mean “what should the registration process be” I think API keys via a user account would do.

…but if they don’t know I expect them to say so. An LLM isn’t trustworthy until it says “I don’t know”.

Exactly the reason I suggest it.

An LLMs “intent” is always to give you a plausible response even if it doesn’t have the “knowledge”. The same behaviour in a human would be classed as lying IMHO.

1. Make bot accounts a separate type of account so legitimate bots don’t appear as users. These can’t vote, are filtered out of post counts and users can be presented with more filtering option for them. Bot accounts are clearly marked.

2. Heavily rate limit any API that enables posting to a normal user account.

3. Make having a bot on a human user account bannable offence and enforce it strongly.

Agreed, It wouldn’t be a good thing. However it’s their own failures and mismanagement that are causing it.

It’s certainly arguable that the algorithm constitutes an editorial process and so that opens them up to libel laws and to liability.

Fair point.

Stupid sharks loose their teeth, not their fins that actually do the work.

Errr…wat!!!

The shark dies either way.

Under what law?

UK currently holds the people that post things liable for their own words. X, the platform, just relays what is said. Same as Lemmy. Same as Mastodon.

If you ban X I don’t see why those other platforms wouldn’t be next.

Now should people/organisations/companies leave X? Absolutely! Evacuate like it’s a house of fire. Should it be shut down by legal means? No.

Screen 0 deleted because of no matching config section.

Your XOrg conf ig has got hard definitions of your devices which aren’t matching what is being detected. Probably best to let auto detection do it’s thing.

Arch people tell you “I use arch BTW”

Rust people make PRs rewriting your code in rust.

Rust people are worse.

Memory ownership isn’t the only source of vulnerabilities. It’s a big issue, sure, but don’t think rust code is invulnerable.

That’s disengenuous though.

• We’re not forcing you to learn rust. We’ll just place code in your security critical project in a language you don’t know.

• Rust is a second class citizen, but we feel rust is the superior language and all code should eventually benefit from it’s memory safety.

• We’re not suggesting that code needs to be rewritten in rust, but the Linux kernel development must internalise the need for memory safe languages.

No other language community does what the rust community does. Haskellers don’t go to the Emacs project and say “We’d like to write Emacs modules, but we think Haskell is a much nicer and safer functional language than Lisp, so how about we add the capability of using Haskell and Lisp?”. Pythonistas didn’t add Python support to Rails along side Ruby.

Rusties seem to want to convert everyone by Trojan horsing their way into communities. It’s extremely damaging, both to those communities and to rust itself.

The question was “How do you define GPL compatible?”. The answer to that question has nothing to do with code being split between files. Two licenses are incompatible if they can’t both apply at the same time to the same thing.

…because they are incompatible licenses.

Not under a license which prohibits also licensing under the GPL. i.e. it has no conditions beyond what the GPL specifies.

My experience is that AMDs virtual memory system for VRAM is buggy and those bugs cause kernel crashes. A few tips:

0. If running both cards is overstressing your PSU you might be suffering from voltage drops when your GPU draws maximum power. I was able to run games absolutely fine on my previous PSU, but running diffusion models caused it to collapse. Try just a single card to see if it helps stability.

1. Make sure your kernel is as recent as possible. There have been a number of fixes in the 6.x series, and I have seen stability go up. Remember: docker images still use your host OS kernel.

2. If you can, disable the desktop (e.g. systemctl isolate multi-user.target, and run the web gui over the network to another machine. If you’re running ComfyUI, that means adding --listen to the command line options. It’s normally the desktop environment that causes the crashes when it tries to access something in VRAM that has been swapped to normal RAM to make room for your models. Giving the whole GPU to the one task boosts stability massively. It’s not the desktop environment’s fault. The GPU driver should handle the situation.

3. When you get a crash, often it’s just that the GPU has crashed and not the machine (Won’t be true of a power supply issue). sshing in and shutting down cleanly can save your filesystems the trauma of a hard reboot. If you don’t have another machine, grab a ssh client for your phone like Juice SSH on android. (Not affiliated. It just works for me)

4. Using rocm-smi to reset the card after a crash might bring things back, but not always. Obviously you have to do this over the network as your display has gone.

5. Be aware of your VRAM usage (amdgpu_top) and try to avoid overcommitting it. It sucks, but if you can avoid swapping VRAM everything goes better. Low memory modes on the tools can help. ComfyUI has --low-vram for example and it more aggressively removes things from VRAM when it’s finished using them. Slows down generations a bit, but better than crashing.

With this I’ve been running SDXL on a 8GB RX7600 pretty successfully (~1s per iteration). I’ve been thinking about upgrading but I think I’ll wait for the RX8000 series now. It’s possible the underlying problem is something with the GPU hardware as AMD are definitely improving things with software changes, but not solving it once and for all. I’m also hopeful that they will upgrade the VRAM across the range. The 16GB 7600XT says to me that they know <16GB isn’t practical anymore, so the high-end also has to go up, right?

It’s meant to be that malloc fails and the application handles it.

Trouble is applications are written expecting it to never fail.