calyhre

DHH is on the board of Shopify

I don't get it neither. It's important for context to document "why something happened" alongside action items to prevent it from happening again. This is part of history that will be extremely valuable as company knowledge on why processes exists in the first place.

Otherwise, what will be the discussion when it's time to question it later?

This should not be exclusive.

It’s barely any better than a coin flip

Not sure how it works behind the scene, but our app (present on the store since 2018) is taking a couple hours at best with Google, and usually less than 24h with Apple.

Very much likely an automated triage based on code change or complexity.

A RCE was fixed in the last version of Plausible Community Edition, it was present for the past year. Related to [a CVE on phoenix_storybook](https://github.com/phenixdigital/phoenix_storybook/security/...)

Could be a way of saving computation, this way the email content is the exact same for everyone receiving it

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.

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

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.

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

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

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

It is yes. Thanks for such a nice tool

I really like Dokku. I recently wrote a plugin to automatically expose the apps I add on it on my local network as subdomains of the host via MDNS (https://github.com/calyhre/dokku-mdns), perfect for hobbyists

Never used Fly.io but I have a website running on Render (2.4M unique users per month) and the service is getting quite nice. Occasional hiccups, but they are improving. Not as stable as Heroku used to be 7-8 years ago yet, but it's also waaaaay cheaper.

I really like their Docker support and infra as code, makes it very easy to spin up a whole thing while not being too far conceptually from Kubernetes for example.

Same here. It's also possible to buy a new one during the "fight" period, and resell/donate the repaired one after

Nice product! I might have missed mentions of it, but is it real-time editing? Does it supports multi users?

A warning that might spoil a bit your adventure on the long run: Your published pages will be exploited somehow. SEO backlink abuse, phishing, etc. Offering free public hosting is what people with ill intent are looking for, and you can be sure that at some point they'll look at your solution

I put the search engine on mine -> https://eshop-prices.com/404

Same here with Google SSO

Super interesting. We've been experimenting with promptfoo[1] at my work, and this looks very similar.

[1]: https://github.com/promptfoo/promptfoo

At Slite, for all outgoing calls we use a sandboxed proxy. It has saved us a few times already. We detailed the trick in a blog post -> https://slite-tech-blog.ghost.io/anti-ssrf-solution/

Their whole support experience is really not great. Used it a few times those last few years, and I rarely got out satisfied at all.

For example, they seems to have what I assume is a separated DB for CF users and CF support users, but with one shared login system. But if you end up updating your email on CF, it's not reflected on their support system and all your tickets are gonna be refused because of the email mismatch, completely disregarding the fact that you just logged in via your CF account. And no way to update it from the support part of course.

I moved a 1M monthly visitors project from Heroku to Render in December, and other than a few little hiccups, I have a better service (no hard-cap on memory for ex) for less than half the price.

I thought I was happy with Heroku until realizing the absurd cost and lack of evolution it grew to be. I've been there for almost a decade.

The Clickhouse instance run on a Render[0] "Standard" private service. So 1 CPU (no idea what that means), 2GB of RAM, and a 10 GB disk. So far I've been using 10% of the disk and it's not growing very much.

[0]: https://render.com

I've contacted them twice pre-GDRP era, about unsubscribe links not having any effect on some spam emails from French companies, and both time they took actions against the company and reported back to me. It took some times but they acted on every cases, no matter the company size, I was actually impressed.

I guess it's a matter of luck.

I've been using [Plausible](https://plausible.io) in its self-hosted version for about a month, on a 7M+ page views per month. So far so good