http://peerjs.com/ → https://peerjs.com/

posts/401.md

@@ -45,7 +45,7 @@ So we sat down and built it. A Javascript frontend, and Go backend. We ran into
 
 One of the best parts of RC, in my opinion, are the check-ins. Check-ins happen every day at 10:30, Monday through Thursday at RC. You get together with six to eight people \(the group changes weekly\), and talk about what you did the previous day, and what you're doing today. My favorite check-in spot was the McCarthy room \(all of the rooms [are named after famous programmers](https://recurse-center.squarespace.com/blog/2015/6/27/days-32-33-34-room-names-at-rc)\). McCarthy is interesting because it actually isn't a room, but rather two couches at 90 degrees from each other, with a tall table you could stand and work at or setup a projector and display things on the wall. I liked it because I could sit down, and the check-ins I had there always seemed super relaxed, and maybe even a little silly, compared to check-ins I had in other spots.
 
-My third project came from a check-in at McCarthy. [Pam Selle](https://thewebivore.com/about/) was talking about this cool idea she had. It had come up a few times when we had talked before, but now her time at RC was nearing the end, and so she asked for help with something \(I don't remember what\), and I said I would help. And thus, I found myself working on [ShhParty](https://web.archive.org/web/20220216070340/http://shhparty.herokuapp.com/). The code is at [pselle/shhparty](https://github.com/pselle/shhparty). Pam's idea was to build a service where you could create a peer to peer [silent dance party](https://en.wikipedia.org/wiki/Silent_disco) with no server in the middle. Using [peer\.js](http://peerjs.com/) we built a system where a user visits the site, creates a party, and then other users and come and join the party. The server only keeps track of the parties, not who is at which one, nor does the stream from the party creator ever reach the server. After we got the basic functionality working, [Cole](https://twitter.com/fantasticole) came in and redesigned it for us. Overall a great success\!
+My third project came from a check-in at McCarthy. [Pam Selle](https://thewebivore.com/about/) was talking about this cool idea she had. It had come up a few times when we had talked before, but now her time at RC was nearing the end, and so she asked for help with something \(I don't remember what\), and I said I would help. And thus, I found myself working on [ShhParty](https://web.archive.org/web/20220216070340/http://shhparty.herokuapp.com/). The code is at [pselle/shhparty](https://github.com/pselle/shhparty). Pam's idea was to build a service where you could create a peer to peer [silent dance party](https://en.wikipedia.org/wiki/Silent_disco) with no server in the middle. Using [peer.js](https://peerjs.com/) we built a system where a user visits the site, creates a party, and then other users and come and join the party. The server only keeps track of the parties, not who is at which one, nor does the stream from the party creator ever reach the server. After we got the basic functionality working, [Cole](https://twitter.com/fantasticole) came in and redesigned it for us. Overall a great success\!
 
 Week Six ended, and with its end, half of the people I spent every day at RC with left. You see, each batch at RC is thirty-ish people. And every batch overlaps with two other batches for six weeks. So for the first six weeks, my batch \(Spring 2, 2015\) shared the space with "Spring 1, 2015" and then the last six weeks, we shared the space with "Summer 1, 2015". Our batch actually had two weeks off in between batches, because there was an alumni week, and a week of planning for the facilitators. But I used a lot of this time to continue working on stuff.