Heyyy you're the one who wrote authlogic! What a blast from the past :) Thank you for your contribution to the Rails community, and congrats on shipping Timber & Vector!
I've been in touch with Grammarly as well [1]. I work for a publishing platform with thousands of writers, editors and contributors. It was very difficult to tell people they can't use Grammarly :/ [1]…
Reminds me of MTR https://en.wikipedia.org/wiki/MTR_(software) A super useful tool for debugging why a client has trouble accessing a website.
That's actually what we did. From pilbox's docs: > It is not intended to be the primary source of images, but instead acts as a proxy which requests images and resizes them as desired. We fetched from S3 on-the-fly…
We put it behind Fastly. We could have used Cloudflare too, but we were racing against time (and angry customers!). We set the cache timeout to 1 hour, and that's pretty much it.
Ugh. Thin, low-contrast, unreadable typography.
Heyyy you're the one who wrote authlogic! What a blast from the past :) Thank you for your contribution to the Rails community, and congrats on shipping Timber & Vector!
I've been in touch with Grammarly as well [1]. I work for a publishing platform with thousands of writers, editors and contributors. It was very difficult to tell people they can't use Grammarly :/ [1]…
Reminds me of MTR https://en.wikipedia.org/wiki/MTR_(software) A super useful tool for debugging why a client has trouble accessing a website.
That's actually what we did. From pilbox's docs: > It is not intended to be the primary source of images, but instead acts as a proxy which requests images and resizes them as desired. We fetched from S3 on-the-fly…
We put it behind Fastly. We could have used Cloudflare too, but we were racing against time (and angry customers!). We set the cache timeout to 1 hour, and that's pretty much it.
Ugh. Thin, low-contrast, unreadable typography.