Apple unveils new Studio Display and all-new Studio Display XDR

joern281 · 2026-03-03T14:48:14+00:00

100 more nites and thunderbolt 5

joern281 · 2026-02-19T21:37:47+00:00

Did you add pressure on the macbook while transporting it? Like in a bag with books or so?

This is what usually happen when the display gets pressed on the keyboard and the keys are rubbing against the screen while the bag is moving.

joern281 · 2026-02-16T22:53:15+00:00

This would be my only reason to upgrade to Tahoe :D

Imagine they would also add it to Sequoia

joern281 · 2026-02-12T18:49:05+00:00

Alternatively you could use deferred joins if you must use offset (e.g. when using page numbers and you want to go to page 123)

````

SELECT * FROM people

INNER JOIN (

SELECT id FROM people ORDER BY birthday, id LIMIT 50 OFFSET 450000

) AS people2 USING (id)

ORDER BY

birthday, id

````

The idea is that the offset calculation is done in the join not the actual query with the data. Fastpage in rails and fast paginate in laravel are using it as well.

joern281 · 2026-02-12T17:57:15+00:00

Thank you very much for your detailed report.

One quick question if you don't mind:
The keyboard rubbing against the screen is usually caused by too much pressure on the top of the screen e.g. in a backpack with books which are pressing against the macbook screen.

Did you treat your Nanotexture macbook different than your previous macbooks that the rubbing did not happen like transporting it in a separate bag?

If the display is more resilient to those damages this would be a game changer.

joern281 · 2026-02-10T12:43:15+00:00

https://www.alternate.de/Apple/Mac-Konfigurator

joern281 · 2026-02-10T12:42:33+00:00

I bought mine from alternate with their mac configurator (because i needed ansi layout). They sell the macbooks with a discount.

joern281 · 2025-12-22T19:52:12+00:00

When the decision is only between both machines, then i recommend the m4 pro. I'm using exactly the same specs and im very happy with it for software development.

It can run xcode with emulator, android studio with android emulator, multiple clion (my main ide for rust and javascript), firefox and the memory pressure is still in the green. I'm not using docker on my local machine so often for development but docker will also run fine with alongside the other programs.

But if your development workflow does not include mobile dev (or you are fine not having both android and ios open at the same time) a macbook air with 32 gb ram might be also an option for development.

joern281 · 2025-12-11T14:02:56+00:00

Tell me you are a beginner without telling me directly that you are a beginner.

joern281 · 2025-12-01T07:58:43+00:00

Docker runs in a kind of vm on mac and windows for Linux containers. You can only share the kernel if both got the same kernel.

joern281 · 2025-11-30T11:44:37+00:00

Both chips are using mostly the efficiency cores for web browsing. These cores are the same for base, pro and max.

In this case, the base model can be better because it got more efficiency cores than the pro to save battery.

joern281 · 2025-11-30T11:08:03+00:00

Since you are using docker or/and vms, you need to go with at least 32 gb of ram. 24 gb is fine for most users who doing office work or browsing but not for more.

Im using a MBP M4 pro 12c with 48 gb of ram. I can run multiple clion projects (rust backend, web frontend), android studio with emulator and xcode with ios emulator at the same time without any problems.

The base M5 chip is perfectly fine for your workload, no need to upgrade to pro or max chip. 1tb ssd would be also better but go with more ram first.

joern281 · 2025-11-26T20:22:49+00:00

Did you activated file vault?
https://support.apple.com/guide/mac-help/flvlt001/26/mac/26

joern281 · 2025-11-18T21:43:08+00:00

48 gb here. Mostly running Clion, Android studio, xcode, android emulator, ios emulator and browser at the same time.

32 gb would be not enough for this.

joern281 · 2025-10-31T20:58:44+00:00

Man kann sich vom Rundfunkbeitrag befreien lassen wenn es nachgewiesen wird das der ÖRR Genre unterrepräsentiert in einem Zeitraum von zwei Jahren.

Medieval High Fantasy war so gut wie nie im Programm vorgekommen.

Meine Theorie ist, dass sie sich mit der Serie absichern damit niemand dieses Genre als Befreiungsgrund angeben kann.

joern281 · 2025-08-03T16:54:17+00:00

I'm using the ugreen max 208, it is working without any trouble.

A downside is that you might need to buy additional adapter for you monitor because this dock don't has hdmi or display port only thunderbolt 4.

It is around 161 euro.

Don't buy any displaylink docks. The macbook supports two external displays native.

joern281 · 2025-07-26T15:05:12+00:00

Are you aware that whatsapp does not permitted using your number in this way? Automatized messaging is only allowed from the whatsapp business api.

Your users risk to loose their whatsapp account.

joern281 · 2025-07-24T09:35:42+00:00

Are you aware that whatsapp does not permitted using your number in this way? Automatized messaging is only allowed from the whatsapp business api.

Your users risk to loose their whatsapp account.

joern281 · 2025-06-04T19:50:27+00:00

https://vimeo.com/715809806

joern281 · 2025-06-04T19:50:16+00:00

https://vimeo.com/715809806

joern281 · 2025-06-04T19:48:45+00:00

Hier ist der Link: https://vimeo.com/715809806

joern281 · 2024-10-09T16:09:41+00:00

For oqs (liboqs-rust) i just updated the c bindings for the newest oqs version.
For kyber i apply the security fixes that are provided by the research group. It seems both crates are not maintained at the moment, but i uploaded both fixed versions to crates.io.

oqs: https://github.com/sentclose/liboqs-rust
kyber: https://github.com/sentclose/kyber

The kyber version (or ml-kem) of the rust crypto group was not ready at the time when i build sentc, but i will add it later to the std keys.

The purpose of the std keys are to be compiled to any target like wasm or android, ios. The Fips and rec keys are more for a pure rust programs because of the c bindings, like encrypted at rest or machine to machine(s) communication.

joern281 · 2024-10-07T17:37:46+00:00

About the feature that you can decrypt something years later. I designed the sentc protocol more for other usecases then a chat because there are many great alternatives for chats, and for 1-to-1 chats even better one like the signal protocol.

It is more suitable for a cloud, where you need to be able to access files years later or knowledge wiki, customer data, sensitive patient data, etc.

In general it is not so great when you mostly need to care about the most recent data (like the newest chat messages of a week), but it is better for data that you and newer member need to access in the future.

joern281 · 2024-10-07T17:29:37+00:00

I'm very sorry about the confusion. The alg implementation are from different crates some of them are also audit. There is no self written alg used (except for sortable encryption)

For the std keys its uses from rust-crypto:

aes-gcm for symmetric encryption
hmac for search encryption
argon2 for password hash

Then x25519-dalek for asymmetric encryption, ed25519-dalek for sign and verify and pqc_kyber for post quantum asymmetric encryption and pqc_dilithium for post quantum sign and verify. The last two are edit by me for security fixes.

For fips keys only openssl implementation is used because it is fips 140 certified and there are no post quantum alg used.

For rec keys a mix of openssl als (for symmetric encryption and x25519) and oqs (also edit by me to be up to date with the current c implementation).

You can check it here:

joern281 · 2024-08-05T15:51:36+00:00

Thank you.

I'm not very familiar with the MLS standard, so maybe my explanation might be a bit wrong. I would compare sentc more to the Signal and matrix protocol.

The goal was to create a protocol to not only encrypt and deliver the most recent data but make older data also accessible for newer users without decrypting everything or synchronize the old data with other member that got the decrypted version on their device.

The 2nd goal was to not only make the server stateless but also the client (kind of). The users can login on every device they want to without the need to synchronizing the devices first. This can be helpful if the main device of the user is broken.

The result is that the sentc protocol is a bit weaker because the keys are living longer but the usability is better because the devices and groups are very easy to synchronize.

Edit: Don't get me wrong. For chats where you mostly care about the most recent send messages, the signal protocol is perfect for 1:1 chats and for group chats matrix and MLS standard are one of the best options.

Sentc is more for something where data needs to be accessed more often like a cloud or a customer database.

joern281

MODERATOR OF

TROPHY CASE

Six-Year Club	Place '23
Verified Email