Recent submissions

Comment · 5 years ago
Comment · 5 years ago
This is a fantastic idea. The concept of code tours is something I've been trying to push for via thorough readmes combined with example PRs to show users how to actually do something but this takes it to another level that I'm very happy to see.
Comment · 5 years ago
I think this is the first webpage I've seen that doesn't load at all without AMP. Pretty concerning that developers are going down this route.
Comment · 5 years ago
Seems neat but using Intel chips over AMD is an immediate deal breaker for me.
Comment · 5 years ago
I'm using an Ergodox EZ which I really enjoy and I'm hoping wireless plus a trackball is in the next iteration. Even just being wireless (or a wireless add-on) would be great.
Comment · 5 years ago
Comment · 5 years ago
Why are you sorry for them? They are making the choice to work at Plaid when they know Plaid is a terrible legal phishing company.
Comment · 5 years ago
Are there plans at any point to support remote work? Seems like a very cool product but relocating is a bummer.
Comment · 5 years ago
Last time I looked at a D.C. based job for another federal agency the answer was no. Considering the lower salaries and fact they don't cover relocation costs it's a pretty big downside.
Comment · 5 years ago
You should include details on how long each of those interviews are. 3 technical interviews plus an intro call seems excessive depending on how long they're expected to take.
Comment · 5 years ago
When Twitch Prime was originally released one of the major issues was reminding people that their token was available. I built primeminder as a tool to remind people to renew their Twitch Prime subscription via email notifications: https://github.com/gravyboat/primeminder, the plan was to eventually advertise in the body of the emails once the user base was large enough.

The second was a remote job board like weworkremotely called remote-first (https://github.com/gravyboat/remote-first). This was when weworkremotely was younger and I was pretty dissatisfied with the fact they didn't even support searching for jobs, it was just a messy list that was a pain to search so I thought I could do better to solve this.

Both projects failed.

Comment · 6 years ago
Okay that makes more sense and is just my bad then. I hadn't even looked at the index thoroughly as the minified JS correlated to the `workers-site/worker/script.js` and I didn't realize the index.js was responsible for generating that based on content mismatch.

I generated my worker the second week of May so it's totally possible that this wasn't in the release I generated with. Thanks for pointing out that the template had been updated.

Comment · 6 years ago
Sorry if I wasn't clear. Yes I understand I can set whatever headers I want in a response via the edit options for my workers. The problem I'm running in to is that I created a worker for a static site and it has a massive 1 line JS blob for the script section that I have to go through to set this. I never created this, it's just what was set up when I used Wrangler to deploy my static site.

This is fine except it's a huge hassle to modify and I'm actually a bit surprised that by default workers don't use secure headers. I figured they would since they're pretty standard now and I'd rather have to disable them if I needed then to manually configure them. If someone isn't familiar with security headers there's also a good chance they would deploy their site and never enable them which makes sites running on workers less secure by default.

I'm going off this several year old blog post: https://scotthelme.co.uk/security-headers-cloudflare-worker/ that talks about how to set this up and it seems like functionality has changed a bit since then, or maybe I am misunderstanding their screenshots. Outside of this I can't find any documentation from Cloudflare about setting these headers that is more recent, or what I would need to set for a new worker that has recently been created to get this functionality.

So I guess my question is two fold, are there plans to make it easier to enable secure headers than to manually modify the worker itself? My plan is to do that currently once I stop slacking and decide to just parse this giant JS blob.

My second question is are there any plans to add documentation around functionality such as this? I was really shocked to see that secure headers weren't something that's simply enabled by default and even more so when I looked through the docs and didn't see any examples on how to set them up. Maybe my use case is niche, but I thought secure headers were pretty standard at this point.

Comment · 6 years ago
Hey Kenton. I recently migrated a few of my static sites to Workers and was hoping you could clarify what the teams plan is around security headers. The only documentation I could find was some random blog post from 2 years ago that didn't help as the way workers function has changed since then and it's no longer as simple as just dropping in a few lines of code.

I'd love to easily configure security headers so my sites are getting good ratings again, but I couldn't find it in the documentation and it doesn't seem like there's been any update to support this. Is your team working on making security headers easier to enable for workers or is there something I missed for setting this up?

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton