Cloudflare's R2 costs $0.36 per million read operations (after the 10 million you get for free) [1]. Vercel is wrapping R2 and is charging $2 per million reads [2]. They're also charging $0.15/GB for egress (after the 1GB you get free), when R2 charges nothing, and the storage cost is doubled from $0.015/GB on R2 to $0.03/GB on Vercel. That's quite the cost increase for the DX improvement.
That's their secret, Cap. You've always had to deal with multiple vendors when there's an outage. Vercel has never made it a secret that they're standing on the shoulders of Tier 1 Cloud giants for their hosting backend.
To me, the storage announcement + this blog really helped contextualize where Vercel sits. And I really like this approach. It’s what I’d want to build on. I love the partnerships with cos out of their core expertise like Neon, and existing integrations with supabase, planetscale, etc
I think its a fair assumption that any massive AWS or similar scale company infra outage is going to knock out a good portion of your SaaS and multiple parts of the web
This isn't finalized yet, apologies for the confusion. We'll be updating the pricing for Blob shortly (it's in private beta and invite only). The pricing for KV and Postgres is up to date.
What’s happening right now is a story we’ve seen plenty of times before. Overhead cost of convenience mixed with vendor lock-in, all while boasting about open source.
I’d love to create tools that were convenient and had fair pricing. The challenge is that you’re trying to grow into a market with worse acquisition economics. Tough to win if winning is the goal. If anyone has a solution reach out. XD
Our egress bill from Cloudfront last month, inc. the 1TB/per region free tier, was nearly $2,000. That's egress traffic ALONE (~20TB of it).
Needlessly to say, we're wrapping up testing on migrating our production (public) buckets to Cloudflare (R2) taking our cost from those $2,000 (and going up every month), to (drum roll)... $0,000/mo.
Have I mentioned AWS egress charges are borderline "extortionary"? :X
I am currently developing an option that offers identical quality and features but at a significantly lower cost. Unfortunately, you will have to wait for approximately a year until I complete the development process. However, I believe that the wait will be worth it, and you will be pleased with the outcome.
For what it’s worth when I was TL I would regularly hang out on discord and answer questions for R2. I believe the team still does that and the community itself also answers a lot of questions. Now that I TL Workers KV I do the same in that chat room.
There’s also the community forums although I find it’s harder to stay on top of those personally.
Not trying to say our paygo support is as good. Just saying for those customers, I do personally try to offer ENT-level support as an entire class of users (ie all paygo = 1 ent to me for the products I personally support)
Can vouch for this. The Discord support, aside from specific account/platform problems, has been most helpful and super friendly, both community members and staff.
Good information. I think active community forums are essential for success of all companies and products. Cloudflare has built this up well. Though Customer support issues should be not be left without response for days or weeks, until community moderators use back-channels to get support ticket resolved.
The question was why is Vercel worth paying more for, and customer support is probably one of those reasons.
The secret to great customer support from Cloudflare is to drop into their Discord and join the channel of the product / service you're having trouble with
Most of the engineers and product leaders on the teams that make the services check those channels daily and jump into help where they can. There's also a huge community of power users there called Community Champions who help out as well.
Seems better done than a lot of status pages, runs on separate infra, updated, has a way to subscribe, etc.
However, saying "degraded performance" when you know it's "down for everyone" is an industry phrasing thing that's irritating. AWS also has "elevated response times" when everyone is seeing 5xx errors, or infinite response times.
> However, saying "degraded performance" when you know it's "down for everyone" is an industry phrasing thing that's irritating. AWS also has "elevated response times" when everyone is seeing 5xx errors, or infinite response times.
Another popular one is "elevated API error rates" when the error rate is 1.
having been on the other side a number of times at a site with huge amounts of traffic, very often things can be down for a huge percentage but our logs will still show thousands of requests succeeding a minute. so it might be working well but slowly for some while not at all for many
Also seeing unicorns, mostly for "No server is currently available to service your request.". If I don't get a unicorn, the page takes a long old time to load.
Related, LMC is a great simulator to learn basic CPU instructions on (I encountered it both at school and at university [UK]): https://peterhigginson.co.uk/lmc/
The one feature I really want for window management on macOS is the ability to split fullscreen applications horizontally, for my vertical monitor. macOS lets you split a fullscreen app vertically so you can have two on the same screen, but when a monitor is oriented vertically you can still only split the screen vertically, not horizontally. Sigh.
You can get value out of yabai even without disabling SIP to add the hooks into Dock.app. The things it needs that for isn't that long of a list, see the first bulleted list here https://github.com/koekeishiya/yabai/wiki/Disabling-System-I... , maybe you don't need those / can replicate them without yabai?
When I initially read this on that page,
> The following features of yabai require System Integrity Protection to be (partially) disabled:
, I thought that meant "so yabai just won't work at all if you don't disable SIP", but it's not the case at all. I use hammerspoon to deal with spaces, and don't care about window transparency/shadows/animation, and I don't know what "picture in picture for any window" means. I do miss stickiness and per-window floating (which are features I used in XMonad), but it's fine, I'm not going to disable SIP for those.
Particularly, if you just want focus-follows-mouse like in X Windows, yabai gives you that without disabling SIP.
I will also +1 this as an i3wm user. I do use displayplacer and yabai together though. I have two identical external monitors that don't behave well with MacOS. Apparently the monitor's unique id's are not unique in MacOS. This causes MacOS to get them mixed up any time I disconnect from them. I have a keyboard shortcut that uses displayplacer to toggle between the two monitor valid configurations.
This person [0] also had that issue, they found that for their monitors for whatever reason, using the contextual screen IDs instead of the persistent ones always results in a consistent configuration. Might be worth a shot.
Since we're on the topic of tiling manager, I'm still using ShiftIt on my old macbook and I still think it's one of the best window manager since it allows you bind keys to particular actions and stays out of the way with minimal configuration. It's not being maintained though.
:wave: Hi, some of y'all may remember me from previous years -- I work on the engineering (and social/support to some extent) of Hacktoberfest.
As a few commenters have noted, Hacktoberfest has had spam problems in the past, mostly due to folks chasing a free t-shirt without thinking about what they're actually doing to achieve that. I'm super sorry about that, it's not what we want this program to be.
In response to the massive spam wave we saw in 2020 with the program, we made some substantial changes to the rules for Hacktoberfest (during the 2020 event, and since) to help reduce the level of spam:
- Hacktoberfest is opt-in for maintainers. They need to add the "hacktoberfest" topic to their repos.
- Contributors are only rewarded for PR/MRs that maintainers accept. Merging, overall approving review, or the "hacktoberfest-accepted" label count.
- Contributors that have two or more PR/MRs identified as spam (either via our automated logic, or maintainers labeling a PR/MR as "spam") will be disqualified permanently.
As always, we're open to feedback on what more folks think could be done to avoid spam with the program, while still keeping it accessible to new folks that want to contribute to open source. hacktoberfest at digitalocean dot com is the place to send that feedback <3
Since most of the comments here have a negative sentiment I just want to say as both a participant and an open source maintainer: I love what you're doing! I am excited to contribute to awesome projects and add another t-shirt to my collection plus can't wait to see contributions from others to my projects!
First impressions are important. We rely on them to filter out a lot of information and reduce options when making decisions. For example, a bad first impression will result in no second-round interview, no first or second date, a lost sales opportunity. I don't think it's unfair to extend that to events such as this. Especially because it's still ultimately a tool to promote Digitalocean services.
If it were up to me, I think I'd modify the site title and social media card data to properly reflect that they've made changes to reduce the negative impact of their promotion on the public. "Hacktoberfest 2022: Lessons Learned Edition" or something slightly tongue-in-cheek and self-effacing. The way it is presented now makes it look like it'll be more of the same.
Congratulations Matt (and @Logan_Liffick, @xamthorz). What a huge improvement over last year's design and site. Good luck with the program, may your service states be predictable and efficient. I'll be participating this year for the first time as a maintainer rather than as shadow hand :D
These sound like very positive changes!
Would you consider going through past years and pre-emptively disqualifying people for their previous spam PRs as well?
And is it obvious on the website to someone when they're disqualified? Or do they just not get a reward?
We don't have easily accessible data on previous years' contributions (we'd have to scrape GitHub again for it all), and I'm not sure disqualifying folks based on historical contributions would be overly fair as they didn't agree to that back then.
Disqualification was rule last year though, and those that were disqualified last year will still be disqualified this year. I'm not sure if there was any obvious messaging last year when someone was disqualified, other than not getting a reward, but this year will definitely show dedicated messaging for those users (working on this profile state as I write this).
[1] https://developers.cloudflare.com/r2/pricing/
[2] https://vercel.com/docs/storage/vercel-blob/usage-and-pricin...