2
points
reynaldi
Joined 118 karma
meet.hn/city/id-Special-capital-Region-of-Jakarta
Socials: - x.com/reynaldicher - github.com/reynaldichernando
---
- reynaldi parentI initially thought it to be the AI context already filled with previous rehearsal conversations. And it remembers that the ingredients are already prepped. In which case, they could just start another chat to start fresh.
- 3 points
- 263 points
- 1 point
- 5 points
- 5 points
- Not sure if my feedback can help.
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.
- VS Code with GitHub Copilot works great, though they are usually a little late to add features compared to Cursor or Windsurf. I use the 'Edit' feature the most.
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.
- 1 point
- Currently building a CORS Proxy.
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.
- 1 point
- 2 points
- 2 points
- I agree with this, but in my past online discussions about fetching publicly available information, two main arguments often arise:
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...
- These services are called CORS proxies! I recently made an updated list of the currently working free ones here: https://gist.github.com/reynaldichernando/eab9c4e31e30677f17...
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)
- 2 points