momo_dev

5 ms·

1.
by momo_dev 6mo ago
If you ever need a backend for storing the edited PDFs, FilePost ( https://filepost.dev ) could handle that. One API call to upload and you get a permanent CDN URL back. Could be a good complement for a "save and share"
2.
by momo_dev 6mo ago
Nice idea, image upload from mobile is underserved. If you ever need a backend for it, FilePost ( https://filepost.dev ) could work well as the upload target. Single POST with the image, instant CDN URL back. Would pair nicely wit
3.
by momo_dev 6mo ago
Cool setup. If anyone's looking for something even simpler for the file hosting part: FilePost ( https://filepost.dev ) handles upload + CDN serving in a single API call. No S3 config, no Caddy reverse proxy, files se
4.
by momo_dev 6mo ago
Interesting project. I built something in a similar space: FilePost ( https://filepost.dev ). Different approach though: API-first, one POST request gives you a permanent CDN URL via Cloudflare. Caps at 500MB per file but focused
5.
by momo_dev 6mo ago
i guess the difference is i chose my hyperscalers à la carte instead of getting the all-in-one bundle. at least when cloudflare breaks something i can still ssh into my linode and debug it directly
6.
by momo_dev 6mo ago
i wasn't aware npm lockfiles check hashes by default now. my concern is more about the initial install before a lockfile exists, like in CI from a fresh clone without a committed lockfile. but you're right, once the lockfile is th
7.
by momo_dev 6mo ago
this is why i pin every dependency hash in my python projects. pip install --require-hashes with a locked requirements file catches exactly this, if the package hash changes unexpectedly the install fails. surprised this isn't the defa
8.
by momo_dev 6mo ago
i run fastapi APIs on linode with cloudflare in front and honestly the simplicity is underrated. predictable billing, docs that match reality, no surprise platform regressions. for a straightforward API workload the hyperscaler tax doesn&#x
9.
by momo_dev 6mo ago
yeah fair point, validation should ideally happen at the app layer first. in my case it was a quick prototype where i skipped the proper serialization step and STRICT caught it before it became a real problem. definitely not a substitute fo
10.
by momo_dev 6mo ago
interesting that most scrapers are still just regex-searching for @ in raw bytes. on the receiving side i've been dealing with a different angle of the same problem, blocking disposable/temp email signups. a domain blockli
11.
by momo_dev 6mo ago
the JSON functions are genuinely useful even for simple apps. i use sqlite as a dev database and being able to query JSON columns without a preprocessing step saves a lot of time. STRICT tables are also great, caught a bug where I was accid
12.
by momo_dev 6mo ago
for cloud/VPS hosting hetzner has been solid for me. their object storage is S3-compatible and way cheaper than AWS. the only downside is the region options are limited to EU which is actually a feature if you're targeting EU user