davad

Shocked Pikachu face.

Shocked Pikachu face.

This.

It definitely is possible, but if you have to ask, you probably don't have the background to do it.

If you want to do it anyways, great! You'll be learning some new skills. I suggest taking it slow. Use a bunch of dummy boards to practice on. When you're ready to try for real, try it on a machine you don't care about first. Something cheap enough that you don't care if you mess it up.

I don't know how dead it is, but it's pretty straightforward to set up your own gateway (public or private). Even if you don't have a tech background, there's the "IPFS Desktop" app that stands up the IPFS service locally.

Do you mind telling roughly how much it cost?

This only works if there is enough supply from those other companies. This also assumes that the other companies have a supply chain that isn't affected by tariffs. Which means each step on the chain needs to produce enough to be a reasonable alternative to tariffed imports.

Get a second opinion. You could probably get a single implant to replace the broken molar.

The only one I think is reasonable is GraphQL. But that isn't rest, and HTTP is just one of the transport layers it supports.

For anything claiming to be RESTful, it's a crime.

The article is talking about art in promo material.

Think about it: whenever you see a piece of production art featured in a social media post or a press release or a game announcement at a big televised showcase, all you ever see is the art. You never know who made it, whether it was created by an individual or a small team (or even a studio).

Two different concepts.

You're talking about work slowing because of increased overhead from more people needing to communicate and make decisions.

The OP is talking about the"bus factor". How many people can leave the project unexpectedly and still have the project survive. E.g. if only one person has access to merge changes, the bus factor is 1 regardless of how many people actively contribute.

(another pet peeve of mine is "rest" APIs that use 200 response codes for everything)

Yup, also some APIs use GET for everything. It's a pain. And it means that filtering by verb only helps if you're intimately familiar with the API. And even then, only if you keep up with changes as they happen. So really, only if you're developing the API yourself.