71–79 of 79 posts
If Cloudflare wants to branch out, here're an idea. Global Memcached or Redis. Support caches near the edges. SPA or apps running on a client's browser/machine can use the one nearby. Support pre-populating/warm-up the caches in batch.
CF already supports this type of thing, workers and the kv store ... https://www.cloudflare.com/products/workers-kv/
Earlier quoted context omitted.
still 170K on the waitlist after 2 months? haha
soonhorse.jpg
https://www.google.com/search?hl=en&q=soonhorse.jpg
Online marketing at it's best.
I'm surprised I've not seen this meme before. https://soon.horse/
I’m amused this is here. This was a random reply to someone who thought maybe we were doing this. To be clear: that’s all this is. But I’m happy to hear all the suggestions.
I feel like right now we are in a fairly centralized state regarding where packages come from and outages and other issues can really impact the CI/CD and development of different services.
Earlier quoted context omitted.
I'm a big supporter of Cloudflare and have been using it for almost 8 years. I personally don't think doing something like that is what Cloudflare needs. What Cloudflare needs is further customization, especially in regards to caching. We actually had to migrate a certain part of our infrastructure to Fastly due to the lack of caching customization/rules. I'd like to see: - Custom caching rules similar to the new fir…
FWIW, our Workers product is pretty good at allowing you to define custom caching rules. We have a section in the Workers docs specifically focused on the Cache API: https://developers.cloudflare.com/workers/reference/cache-ap... If that doesn’t help you build what you’re looking for, happy to chat via email and hear more about what you need: kristian@cloudflare
Also your link is missing a trailing slash (which is odd that their router doesn't add that). https://developers.cloudflare.com/workers/reference/cache-ap...
1) Vary by cookie for $20/mo or free plans
2) A page rule for “don’t send origin cookies” or something (useful for not passing through those headers from the origin for assets/etc)
3) getting the peering connections better in AU so the network handles traffic like normal instead of only $200/mo plans getting priority/local AU routing
More seriously. I’d be curious to hear about what you’d build on our network. We are all over the world and it would be fun to hear about companies other than GitHub that you think we should disrupt.
Earlier quoted context omitted.
Bare git only stores code, not issues, tickets, wiki, and all the stuff that goes beyond source files. There are a myriad of open source solutions for this, but there is no standard format that allows easy migration and inter-linking.
would be easy enough for a branch of "issues" containing a number, index.json and ####.md where the number is the initial issue and comments, with some front-matter to associate user details.
I'm kind of surprised it isn't already like this, or similar.
