But then you end up potentially exposing the origin server. This could be an opt-in option though

I don’t know a lot about the rest of Europe on this, but here in France it’s been more than a decade SMS are unlimited in mobile plans, and these plans are quite cheap.

We also have free roaming in the whole Europe.

Whatsapp came out 16 years ago. Yes, the main driver for adoption was avoiding fees. They still emphasize it being free to this day.

The adoption of messaging apps caused a lot of carriers to reduce or eliminate the SMS fees, as they saw the business was evaporating.

Carriers actually massively jacked up SMS fees, just not for consumers.

One of Signal's main cost centers is activation SMS messages. For many other small players it is a significant factor too.

Yarn just landed a similar feature too https://github.com/yarnpkg/berry/pull/6901

And it supports excluding single versions! Looks like yarn is back on the menu.

I have the same issue and it's driving me crazy. One bluetooth device is waking up a MBP M4 regularly during the night, lighting up an external screen. Even without any connected devices.

Conversely, I have a joystick that prevents my Windows desktop from sleeping; thankfully it won't wake it up if I manually sleep it.

Badly behaving peripherals suck.

Hey, I worked on this. Feel free to shoot any questions if you like

It seems that writing a tool in anything else than English will bypass most of this scanner

We also migrated away from Next.js last year to [Vike], big improvment on developer experience all around. Most of our needs are covered by just pre-rendering pages ([SSG])

[Vike]: https://vike.dev/ [SSG]: https://vike.dev/pre-rendering

Could you describe a bit the load and the server/db specs? I’m using Plaisible right now and I wonder how it would handle with similar specs

We had separate database and app instances, the DB instance had 32 cores and 64GB memory, which we doubled to keep up with our requirements. We have tens of millions of visits daily, and our database was close to ~300GB within the first few months.

For plausible I believe that since it runs on Postgres, scaling should not be a problem as long as you scale the resources with it.

It's fixed in the developer edition 132.0b5 also if you are wondering

I was indeed wondering. Thank you.

It's actually a pill to eat less, seems to be a hunger suppressant