jotto
My NixOS and Nomad Dev Environment
My NixOS and Nomad Dev Environment
Google May Still Need Pre-Rendering or SSR
With respect to JavaScript apps (React, Angular, etc.):
It's not clear these days because the major search engines don't explicitly clarify whether they parse JavaScript apps (or if they only parse high-ranking JS apps/sites. But 10 years ago it was a must-have to be indexed.
One theory on pre-rendering is it reduces cost for the crawlers since they don't need to spend 1-3s of CPU time pre-rendering your site. And by reducing costs, it may increase chances of being indexed or higher rank.
My hunch is that long-term, pre-rendering is not necessary for getting indexed. But it is typically still necessary for URL unfurls (link previews) for various social media and chat apps.
disclosure: I operate https://headless-render-api.com
Stripe is Easy, Bitcoin is Easier
Exploiting DeFi Apps with This One Weird Trick
Exploiting DeFi Apps with This One Weird Trick
AMM Braindump
Arbitraging Uniswap and SushiSwap in Node.js
Stripe is Easy, Bitcoin is Easier
Stripe is Easy, Bitcoin is Easier
If that's true, is there a TailsOS equivalent for phones?
You don't pay for Google with cash. You pay for Google by submitting your free will.
Ask HN: What is the most ergonomic computer setup?
Ask HN: Should an ANN Be Allowed Access to Amazon Mechanical Turk API?
If you can be patient enough to cache any state you might have in a special global var that gets serialized during the "server side render", then it works for any JavaScript framework that can rehydrate/reattach to SSR'd HTML.
* March 4th assets: 4.2T
* Today: 5.8T
* Proposed: 2.3T more
so that's 3.9T since March 4th. Doubling. Not "order of magnitude"
Ask HN: Kubernetes Desktop App?
Is there a simple desktop app (Electron is fine) where I can quickly view what's running and tail the logs of active containers?
I launched it shortly after https://www.prerender.cloud, which server-side renders JavaScript SPAs, to make integration easier.
Prerender.cloud kind of sells itself, but roast.io does not. I've wondered if it appears too complex.
Ask HN: Is there a Redis alternative that uses disk?
Just need a key/val get/set.Redis stores everything in memory. It uses the disk for snapshots, but what about using the disk when there's not enough memory for storage? (memory is expensive)Postgres works except it doesn't reclaim disk space without a vacuum full (which requires a lock) so if you're doing a lot of deletes, Postgres is impractical.
Ask HN: Memory+Disk Cache?
Like a Redis that also uses disk to bring down the cost of a memory-only cache.In other words, I want a key/val lookup that keeps most recently used in memory, other stuff on disk.Postgres works except it doesn't reclaim space without a vacuum full (which requires a lock)