servo / blog.servo.org Goto Github PK

http://www.ifdown.net/servo-starters/ is cool! Please put the link on the blog so I can find it more easily next time I forget where it lives 🔍

(also https://github.com/servo/servo-starters)

This here breaks:

<link rel="canonical" href="{{ page.url | replace:'index.html','' | prepend: site.baseurl | prepend: site.url }}">

Currently resulting in:

<link rel="canonical" href="http://blog.servo.orghttp://blog.servo.org/">

should be without the double leading baseurl.
It's the same for the feed which will most likely break some feed readers.

I just commited a change to blog.servo.org by mistake: 3add526

Github allows me to edit a markdown file, and create PR, but I clicked on "Commit" instead of "Create a PR".

Maybe we should add something to prevent accidental commits.

As part of deploying HTTPS for servo.org, I'd like to also get HTTPS on blog.servo.org. To get end-to-end encryption on the blog, I need a https:// URL to point the servo.org CloudFlare DNS at.

Problem: When you access this site at https://servo.github.io/blog.servo.org/, the CSS isn't displayed and the posts have invalid URLs (ie http://servo.github.io/2015/11/30/twis-43/).

Fork this repository and then visit https://yourusername.github.io/blog.servo.org to see how it looks and verify that the blog post URLs resolve.

By the time TWiS will get written next, the servo/servo project will probably have reached 5k stars

Yay arbitrary base-10 achievements

When we initially switched our DNS to CloudFlare, there were some concerns about accessibility for Tor users. Thanks to recent cloudflare improvements (https://support.cloudflare.com/hc/en-us/articles/203306930-Does-CloudFlare-block-Tor-), we have now explicitly whitelisted traffic from Tor so that legitimate users won't see CAPCHA challenges when accessing servo.org sites.

In _posts/2017-01-04-twis-86.md, point 5 of the "Notable Additions" section has the link https://github.com/servo/servo/issues/147840, which should be servo/servo#14784

Simple, short formula with freeform responses:

• tell us about yourself
• why did you start contributing to Servo?
• what was challenging about your first contribution?
• what do you like about contributing to the project? what do you get out of it?
• any final thoughts you'd like to share?

the weekly blog post contain link to weekly status update as https://www.standu.ps/project/servo/, but the link do not function any more .

<ajeffrey> standups: We now have performance tests for the Alexa top 10, contributed by the servo community! https://github.com/servo/servo-warc-tests/issues/8