dinkelberg

Fair point. But probably not going to happen...

If you want to keep XSLT in browsers alive, you should develop an XSLT processor in Rust and either integrate it into Blink, Webkit, Gecko directly, or provide a compatible API to what they use now (libxslt for Blink/Webkit, apparently; Firefox seems to have its own processor).

I have used it a year ago with macOS 14 or 15 and it worked. I've had problems copying too many files at once (don't remember the problem exactly), that's why I only copy about 100 at a time.

Your mileage may vary.

Counter question: How do you know it works?

A file manager better be rock solid, I don't want a bug to delete any files or do other shenanigans.

For those who want to use Google's Android File Transfer app for Mac, which for some reason isn't regularly available from Google anymore, it's still available by direct download: https://dl.google.com/dl/androidjumper/mtp/current/AndroidFi...

Chroma subsampling was developed for TV, long before JPEG.

Are you speaking of chroma subsampling, or is there a property of the discrete cosine transform that makes it more effective on luma rather than chroma?

Sorry for confusing you!

Would you tolerate using DANE?

TFA itself has an incorrect DOCTYPE. It’s missing the whitespace between "DOCTYPE" and "html". Also, all spaces between HTML attributes where removed, although the HTML spec says: "If an attribute using the double-quoted attribute syntax is to be followed by another attribute, then there must be ASCII whitespace separating the two." (https://html.spec.whatwg.org/multipage/syntax.html#attribute...) I guess the browser gets it anyway. This was probably automatically done by an HTML minifier. Actually the minifier could have generated less bytes by using the unquoted attribute value syntax (`lang=en-us id=top` rather than `lang="en-us"id="top"`).

Edit: In the `minify-html` Rust crate you can specify "enable_possibly_noncompliant", which leads to such things. They are exploiting the fact that HTML parsers have to accept this per the (parsing) spec even though it's not valid HTML according to the (authoring) spec.

Epiphany (GP had a typo) and Three Kings is the same occasion, in fact. Wikipedia: https://en.wikipedia.org/wiki/Epiphany_(holiday)

A huge pet peeve of mine is people getting annoyed by phrases like "I mean." :)

How did you measure this? Do you know that /dev/null is the limiting factor, or could it be the data source that is limiting?

And those are some very low hanging fruit. If you look at the bigger picture, Apple does not know how to balance ease of use on the one hand and control over details by power users/geeks on the other hand. They simply do not let you configure things, because coming up with good UI for that is hard. But on macOS, power users probably make up a large share of their users. They should figure this out.

I do not think that GP's comment was meant that way. GP simply wanted to clear up a misunderstanding that was apparently created by the renaming of this thread to "Greg Newby, CEO of Project Gutenberg, has died", which has been undone since. I am sure GP did not mean to detract from Greg Newby's contributions to the project.

I'm sorry, but this reads somewhat misanthropical itself. Let people have some fun?

This article has a bad name. It is about very reliably detecting individuals near WiFi networks, regardless of whether they carry a device with them, by decoding unencrypted WiFi signals. The title makes it sound like generic "beware of Internet surveillance" stuff.

I would recommend reading the post that Hillel is responding to instead, namely Luke Plant's "Breaking 'provably correct' Leftpad" (https://lukeplant.me.uk/blog/posts/breaking-provably-correct...).

Rest in peace, Professor Lehrer.

Your witty lyrics combined with virtuoso piano play have not yet been surpassed, to my or your knowledge, which you might have found sad; it might alternatively be seen as testament to talents that may appear less than once in 100 years.

Your departure saddens me greatly.

The certificate for blog.torproject.org should not be self-signed. For me it is an extended validation certificate issued by DigiCert Inc.

Why should it not allow for your spiralling brushstroke? You can divide the spiral into the strokes corresponding to each turn around the center. We can assume that each of these strokes is measurable (otherwise we would not need the construction of the spiral). Then the entire spiral is just a countable union of those measurable strokes, thus it is measurable itself.

More prior art: the Light Table IDE https://chris-granger.com/2012/04/12/light-table-a-new-ide-c... (I haven't used it.)

The imagery on the frontpage seems to be taken from Uniqlo advertisement material from 2020. There seem to exist no terms of service. The site doesn't look legit to me.

Edit: A source: https://manofmany.com/fashion/mens-fashion-trends/uniqlo-u-2...

Out of curiosity, which companies other than Jane Street would you consider "Better-than-FAANG"? I am asking because I am interested in internships, too, as I am currently an undergrad (in math).

The concept of the antilibrary might help me make sense of my book collection. I stopped buying books because I usually don't read them in the end. However sometimes there are rare moments where it is nice to be able to fetch a specific book from the shelf.

No, I don't know how they communicate exactly. However, I imagine between the processor and flash memory proper there sits a flash memory controller (provided by the flash memory manufacturer) that speaks some protocol akin to ATA. That way manufacturers would be able to replace flash memory A by flash memory B with relative ease, because the abstraction of the protocol allows them to ignore how that specific flash memory is implemented exactly.

Is that wrong? Does the OS on smartphones generally have direct access to the flash memory proper?

Edit: I remembered another protocol that I would guess is used in smartphones for communication with the flash memory, namely UFS (which is also utilized with SD cards).

Edit 2: Note that it is irrelevant whether the protocol used is ATA, UFS, or something different.

> A USB based method for resetting a device would be perfectly acceptable to use before sending in a device for repair.

I think that is true, but with one caveat, you should test if the resetting actually worked.

I once had an Android phone with "full encryption" enabled that, after resetting, still had all the user data on it. It was obviously not only not reset, it wasn't even encrypted in the first place.

I am sure a lot of mobile phones have problems like that, because I think that smartphone manufacturers don't care about quality too much, as long the issues are not immediately apparent to an average user.

But if you can't recover the data afterwards yourself, I would agree that you can normally send it to recycling or repair.

Thank you. My comments might sound very strict and total. But of course everyone has different threats that they care about, and repair shops are probably not too sophisticated.

"Our results lead to three conclusions: First, built-in commands are effective, but manufacturers sometimes implement them incorrectly. [...]

We tested ATA commands for sanitizing an entire SSD, [...]. We find that while most implementations of the ATA commands are correct, others contain serious bugs that can, in some cases, result in all the data remaining intact on the drive."

M. Wei, L.M. Grupp, F.E. Spada, S. Swanson: "Reliably Erasing Data From Flash-Based Solid State Drives." <https://www.usenix.org/legacy/events/fast11/tech/full_papers...>

I guess it is true that you can erase an entire flash device in a split second.

But that doesn't help you if the erase command was not implemented correctly.

And I am sure that you cannot implement an erase command from within the operating system. It has to be implemented in the flash memory controller. So if your hardware manufacturer got it wrong, you can't fix it.

It might not be possible to wipe the data off the flash memory, due to how flash memory works. As you can only reset bits on the flash memory some amount of times, flash memory controllers try to avoid resetting bits and they try to distribute resets evenly on the memory (called wear leveling), so that it doesn't happen that parts of the memory are already worn out while other parts are healthy. So "deleting" and even "zeroing" flash memory might not do what you would expect. Instead of resetting the bits of the original content, it might put the zeros somewhere completely different.

And wipe commands that one can send to flash memory chips are sometimes broken too (they might be implemented as no-ops).

Edit: Also, even if you tell it to write zeros everywhere, it might not delete the content, because there is hidden extra memory on flash memory chips.