Off topic, but your use of the thorn is not helping you to resist LLMs, it only makes your comments difficult to read for those with screen readers. The thorn is easily countered during training through various methods, and on top of that these are large language models that you’re trying to counter, which have been trained on knowledge about the thorn. Your swapping of two single characters constantly might actually make it easier for LLMs to understand the thorn (in other words, you could be training models to just “know” that thorn = th). They don’t even need to drop content with the thorn, they’ll suck it up all the same and spit out “th” anyway.

Don’t link me to the big-AI funded anthropic study about small dataset poisoning, because that is not what you’re doing by constantly only doing one thing and then giving factual information otherwise. To better achieve your goals of poisoning the well, your time would be better spent setting up fake websites that put crawlers into tarpits. Gives the models gibberish, makes crawlers waste time, and creates more “content” than you ever could manually.

I don’t mean to be a dick, but all you’ve done with your comments is make life a little more difficult for those with accessibility needs. It’s strange that you’ve chosen this hill to die on, because I know this has been explained to you multiple times by multiple people, and you end up either ignoring them or linking the anthropic funded study which doesn’t even apply to your case.

Containers are the best, so probably

Those both work fine in Wayland.

I use Bazzite for devwork too, I do use distrobox though which allows me to get proper dependencies without layering more onto the system image.

My bank apps work on Graphene with the exploit protection compatibility mode enabled, even the ones that require Play Integreity API.

It should be noted that while you can do this, it can increase your attack surface, defeating a lot of the point of Graphene. Before I started using Graphene, I was a huge fan of rooting and getting full control of my device, so I definitely understand the appeal. But I don’t think I would root Graphene myself, automated or otherwise.

My fucking neighbors just keep letting their outdoor only cats reproduce and get mad when they meow for kibble. It’s the worst. My county has a well funded TNR and last litter program, but they don’t give a shit. I’ve done TNR of at least 8 or 9 cats and they just keep coming.

These aren’t even the completely wild and feral cats or anything (since the shitty neighbors feed them from time to time) although I’m sure their offspring has made some feral cats by now. It’s horrible.

Any Austin is great

The only real way to do heat transfer in space is through infrared. But that is not very efficient, so most compute in space is managed to reduce heat as much as possible. Data centers, or even just a few 2-4u servers with GPUs produce significantly more heat.

What if the craft is in the sun? Then, you not only have to dump the heat from the onboard servers, but also the sun. These changes are rapid, and not easily managed. Plus, the cold side would still need something to radiate into. Heat does not transfer the same way in a vacuum, even closed loop systems on the ground need air to dump heat into. And these companies don’t even want to use that because it’s not efficient, so they waste our water instead.

Make it make sense.

Server farms, especially ones with tons of GPUs, see little benefit from being in LEO. They cannot radiate heat efficiently, especially this amount of heat. Plus, unless boosted every now and then, they’ll eventually burn up.

How do you fix a hardware issue up there?

None of it adds up on the balance sheet. It makes zero sense to do this in space. The only benefit is hyping up the AI market because space. That benefit won’t last very long in our newscycle.

The new repo has two releases in it now. These releases are not signed with the original key as far as I can tell. Further, GitHub is silently redirecting to the new repo, even in Obtainium, meaning it’s possible that if you had this previously installed via Obtainium and updated now, you may have unsigned apks installed that may or may not contain the changes in the repo.

This is a mess. I deleted the repo from Obtainium (luckily I don’t auto install updates) and will wait to see what happens over the next few months. Might just save my notes in a network share instead of using syncthing from my phone. Idk, notes are all that I was using it for.

Watch for spicy pillows… they’ll light your stuff on fire.

Well, yes, but that is not exclusive to Pixels, and in fact, most phones (other than the latest iPhones) are more vulnerable. Pixels, especially the latest devices, have the best hardware security features of any Android phone (unfortunately). You’re focused on Pixel, but that’s only because of the recent leaks which specifically focused on Pixel because of their breaching difficulty. Here’s the full matrix from last year (which hasn’t leaked as recently):

https://discuss.grapheneos.org/d/14344-cellebrite-premium-july-2024-documentation

GrapheneOS, even now, is not vulnerable for several reasons, most of which tie into the hardware features of the Pixel. There’s a reason Graphene only works on Pixel.

All I’m saying is that it’s entirely misleading to imply that only Pixels are vulnerable. This is not the case, even for iPhones.

I’m also not sure why you seem to be trying to say I disagree on the fact that Google is happy to leave vulnerabilities wide open, when that is exactly what I said in my original comment. Their new release schedule allows them to leave these vulnerabilities open for an even longer time, making Cellebrite’s job easier.

The law enforcement angle is exactly the point, yep.

Everyone who eats and drinks chemicals will eventually die!

If you’re talking about AWS, AWS does much more than just cloud storage.

The AI we’ve had for over 20 years is not an LLM. LLMs are a different beast. This is why I hate the “AI” generalization. Yes, there are useful AI tools. But that doesn’t mean that LLMs are automatically always useful. And right now, I’m less concerned about the obvious hallucination that LLMs constantly do, and more concerned about the hype cycle that is causing a bubble. This bubble will wipe out savings, retirement, and make people starve. That’s not to mention the people currently, right now, being glazed up by these LLMs and falling to a sort of psychosis.

The execs causing this bubble say a lot of things similar to you (with a lot more insanity, of course). They generalize and lump all of the different, actually very useful tools (such as models used in cancer research) together with LLMs. This is what allows them to equate the very useful, well studied and tested models to LLMs. Basically, because some models and tools have had actual impact, that must mean LLMs are also just as useful, and we should definitely be melting the planet to feed more copyrighted, stolen data into them at any cost.

That usefulness is yet to be proven in any substantial way. Sure, I’ll take that they can be situationally useful for things like making new functions in existing code. They can be moderately useful for helping to get ideas for projects. But they are not useful for finding facts or the truth, and unfortunately, that is what the average person uses it for. They also are no where near able to replace software devs, engineers, accountants, etc, primarily because of how they are built to hallucinate a result that looks statistically correct.

LLMs also will not become AGI, they are not capable of that in any sort of capacity. I know you’re not claiming otherwise, but the execs that say similar things to your last paragraph are claiming that. I want to point out who you’re helping by saying what you’re saying.

Containers are better than any other option, so of course they’re being used! I’m gunna use containers even harder!

They’re making their own phone now. It’s not going to die, at least not in that way.

Up 1% for the day