patatahooligan @ patatahooligan @lemmy.world

Posts

1

Comments

223

Joined

2 yr. ago

This makes no sense. There might be various reasons a person might want/need to be on facebook. Does that mean they waive all right to privacy in every aspect of their life forever?

What did he do? I'm out of the loop.

No, there's no way to automatically make something become law. A successful petition just forces the European Commission to discuss it and potentially propose legislation. Even though it's not forcing anything to happen, there is an incentive for the commission to seriously consider it as there is probably a political cost to officially denying a motion that has proven that it concerns a large amount of people.

Sign the petition even if it's surpassed 1mil signatures by the time you read this! The signatures will be verified after the petition is complete. This could lead to removal of any number of them. We don't want to barely make it. Let's go as high as possible!

That's just like your opinion man.

Yeah for sure there's ton of clickbait, but this isn't "a minor technical matter". The news here isn't the clash over whether the patch should be accepted in the RC branch, but the fact that Linus said he wants to remove bcachefs from the kernel tree.

"Fair use" is the exact opposite of what you're saying here. It says that you don't need to ask for any permission. The judge ruled that obtaining illegitimate copies was unlawful but use without the creators consent is perfectly fine.

Of course they're not "three laws safe". They're black boxes that spit out text. We don't have enough understanding and control over how they work to force them to comply with the three laws of robotics, and the LLMs themselves do not have the reasoning capability or the consistency to enforce them even if we prompt them to.

I'm sure many people don't even think about that. Having to reinstall all your packages from scratch is not something they do frequently.

And for the people who are looking to optimize the initial setup, there are many ways to do it without a declarative package manager. You can:

• Write a script for your initial setup that includes installing packages
• Use a tool like ansible
• Use meta-packages
• Export your currently installed packages to a file and pass that to the package manager on the new installation

Many times these keys are obtained illegitimately and they end up being refunded. In other cases the key is bought from another region so the devs do get some money, but far less than they would from a regular purchase.

I'm not sure exactly how the illegitimate keys are obtained, though. Maybe in trying to not pay the publisher you end up rewarding someone who steals peoples' credit cards or something.

They work the exact same way we do.

Two things being difficult to understand does not mean that they are the exact same.

NVMEs are claiming sequential write speeds of several GBps (capital B as in byte). The article talks about 10Gbps (lowercase b as in bits), so 1.25GBps. Even with raw storage writes the NVME might not be the bottleneck in this scenario.

And then there's the fact that disk writes are buffered in RAM. These motherboards are not available yet so we're talking about future PC builds. It is safe to say that many of them will be used in systems with 32GB RAM. If you're idling/doing light activity while waiting for a download to finish you'll have most of your RAM free and you would be able to get 25-30GB before storage speed becomes a factor.

So the SSD is hiding extra, inaccessible, cells. How does blkdiscard help? Either the blocks are accessible, or they aren't. How are you getting a the hidden cells with blkdiscard?

The idea is that blkdiscard will tell the SSD's own controller to zero out everything. The controller can actually access all blocks regardless of what it exposes to your OS. But will it do it? Who knows?

I feel that, unless you know the SDD supports secure trim, or you always use -z, dd is safer, since blkdiscard can give you a false sense of security, and TRIM adds no assurances about wiping those hidden cells.

After reading all of this I would just do both... Each method fails in different ways so their sum might be better than either in isolation.

But the actual solution is to always encrypt all of your storage. Then you don't have to worry about this mess.

I don't see how attempting to over-write would help. The additional blocks are not addressable on the OS side. dd will exit because it reached the end of the visible device space but blocks will remain untouched internally.

The Arch wiki says blkdiscard -z is equivalent to running dd if=/dev/zero.

Where does it say that? Here it seems to support the opposite. The linked paper says that two passes worked "in most cases", but the results are unreliable. On one drive they found 1GB of data to have survived 20 passes.

in this case, wiping an entire disk by dumping /dev/random must clean the SSD of all other data.

Your conclusion is incorrect because you made the assumption that the SSD has exactly the advertised storage or infinite storage. What if it's over-provisioned by a small margin, though?

From the article:

Those joining from unsupported platforms will be automatically placed in audio-only mode to protect shared content.

and

"This feature will be available on Teams desktop applications (both Windows and Mac) and Teams mobile applications (both iOS and Android)."

So this is actually worse than just blocking screen capturing. This will break video calls for some setups for no reason at all since all it takes to break this is a phone camera - one of the most common things in the world.

He didn’t say anything about Nazism being an opinion you disagree with.

This is literally the only point the article makes and there's no point even discussing it further if you're too blind or dishonest to admit that.

You don't have to trust Drew, though. Vaxry is pretty clear on his stance on the subject.

if I run a discord server around cultivating tomatoes, I should not exclude people based on their political beliefs, unless they use my discord server to spread those views.

which means even if they are literally adolf hitler, I shouldn't care, as long as they don't post about gassing people on my server

that is inclusivity

Source: https://blog.vaxry.net/articles/2023-inclusiveActivists

Note how this article is not where he first stated the above. This article is where he doubles down on the above statement in the face of criticism. In the rest of the article he presents nazism as an opinion people might have that you disagree with. He argues that his silent acceptance of nazis is the morally correct stance while inclusive communities are toxic actually.

This means that it's not just Drew or the FDO who are arguing that Vaxry's complete lack of political stance is creating safe spaces for fascists. It's Vaxry himself that explicitly states this is happening and that it's intentional on his part.

C is pretty much the standard for FFI, you can use C libraries with Rust and Redox even has their own C standard library implementation.

Right, but I'm talking specifically about a kernel which supports building parts of it in C. Rust as a language supports this but you also have to set up all your processes (building, testing, doc generation) to work with a mixed code base. To be clear, I don't image that this part is that hard. When I called this a "more ambitious" approach, I was mostly referring to the effort of maintaining forks of linux drivers and API compatibility.

Linux does not have a stable kernel API as far as I know, only userspace API & ABI compatibility is guaranteed.

Ugh, I forgot about that. I wonder how much effort it would be to keep up with the linux API changes. I guess it depends on how many linux drivers you would use, since you don't need 100% API compatibility. You only need whatever is used by the drivers you care about.

Does it have to be Linux?

In order to be a viable general use OS, probably yes. It would be an enormous amount of effort to reach a decent range of hardware compatibility without reusing the work that has already been done. Maybe someone will try something more ambitious, like writing a rust kernel with C interoperability and a linux-like API so we can at least port linux drivers to it as a "temporary" solution.