charcircuit

adjust up or down to reach sell frequency desired.

Start with price too high lower it over time until it sells.

These are the same strategy.

I agree, other formats, both textual and binary should be tested.

Even in today's world of modern iPhones, there's nothing that lets you easily jump to a specific part of an audio or video and re-record sections of it in the same way you can with a cassette.

Don't most DAW have a feature like this built in? I've also seen Final Cut Pro have a record button that can do something similar for video.

There are already browser extensions similar to this.

But are those bounded on the speed of tokenization?

I have paid API rates. I needed AI to cleanup file space and I didn't want to gamble with the alignment of Chinese models.

You can't censor Bitcoin.

Your payment processor could be legally restricted from paying you your bitcoin.

DAI exists and is not able to be frozen, but if the merchant's AI system flags a bitcoin transaction do you think you'll be able to cash that out? Just because they can't block it at the protocol level that doesn't mean they'll sign the transaction to send it to you.

Bitcoin - the only legitimate cryptocurrency secure enough for transacting at scale.

I prefer the trend of using stable coins for payment instead. I think merchants are much more willing to work with a digital dollars than with something with constantly fluctuating value.

As they are both distributed systems there will be some inherit underlying similarities, but a botnet has things like antidebug, stealth, privilege escalation, etc. They typically include attack payloads or spying features like taking screenshots, keyloggers and stealing account information. Additionally they may include further ways of spreading to other computers such as messaging people on Discord or using other vulnerabilities. They might also try and take exclusive control of the device by patching security vulnerabilities and uninstalling other malware. Well unless they sell dropper capabilities letting other people deploy malware to the machine.

This still exists today. When a new song gets released on YouTube for example a group of people close to it in latent space gets it recommended. By seeing a recommendation of a song in your feed you are part of a cohort of people with similar tastes.

The TFA explains that it is up to game to decide if they want to use attestation.

“The risk is amplified when consent comes from individuals within the household who use the device but shouldn’t give consent, such as minors.”

Note that the same applies for the other privacy invasive webos features. But since that doesn't harm big tech's monopoly they will conveniently avoid mentioning it.

If you don't want to share your internet with others, that is your choice, but please don't make seem like you are only sharing the internet with criminals. That is a harmful belief to spread.

Most traffic is normal scraping like checking amazon prices.

Just because others abuse privacy doesn't mean that we should remove privacy from everyone else. They also let you get around geoblocking.

Along with everything else. These parameters can make speculative decoding less accurate increasing the inference cost.

You can also use a hex editor to modify compiled binaries

It would be like if someone gave you a prompt you could pass into ChatGPT to produce the entire Linux kernel. While yes you could modify that prompt and then spend a ton of money on inference to generate millions of lines of code which hopefully are equivalent to the original Linux kernel it would be easier if you just had the source code to work with where you can make a simple extension. If you want to end a model you want the weights, and not the entire setup to generate it. The weights are the starting point that you can work off for training a new model similar to how the source code is the starting point people want to work off of.

Training runs are not deterministic. Not just in the case of floating point not being associative, but nodes have hardware issues and go down and back up at various points through training. Problems get encountered and then various parameters get changed during the middle of a training run.

Making the process of creating the source code repeatable goes beyond the idea of open source. Open source is about being able to work with the code, not recreate it. It doesn't require domain experts to document every single thing they know. For example look at some of the GPU drivers in the Linux kernel. The GPU is not properly documented and there is trust that vendors are implementing things correctly.

The training corpus + training code is just an automated editor for the weights. It would be like requiring the source code for Visual Studio for software made within it to be open source.

Weights are not an output artifact no more than source code is. There is never a moment where you can claim that it's done. As requirements change new ways to change the weights / code come up. With different projects you might want to import the weights / code into a bigger model / codebase.

The weights are the "source" of a model.

Can you precisely describe what the goal of #1 is. For flatpaks an app's dependency can be specified with a sha256 of the artifact or a specific commit of the dependency.

It's wild that such a big company is openly admitting they hacked into another company. This is an easy CFAA lawsuit.

And then there solution for HuggingFace raising the concern that OpenAI couldn't help do forensics wasn't to fix their safe guards, but to introduce them into a special program. The next company they hack might not be in that special program either so the guidance of having an open model on hand still applies.

Slack already has an API for building bots. It doesn't need to be open.

Let’s now assume our attacker has a really powerful machine, has gotten your salt and now will compute their own “table”.

You should be using a TPM so such an attack is impossible. The TPM should be what is rate limiting the guesses. You don't need a KDF here.

I suggest you take a look at Fedora Silverblue. It accomplishes all 3 of those goals.

It would still not allow downgrades to work properly

If you really need this, then there are options like swapping the linker with an older version or making a hardcoded linker that now points to an older one.

It would cause glibc/ld.so to have a harder time adding new features, as they now need to worry about incompatible versions being used together

Every language runtime has to care about not breaking compatibility with apps that have been released already. This is not a new or unique problem.

in ways that can be subtly incompatible

There is much more value to be had in making glibc properly backward compatible so you can have a single one that can be used with everything than trying to make it so that you can swap everything around, creating extra complexity and compatibility risks.

and the assumptions in the rest of the ecosystem have been fighting every step of the way

There is an arrogance in the way of thinking that when you see everyone breaking your arbitrary rules you think to yourself "there is no way my rules are at fault, it's everyone else's fault for breaking them."

due to the huge number of places where hardcoded relationships have been baked in.

And why are hardcoded relationships bad for developers or users of the operating system? "Because they break Nix" is not a good excuse. Plenty of other operating systems work just fine with such things hardcoded, I don't see developers complaining about these hardcoded things, and moving things around can only make things more confusing for the user.

To me it looks like Nix picked a poor design and instead of going back to the drawing board and trying to come up with a better design they have gone all in on trying to force their bad design to work.

How much work do you think iOS or Android spend on app packaging / installation per year. Despite having millions of more developers and billions of more users they spend orders of magnitude less than NixOS does.

Edit: I can't reply since I'm rate limited.

Debian already supports installing multiple php versions.

You can use the update-alternatives command to set which one is default for the php command.

Via your web server's config you can config which php version a site will use.

Thanks for the reply and explanation.

which means having to decompile all of them

This same thing applies when the game code is in C#. You may have to go through many classes to figure out how everything fits together. Decompiling all of them.