gravyboat
Joined 11 years ago
Joined 11 years ago
It also doesn't work for team based projects. I'm one of the maintainers of Streamlink [1] which has members from around the world and we've been running various methods of donation since 2017 or so. In that time our Open Collective [2] has made about $1600 USD. We have over 50,000 users across all platforms (based on download stats as we don't collect any metrics in our apps so it's potentially higher) yet the entire amount we've collected is thanks to less than 100 people. We note the Open Collective on every release as well.
My own personal donation methods total $15 from one person in the past 5 years since we forked the project and started maintaining it. We have more users than many start ups do and I know that there are several companies using our software, but I haven't figured out how to make donations really work yet. How do we determine who should make what from a shared pool of money? How do you value a contribution, PR, etc., and most importantly how do you get users to actually pay without negatively impacting the project?
[1]: https://github.com/streamlink/streamlink [2]: https://opencollective.com/streamlink
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.
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.
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.
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?
My own personal donation methods total $15 from one person in the past 5 years since we forked the project and started maintaining it. We have more users than many start ups do and I know that there are several companies using our software.
[1]: https://github.com/streamlink/streamlink [2]: https://opencollective.com/streamlink