elithrar

13 ms·

31.
by elithrar 4y ago
No concrete plans at this time, especially since there are many competing implementations. If we open-sourced we’d need to do it right (proper governance, triage, support, etc) vs just putting into a public repo and calling it a day.
32.
by elithrar 4y ago
D1 _does_ use Durable Objects under the hood! Like Pub/Sub, it's ultimately an implementation detail, albeit probably interesting to this audience.
33.
by elithrar 4y ago
In the MQTT world, in which Pub/Sub is based, every publisher is a client, and every subscriber is a client. You can be both, too! Assuming your existing backend is in $SOME_CLOUD_PROVIDER, publishing messages to Pub/Sub is just a
34.
by elithrar 4y ago
(I'm the PM for this at Cloudflare & the blog author) We looked at a number of existing options — trying to strike a balance between languages we run at scale (tooling, ops, security), memory safety, and long-term maintainability a
35.
Cloudflare Pub/Sub: Programmable MQTT Message Brokers(blog.cloudflare.com)
128 points by elithrar 4y ago|47 comments
36.
D1: Our SQL database(blog.cloudflare.com)
592 points by elithrar 4y ago|228 comments
37.
by elithrar 4y ago
This thread by Kenton Varda (one of the engineers on the Workers platform) explains it in different terms: https://twitter.com/KentonVarda/status/1524033314448891905 Put really concisely: you want to add serverles
38.
Cloudflare Workers for Platforms: Make Your Own Product Programmable(blog.cloudflare.com)
13 points by elithrar 4y ago|17 comments
39.
by elithrar 5y ago
(Feel free to drop me an email - silverlock@cloudflare.com - if you want to chat more) We’re iterating on a standard for this - our current thinking is to use well-known URIs to publish both a public key (is the hash legit?) and hash endpoi
40.
by elithrar 5y ago
(I lead privacy products at CF and co-authored the linked post) This—improving trust in the system and making it provable—is something we're looking to do. Having the publisher sign the hashes and publish the public key is one approach
41.
by elithrar 5y ago
Not all .ru sites are state-owned.
42.
by elithrar 5y ago
> dns is not ip addresses. all that means is russian websites would stop working via normal dns, not that ip addresses would stop routing and non .ru would continue to resolve normally A “man on the street” isn’t browsing via IP address,
43.
Cloudflare acquiring email protection provider Area 1 Security(bloomberg.com)
5 points by elithrar 5y ago|0 comments
44.
by elithrar 5y ago
RE: intelligence agencies - https://twitter.com/wingarscarlett/status/148160261830488883... One of the replies to Ben’s tweet includes a diagram and references to the NSA’s RJ-45+Ethernet capturing device within t
45.
by elithrar 5y ago
> and also believe Firefox is going to be forked Out of curiosity: by whom? I don't think this is likely at this point, short of some truly benevolent benefactor pushing tens of millions of dollars per-year into a competing foundati
46.
by elithrar 5y ago
> In the ESO hybrid energy storage system, Invinity’s vanadium flow batteries are used to ‘front-end’ the energy asset, acting as a first line of response when the system is called into service; only after the required response exceeds t
47.
by elithrar 5y ago
I have seen this “non-zero” times - not common, but it exists. Some folks are insistent that their PR and their specific problem be addressed by your project, and the effort they put into writing code before discussing it just increases the
48.
Relational Database Connectors for Cloudflare Workers(blog.cloudflare.com)
49 points by elithrar 5y ago|13 comments
49.
by elithrar 5y ago
As John says - sounds odd - but please drop me an email with more details - silverlock at cloudflare Understanding the # of unique names, peak QPS, % of response types, etc will help. I consider it a “bug” if you can take the same profile o
50.
Cloudflare Distributed Web Gateways: Unlocking the Web3 Metaverse(blog.cloudflare.com)
106 points by elithrar 5y ago|16 comments
51.
by elithrar 5y ago
The blog post on egress speaks to that - but the true scale at which the major clouds buy hardware and deploy it - just changes the dynamics here. We're (collectively) not used to seeing products marked up to such an extent. The $&#x2F
52.
by elithrar 5y ago
WebRTC Components (TURN) doesn't discriminate being media tracks or data channels, and will relay data channels as well :-) We also have WebSockets via Cloudflare Workers for layering more complex logic on top: https://devel
53.
by elithrar 5y ago
This is a fairly common definition of real time - not specific to Cloudflare. Two people talking over PSTN/cellular between Sydney and London is >= 250ms in the best case. Participants in the same country obviously won’t see this ki
54.
by elithrar 5y ago
> and some higher level libraries for using WebRTC Not libraries - we’re building APIs that allow you to create rooms/channels, connect participants, manage authn/authz, ingest via non-WebRTC protocols (and still broadcast to p
55.
by elithrar 5y ago
> My hypothesis is that if Netflix/Youtube hadn't stressed out our bandwidth and forced the ISPs of the world upgrade for the last decade, the world wouldn't have been ready for WFH of the covid world. Couldn't agree
56.
by elithrar 5y ago
> I heard they are paying something between $0.20 (eu/us) to $10 (exotic) per TB based on the region of the world where the traffic is coming from They're likely paying even less. $0.20/TB ($0.0002/GB) is aggressive b
57.
by elithrar 5y ago
> Most ISPs don't though. You sure? ISPs can, and do, this fairly readily. They wiggle on what “your data is” (“CPNI”) but browsing history via DNS queries is not uncommon (and cheap, to boot). Go read Spectrum’s policy and how they
58.
by elithrar 5y ago
The JavaScript Challenge pages only run on dynamic assets, and so won’t impact image assets served. Beyond that: • You can turn down the sensitivity of the challenge pages: https://support.cloudflare.com/hc/en-us/a
59.
by elithrar 5y ago
Correct. More specifically, you breathe a denser oxygen mix (2 atmospheres of density).
60.
by elithrar 5y ago
> Cloudflare DNS does not route efficiently with AWS CloudFront anycast DNS. I tracked down insanely slow `rustup update` downloads to incorrect selection of ideal routes to the AWS resources caused by using CF to resolve the DNS. Please

More ›