Not very exciting. GET is pretty close, and many proxies will happily send the body upstream… not GCP load balancers though. So you can’t totally rely on that. It seems like if you actually need this you could use a header to change POST behavior at the cache layer.
Using both works well. Have GPT generate a class, module, component etc. Then tweak/polish it in editor with co-pilot assist (it has more context about the project). I used this last week and it saved me quite a bit of boilerplate work. The tools will continue to get better.
I’m about a quarter into the The Dark Forest. So far so good. @nonlinear sold me on the series.
It will reject on receive. An explicit and meaningful message makes sense though.
For example, imagine receive was implemented and sending eth to the contract would contribute eth if the fund was open, or allocate yield if the fund was successful. Now imagine a proposal passing after it hit max goal, and the transaction occurs. The funds would be allocated to the contributes pro-rata.
Because tokens can be contributed, and returned to contributors, we used explicit calls for them as to disambiguate a defined receive function.
Luckily, things move fast. Unfortunately, things move fast. I feel this way about node in general, having used stacks with Java where really old shit still works.
I started migrating this afternoon. I hit a few snags, but was able to get it built in an hour or so. Most of my changes were around how I was reading contracts with ethers, and the strict types ‘${number}’ , ‘0x{string}’ and the type changes for Provider and Signer. Not done, but not frustrated.
You can use your own modem in the US. At least with every ISP I have used.
I went with enterprise equipment, but the cheap version: Ubiquiti router, POE switch, UniFi APs ceiling mounted (POE), UniFi security cameras, and hardwire to some places.
Set you max gas fee to 60 before sending the transaction and it will mine at some point tonight. I did that yesterday and it took 4 hours.
Coffee in the morning and drawing or building legos with my daughter before bed.
At some point the compute power of a laptop will be marginally better than phones for most creator use cases. It’s there now for consumer use cases. You will dock the phone to your keyboard, mouse, large monitor or headset, and do your work. So… yes, I think so.
It's a networking / caching issue. Clients fetch metadata for an NFT over the network, and often cache the information to keep load times low. If the metadata changes, or isn't accessible, the client may render something else.
We fixed the underlying problem, but we can’t invalidate cache on third party systems. I see the correct image here now.
If the campaign goal is not reached within the allotted time, contributors can withdraw their contribution.