reynaldi
Nano Banana 2 Lite Review
Testing Claude Sonnet 5's agentic claims
Testing Grok Imagine's 15-20x Faster Image Generation
Show HN: Same-Same, But Different – AI Image Matching Game
Then I have the same question with the article, why do we need this standard? If it's just to let the LLM know to call the tool in JSON format
Polar raises $10M in Seed Round
Cloudflare CEO: Football Piracy Blocks Will Claim Lives; "I Pray No One Dies"
Show HN: HyperExpress
IPv6 Support in Public Docker Registries
How to Build an Anycast Network
As someone who don't know anything about SOC2, but still aware that if I want to signal 'data privacy' that I need to get it: I don't know what I'm supposed to do on your site.
Some sort of onboarding can help, like what are my steps from knowing nothing to actually getting the SOC2. Maybe some educational contents or resources can also help.
Windsurf I think has more features, but I find it slower compared to others.
Cursor is pretty fast, and I like how it automatically suggests completion even when moving my cursor to a line of code. (Unlike others where you need to 'trigger' it by typing a text first)
Honorable mention: Supermaven. It was the first and fastest AI autocomplete I used. But it's no longer updated since they were acquired by Cursor.
Show HN: Tron-Like Map in JavaScript
After working on it for a while, I noticed there’s a stigma around using CORS proxies, often associated with fetching undocumented APIs.
While that’s sometimes true, I’m hoping to change that perception, to show that they can also be used for accessing real APIs. It just requires the proxy to correctly handle credentials and secrets.
The idea is to open up more possibilities for building static-first apps without worrying about CORS.
Kimi Audio 7B
Show HN: 3D Lord of the Rings inspired museum created with Three.js and Blender
UseBigInt64 deserializes negative numbers incorrectly
1. The resource owner doesn’t want you fetching their resource.
2. They don’t want to suddenly be flooded with requests.
Each of these points has counterarguments. For example, the Same Origin Policy (SOP) only restricts fetches from the client side, and nothing stops people from fetching via a backend.
The second argument makes sense, the resource owner doesn’t want their resource to be freely fetched and to suddenly receive thousands of requests that their server likely can’t handle. SOP helps prevent this, but if you’re fetching from the backend, you should implement caching to avoid repeatedly hitting the target resource.
I created a CORS proxy [0] to handle this scenario, including caching responses.
There are also several free CORS proxies [1] available, they might be considered sketchy, but they’re probably fine for testing.
[1] https://gist.github.com/reynaldichernando/eab9c4e31e30677f17...
in case you don’t want to recreate the video
also nice job on the video demo, was it made using inscribed? :p
Do note that these proxies are for testing only, and they are heavily rate limited.
For production use case, you might consider using Corsfix (https://corsfix.com)
(I am affiliated with Corsfix)
> 1.58-bit FLUX achieves a 7.7× reduction in model storage and more than a 5.1× reduction in inference memory usage