

I could not work out why my Sony headphones were giving me a ding sound and then my listening was interrupted with ambient noises. I assumed Bluetooth connection requests at first, but for me it was the “speak to chat” feature that can be disabled.


I could not work out why my Sony headphones were giving me a ding sound and then my listening was interrupted with ambient noises. I assumed Bluetooth connection requests at first, but for me it was the “speak to chat” feature that can be disabled.


I picked zoho.com free tier, with an eu.org domain after scanning through a set of different options. No marketing appended to emails and only throttles on excessive sending instead of hard limits. Each service sends from its own address.
purelymail.com was my backup paid option if the free plans were no good, with the advanced pricing and low usage the cost would be miniscule.


You just solve it as per the blog post, because it’s trivial to solve, as your browser is literally doing so in a slow language on a potentially slow CPU. It’s only solving 5 digits of the hash by default.
If a phone running JavaScript in the browser has to be able to solve it you can’t just crank up the complexity. Real humans will only wait tens of seconds, if that, before giving up.


It will obviously depend heavily on the type of bot crawling, but that is not hard coordination for harvesting data for LLM’s, as they will already have strategies to prevent nodes all crawling the same thing - a simple valkey cache can store a solved JWT.


The author demonstrated that the challenge can be solved in 17ms however, and that is only necessary once every 7 days per site. They need less than a second of compute time, per site, to be able to send unlimited requests 365 days a year.
The deterrent might work temporarily until the challenge pattern is recognised, but there’s no actual protection here, just obscurity. The downside is real however for the user on an old phone that must wait 30 seconds, or like the blogger, a user of a text browser not running JavaScript. The very need to support an old phone is what defeats this approach based on compute power, as it’s always a trivial amount for the data center.
You might consider something like the friendly elec CM3588 for a DIY option with openmediavault or freenas. I have a big old box currently with spinning metal, but am looking at this as an option now that there are some larger m.2 drives available.
There’s only so much that can be done on the hardware/ firmware side, but his for me is the real gap that Linux can improve upon. Hibernate, disk encryption and secure boot/tpm unlock together have just worked for a long time on Mac and Windows.
The kernel decisions seem hostile and hard code a big assumption that it’s always unsecure to restore from hibernate automatically. What’s more insecure is having to disable disk encryption entirely. Secure boot is often misunderstood, but for all its flaws it is better than nothing, and your average user does not want to manually enter a decryption key on top of their user login all the time.
Because of this I feel a lot of software is not written and tested with hibernate in mind, so you also roll the dice on what works and what doesn’t when restoring today.
Sleep for 1 hour and then auto hibernate after, in a working setup, meant this problem was solved - always enough battery to resume doing work, no user decision required, quick wake up if resuming a recent session.
I’d love to see multi-user switch selectively suspending user processes and writing them to disk, so you can quickly restore state between users, and if one user left a browser or game running it’s not draining the battery on what are now known background tasks. No OS does this one well today.