> In Lua it's only the start/end of the string

There's an additional caveat: if you use the optional "init" parameter to specify an offset into the string to start matching, the ^ anchor will match at that offset, which may or may not be what you expect.

That is a good point, and something I've actually (personally) used quite a bit when writing parsers

> which may or may not be what you expect

I find it hard to imagine any other expectation passing the rubber duck test.

"Oh, so you expected the match to always fail, no matter what the string was?"

Well, it's not a completely outlandish scenario that the value of `init` might come from a variable that is sometimes at the start of the string and sometimes not, and a newcomer might expect `^` to only match when it is.

Don't get me wrong, it's certainly far more useful as it is, I'm glad it works this way.

Although those functions operate on "binary strings", not Uint8Arrays, and there is no especially clean way that vanilla JS exposes to convert between the two that I am aware of.

SBF's announcement of Chapter 11 proceedings today explicitly includes FTX US:

https://twitter.com/SBF_FTX/status/1591089317300293636

If only I had a FTX US account. I'd get one more day of GTFO...

From their own benchmarks it seems more like bzip3 is geared towards a different compression/speed trade-off than bzip2, rather than an unambiguous all-around improvement. Am I misreading it?

That's what I took out of it too. Sacrificed a bit of speed and a lot of memory for a smaller output size.

edit: ah, bzip3 is parallelizable, while bzip2 isn't. That alone is enough for me to be able to claim 'faster'.

bzip2 can exploit concurrency through pbzip2, can't it?

It is kind of a hack for decompression, where you look forward in the stream for a block signature, and try decompressing from there.

In practice it works, but it isn't pretty ;)

see also: lbzip2

(context: I have had a situation where files created by pbzip2 on linux were not able to be decompressed with some library on .NET, but using lbzip2, they were. I never looked into the details.)

Can't agree more, lbzip2 is the go-to tool for dealing with bzip2 compression and decompression, it's a whole lot of faster than bzip2 which is single-threaded!

Went to http://www.sonnyjs.org/ (latest Chrome, Windows 7) - there doesn't seem to be any way to scroll the left-hand menu (it cuts off at "StorageManager" sub-heading for me at default zoom level, I can see there are more by zooming out though) and of the ones I can see, the menu items "render" and "kill" don't seem to do anything.

The extracted quote at the top of the Forbes article here seems to indicate he was thinking along those lines: http://www.forbes.com/sites/sarahjeong/2015/01/22/the-dread-...

"I imagine that someday I may have a story written about my life, and it would be good to have a detailed account of it."

But if you'd like to search Verbatim and also restrict your results to the most recent month/year/etc., even though these are separate dropdowns under Search Tools, you're out of luck. Google seemingly just won't allow this.

My mistake, I misread.

As Jason Scott (@textfiles) notes on Twitter, this will be something of a first: with all the old content coming back, Archive Team/archive.org "literally provided a backup of a site while it swapped owners."