Twitter most likely hasn't been able to retain the "right" people.

Only people that don't want to get deported during a tech hiring slowdown

This is true.

It's interesting that you mention multivitamins. When I was burnt out I noticed that Vitamin B, D3 and zinc have a huge positive effect on my mood and energy level.

One major acquisition that is missing from your list was the aquisition of Postbank in 2018.

IMHO Twitter wants to make sure content does not easily leave their platform, thus the stricter rate limits on reading.

At the moment, there seems to be no way back. The page to convert an individual user account to an organization account (at https://hub.docker.com/settings/convert) explicitly states:

> To use organization features, convert your account from a User to an Organization.

> You can't undo this action.

Delete and recreate the account?

Does Docker reserve the namespace of deleted accounts/orgs?

EDIT: I seem to have answered my own question... https://forums.docker.com/t/how-can-i-delete-old-previous-ac...

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!

After a brief glimpse at the documentation, I am missing a feature comparable to Kafka's partitioning. Well, the protocol [1] briefly mentions it, but it does not seem to be exposed.

Getting insights into the roadmap for this would certainly be interesting...

[1]: https://github.com/rabbitmq/rabbitmq-server/blob/v3.9.x/deps...

Genuine question: what is it that you need from Kafka partitioning?

Not OP, but what I need from Kafka partitioning is guaranteed message ordering (per partition key).

I don't know about RabbitMQ, but with Apache AMQ there is message grouping, which is kind of similar, but not quite the same. With Kafka it's unavoidable, which is good.

Guaranteed ordering per partition while keeping the ability to scale across partitions.

Care to elaborate?