👋 hello!!

looking forward to getting stuck in in Jan! :)

New Relic added a poll to see if others would be interested in adding support for Cloudflare Workers https://discuss.newrelic.com/t/feature-idea-support-for-cloudflare-workers/125321

hey everyone, if you need to DM the team on anything, please direct those messages only to me or @User please. We're the ones responsible for this Discord 🙂

this is so weird... I guess the server components could be rendered in a Cloudflare Worker? https://reactjs.org/blog/2020/12/21/data-fetching-with-react-server-components.html

I really don't get how caching would be handled though... would appreciate it if some people on the workers team would provide feedback on the RFC. 🙂

I watched the first half of the video last night and keep meaning to come back to it

it kind of hurts my head

but honestly it formalizes a lot of what Next.js and Flareact are doing

I found the differentiation between server/client components pretty straightforward which I was surprised about

it seems like you could probably instantiate components on the server and enrich them with KV/Durable Objects before sending them to the client which would be super dope

I've seen example repos floating around I just haven't dove fully in yet

right?! so flareact makes a request to cloudflare on page navigation to get the "props" for that page (in JSON) this seems like the same kind of thing (ish). So in that way it's replacing getEdgeProps with a standard Server component. 🙂

I think the only thing that would really be needed is a "react io" library for Cloudflare to access fetch (like their react-fetch example) and kv

or the Cache API. 🙂

what I've always thought annoying about Next/Flareact is that the props are either generated on the server or on the client, you can't opt-into both

this is actually a big problem on https://chickar.ee/ because while I want a resource like https://chickar.ee/www.nytimes.com to load from the server, it's actually way more effecient to load it from the client (because the client has DOMParser)

to get around this limitation, I'm using HTMLRewritter to just rewrite the metadata on the worker. :/

see: https://github.com/chickaree/edge/blob/2263d0cccb28c4b358664bf05388397bda99a2b7/handlers/next.js

so it's exciting to see "shared" components that would work either on the client OR on the edge

Maybe, you should create another group "Community Managers" to make it more easy to understand. Having a group Workers Team is an "invitation" to DM. Then add the notice to the welcome message.

Agreed. Will update soon about creating a community champions group - trying to get resources on my end to send free Cloudflare stuff to anyone who wants to join!

Free enterprise when 🥺🤪

I'd be happy with just Cache-Tag support on the free plan. 🙂 or even better... open souring the worker for WordPress. 😛

fun fact: Drupal has Cache-Tag support out of the box. 🙂

I'm going to preface this by saying my work is completely unrelated, but my best guess from reading the post is that some government approved and regulated center has actual large sets and performs the hashing on their end, after which the service mentioned in the post just rapidly checks for hash similarity on data in transit

> "Today our teams are working on adding additional cabling and more generators to provide more power into the building for our equipment and the restoration efforts. We continue to assess the damage to the facility and have confirmed that the building’s commercial power connections are damaged and offline. We are working with the local power utility on repairs. In addition, there is other significant damage to the building from the blast, including to the elevators, some beams/columns, and the building’s façade. - AT&T Sunday update https://fox17.com/news/local/att-internet-phones-911-issues-from-bombing-continue-into-sunday-downtown-nashville-tennessee-broadway-outages I fucking hope the incoming FCC holds a hearing on this. I think every American wants to know why the bombing of one building dropping power to an internet exchange managed to take down Verizon, T-Mobile, and AT&T, and over 72-hours later there was no plan in place to restore access to 911 call centers.

It’s incredible that one internet exchange being bombed knocked out all three cellular providers in the state

I already know...

Despite the internet exchange being literally bombed the Cloudflare Nashville DC is fully operational