text stringlengths 0 1.36k |
|---|
**Alex Sexton:** My pick will be Observatory from Mozilla, which is the security checker that I mentioned before. If you have a website and you're interested in finding the security properties of that website and what you might wanna do to increase them, such as get rid of your SHA1 certs, then check out Observatory.mo... |
**Rachel White:** My pick is actually a talk, and it's Mariko Kosaka's talk on How Computers Read Pixels. It's really interesting and has great diagrams if you're ever wondering how image processing works, which is a foundation for a ton of augmented and mixed reality stuff with WebGL. It kind of helps you understand o... |
**Mikeal Rogers:** Mariko's talks are always so good. She really dives into these concepts that everybody takes for granted, and really learns them and explains them in a really amazing way. |
**Rachel White:** I know. I've told her that I really appreciate how she doesn't just explain how something's working so that it's accessible to everyone, but she also tells the journey of what lead her to want to even do that in the first place, and the struggles that she had while making it, and then the successes. T... |
**Mikeal Rogers:** Of course, you can find links to all this stuff in the show notes. That's it for this week... We'll of course be back next week. Rate us on iTunes, because that's the thing that people say at the end of podcasts, so you should probably do that... |
**Alex Sexton:** Subscribe and rate! |
**Rachel White:** And be nice! |
**Mikeal Rogers:** Subscribe, be nice... And yeah, check us out at JsParty.fm. |
• Google's announcement about Internet security flaws |
• SHA-1 hashing algorithm has been cracked |
• Discussion on the impact of SHA-1 being broken |
• Explanation of how SHA-1 works and its uses in Git |
• Concerns about the ease of forging hashes and the potential for malware injection |
• The speaker discusses the relatively insecure nature of "shot one" and how its continued use has been debated in the security community since 2005. |
• Alternative algorithms are available that don't have the same problem, but shot one is still widely used due to Linus Torvald's skepticism. |
• Google and German researchers publicly revealed a method to crack shot one, making it clear how they did so. |
• The attack requires significant computing power (over 100 years of time) but will become more feasible as technology advances. |
• Using "shot two fifty six" is recommended instead, which has higher entropy and is essentially the same algorithm with some improvements. |
• Multi-hash is a format that allows for optional support of different encryption algorithms and hashing functions to future-proof applications. |
• Security on the web is a multilayered concept, and breaking one layer doesn't make the others secure |
• Using Cloud Slayer or SSL/TLS can provide security, but it's not enough |
• A single weak link in authentication can compromise the entire system, making a chain or linked approach more effective than an onion metaphor |
• OAuth initially used extra encryption to protect against HTTP without TLS, but later dropped this practice when using TLS |
• TLS can be compromised by certificate authorities being hacked, so relying solely on it for security is not enough |
• Mozilla Observatory is a useful resource for checking website security and providing a prioritized list of improvements |
• PCI determines algorithms for storing credit card numbers and other sensitive data |
• Don't implement security measures yourself, use well-known libraries instead |
• Cryptographic techniques like SHA-1 are not recommended, use alternatives like Bcrypt or Sodium encryption |
• Use CI tests to check for known vulnerabilities in dependencies like NPM packages |
• Utilize services that scan open-source modules for vulnerabilities and offer patching solutions |
• Node.js version 7.6 release |
• V8 engine update and ABI changes |
• Async/await feature now enabled by default in Node.js |
• Performance concerns and comparisons to callbacks and promises |
• History of promise standardization and competing standards (A+, B, C, D) |
• Dominic Nicola's work on promoting a unified promise standard |
• Browser API inconsistencies for IO handlers |
• Benefits of having a standardized async/await feature |
• Discussion of native promises in Node.js and their limitations |
• Comparison of native promises to other libraries such as Bluebird |
• Async await feature as syntactic sugar for promises |
• Error handling with promises, including error eating and tracking |
• Performance considerations with async/await |
• Indifference towards code preferences and the lack of controversy |
• Node's error handling conflicts with the way node handles errors |
• Production systems have issues with promises swallowing errors |
• A style argument exists between object-oriented and functional programming approaches to promises |
• Callback hell is a common issue in asynchronous coding |
• Async functions and generators are alternative mechanisms for asynchronous coding that don't swallow errors |
• Coroutines and the co library are used in some cases, particularly in China |
• The async module was an early attempt at bridging the gap between callbacks and promises |
• Community growth and imitation in software development |
• Comparison of node bots and web application development |
• Challenges with sequential actions and asynchronous programming |
• Performance arguments for promises vs native functions |
• Personal preferences and opinions on callback hell and promise usage |
• Feature Project of the Week: ARJS |
• ARJS (Augmented Reality for JavaScript) is a library that uses ARToolkit and A-Frame to blend augmented reality with digital markers |
• ARJS can be used with Android phones, but not iOS phones due to technical limitations |
• The library allows developers to create interactive 3D objects that appear as holograms when viewed through a phone or device |
• A-Frame is a popular tool for creating WebGL VR in the browser and is being used as the foundation for ARJS |
• The library has good documentation and runs at 60 frames per second on devices such as the Nexus 6 |
• Discussion of Leap Motion device and its capabilities |
• Possibility of using Leap Motion with augmented reality applications |
• Mention of Mayo armband for hand tracking |
• Comparison of Leap Motion and Mayo armband features |
• Idea of combining Leap Motion with other technologies (e.g. Maya) to create interactive experiences |
• Reference to past examples of innovative demos (e.g. Emscripten compiling Doom) |
• Discussion of future possibilities in augmented reality, including drawing shapes on paper and manipulating them in 3D space |
• WebGL programming experience |
• A-Frame and 3JS libraries used for development |
• Regal library as an alternative to 3JS, with improved tooling and debugging |
• Makola Lysenko's work on Regal and its features |
• Bits.coop consulting business and its cooperative model |
• Observatory security checker from Mozilla |
• Marco Kosaka's talk on computer pixel reading |
• Discussion of Maria Kosaka's talks and her approach to explaining complex concepts |
• Plans to feature library, project, or talk spotlights every other week |
• Mention of links in show notes for further information |
• End of episode announcements (rating, subscribing, etc.) |
• Upcoming live podcast schedule (Fridays at 3 p.m. U.S. Eastern) |
[0.00 --> 5.22] Bandwidth for JS Party is provided by Fastly. Learn more at Fastly.com. |
[8.98 --> 13.04] Welcome to JS Party, a weekly celebration of JavaScript and the web. |
[13.42 --> 18.36] Tune in live on Fridays at 3 p.m. U.S. Eastern at changelaw.com slash live. |
[18.70 --> 22.74] Join the community and Slack with us in real time. Head to changelaw.com slash community. |
[23.26 --> 27.00] Follow us on Twitter. We're at JS Party FM. And now on to the show. |
[27.00 --> 31.40] Hey, everybody. Welcome to JS Party, where it's a party every week with JavaScript. |
[32.28 --> 34.82] All right. Let's dive right into it. |
[35.98 --> 40.58] I want my voice to be heard that I think that's a dumb slogan. Move on. |
[41.44 --> 44.66] I kind of, I think it's dumb, but I like making Michael say it. |
[45.04 --> 47.32] Okay, that's fair. That's fair. That's very fair. |
[47.42 --> 48.98] That's really fair. That's really fair. |
[49.34 --> 50.36] All right. I'm Michael Rogers. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.