Episode 110 of The SitePoint Podcast is now available! This week the panel is made up of Louis Simoneau (@rssaddict), Patrick O’Keefe (@ifroggy), and Stephan Segraves (@ssegraves).
SitePoint Podcast的 第110集现已发布！ 本周的座谈会由Louis Simoneau( @rssaddict )，Patrick O'Keefe( @ifroggy )和Stephan Segraves( @ssegraves )组成。
在浏览器中收听 (Listen in Your Browser)
Play this episode directly in your browser — just click the orange “play” button below:
直接在浏览器中播放此剧集-只需点击下面的橙色“播放”按钮即可：
下载此剧集 (Download this Episode)
You can download this episode as a standalone MP3 file. Here’s the link:
您可以将本集下载为独立的MP3文件。 这是链接：
SitePoint Podcast #110: Louis’ First Show (MP3, 42:14, 40.6MB)
SitePoint播客＃110：路易的首秀 (MP3，42:14，40.6MB)
剧集摘要 (Episode Summary)
Here are the topics covered in this episode:
以下是本集中介绍的主题：
- The AWS outage and what it means for cloud computing AWS故障及其对云计算的意义
- myYearbook and moderating live video chat myYearbook和主持实时视频聊天
- CSS3 vs. CSS: a speed test CSS3与CSS：速度测试
- Facebook launches “Send” Facebook启动“发送”
- jQuery 1.6 beta released jQuery 1.6 Beta发布
Browse the full list of links referenced in the show at http://delicious.com/sitepointpodcast/110.
浏览http://delicious.com/sitepointpodcast/110中显示的参考链接的完整列表。
主持人聚光灯 (Host Spotlights)
Stephan: Extending WiFi to one mile
斯蒂芬： 将WiFi延伸到一英里
Patrick: NewME Accelerator
帕特里克： NewME加速器
Louis: The Cicada Principle and Why It Matters to Web Designers
面试成绩单 (Interview Transcript)
Louis: Alright, so here we are another episode this week. It’s my first time on the show with you guys so hi Stephan.
路易斯：好的，所以这是本周的另一集。 这是我第一次和你们一起参加演出，所以斯蒂芬嗨。
Stephan: Howdy.
史蒂芬：你好。
Louis: And hi Patrick.
路易斯：嗨，帕特里克。
Patrick: Hey, Louis, welcome to the show, the group show officially.
帕特里克(Patrick)：嗨，路易(Louis)，欢迎参加表演，正式参加集体表演。
Louis: Yeah, yeah, well I’ve been doing a couple interviews but it’s my first time actually on the panel so that’s exciting. Unfortunately Brad could not make it today. We got pushed back a day later than usual because it was a public holiday here in Australia and I was not in the city so I didn’t have access to any kind of high speed Internet.
路易斯：是的，嗯，我已经进行了几次采访，但这是我第一次真正参加小组讨论，这很令人兴奋。 不幸的是，布拉德今天无法做到。 我们被推迟了一天，比平常晚了一天，因为这是澳大利亚的一个公共假期，我不在城市里，所以我无法使用任何类型的高速互联网。
Patrick: We had some discussion amongst us if that was a real holiday or not because there was no holiday here, I’m not real sure.
帕特里克(Patrick)：我们之间进行了讨论，以确定那是否是一个真正的假期，因为这里没有假期，我不确定。
Louis: Actually it was a weird one because there are usually two public holidays in April, so there’s Easter which is a normal one, and then there’s Anzac day which is kind of like our Memorial Day or Veteran’s Day here.
路易斯：其实这很奇怪，因为通常在四月有两个公共假期，所以复活节是正常的假期，然后是安扎克节，就像我们的阵亡将士纪念日或退伍军人节。
Patrick: So that was a terrible joke and I should feel really bad, I’m sorry.
帕特里克：这是一个可怕的笑话，对不起，我应该感到很难过。
Louis: (Laughs) no, but they actually fell on the same weekend this year, so we had a five-day weekend; the usual four-day weekend for Easter plus an extra one for Anzac day, so that’s why we had a Tuesday off which is kind of weird. But yeah, so I was out of the city but I’m back now and on the equivalent of a Monday morning for me I’m here recording the podcast with you guys.
路易斯：(笑)不，但是实际上他们是在今年的同一周末，所以我们有一个五天的周末。 通常是复活节的四天周末，再加上安扎克一天的额外周末，所以这就是为什么我们在星期二休假有点奇怪。 但是，是的，所以我出城了，但现在我又回来了，相当于我一个星期一的早晨，我在这里与你们一起录制播客。
Stephan: Glad to have you here.
史蒂芬：很高兴有你在这里。
Louis: Yeah, it’s good to be here. I realize I’ve got some big shoes to fill, Kev was a fixture on the show for so long, but I’ll try and step in and see how we can roll this, and as Kev said on the last show he’ll probably be around for some panel shows in the future so that’ll be fun as well.
路易斯：是的，很高兴来到这里。 我知道我有很多大鞋要塞，Kev一直是秀场上的固定装置，但我会尽力介入并看看如何滚动，就像Kev在上一场秀上所说的那样将来可能会参加一些面板展示，所以也会很有趣。
Patrick: So before we get started with the stories I wanted to mention that the SitePoint Podcast will be back at WordCamp Raleigh for the second straight year, we made our first live show, our live debut last May in Raleigh, North Carolina for WordCamp Raleigh, and we’re going to be back again same dates, May 21st and May 22nd is the conference, we’re going to be recording the show May 21st from 12:00 p.m. to 2:00 p.m. Eastern Standard Time, that’s UTC minus four, and right now we plan to stream that through SitePoint.com/podcast, and there’s a lot that has to be announced or decided, but we wanted to make sure you knew about it so you could keep an eye out for that or if you’re in the area definitely stop by and attend the conference, that’s wordcampraleigh.com for more information.
帕特里克(Patrick)：因此，在我们开始讲故事之前，我想提一下SitePoint Podcast将连续第二年回到WordCamp Raleigh，我们进行了首次现场表演，我们于去年五月在北卡罗来纳州罗利进行了首次现场表演，为WordCamp Raleigh和我们将要再次回到同一日期，5月21 日和5月22日nd时的会议上，我们将要录制节目5月21 日 ，从下午12:00至下午2:00东部标准时间，这是UTC减4，现在我们计划通过SitePoint.com/podcast进行流式传输，有很多事情需要宣布或决定，但我们想确保您了解它，以便您随时注意或如果您确实在该地区停留并参加会议，请访问wordcampraleigh.com了解更多信息。
Louis: Awesome. I imagine is Brad going to be giving some talks there or a talk?
路易斯：太好了。 我想布拉德会在那里演讲还是演讲？
Patrick: Yeah, both Brad and myself will be speaking. Brad is delivering a presentation called Surviving the Zombie Apocalypse Using Custom Post Types and Taxonomies.
帕特里克：是的，布拉德和我自己都将发言。 布拉德(Brad)正在发表名为“使用自定义帖子类型和分类法生存僵尸启示录”的演讲。
Louis: (Laughs)
路易斯：(笑)
Patrick: So yeah, that’s Brad’s zombie title, and then I’m talking immediately after in the same room doing Comment Moderation 2.01 which is topical for us on the podcast with some of the comments we get.
帕特里克(Patrick)：是的，那是布拉德(Brad)的僵尸头衔，然后我在同一个房间里聊天，然后做Comment Moderation 2.01，这在播客中是我们的话题，并收到了一些评论。
Louis: (Laughs) yeah, so I only checked my email this morning and saw that so that was a lot of fun. Alright so you guys ready to kick in to the news?
路易斯：(笑)是的，所以我今天早上才检查我的电子邮件，发现那很有趣。 好了，你们准备好接受新闻了吗？
Stephan: Let’s do it.
史蒂芬：开始吧。
Louis: Alright I think Stephan is up first.
路易斯：好吧，我认为斯蒂芬是第一位。
Stephan: Well, I think the big story last week and into this week has been the Amazon EC2 outage, and the risk of the cloud, and that’s the article I have, it’s from PC World and it goes into some — brings in some questions about the cloud, and then I also have a VentureBeat article that talks about exactly what happened and what the issues were. I think it’s really about their backup system is how I read it, that they didn’t have as good a backup, Amazon that is, did not have as good backups as everybody thought, and when parts of their storage network started going out there was no rollover to the backups and people lost their websites including Quora, FourSquare, Reddit, things like that. So did you guys notice any outages? I didn’t really notice much because I don’t use any of those websites, so did y’all notice anything?
史蒂芬：嗯，我认为上周和本周的大事件是Amazon EC2中断，云的风险，这是我的文章，来自PC World，涉及到一些问题。关于云的知识，然后我还有一篇VentureBeat文章，讨论发生的确切情况和问题所在。 我认为这实际上是关于他们的备份系统的阅读方式，他们没有一个很好的备份，亚马逊即没有所有人都认为的那么好备份以及他们的存储网络的某些部分开始出现时没有过渡到备份，人们失去了包括Quora，FourSquare，Reddit之类的网站。 你们有没有发现任何中断？ 我没有真正注意到太多，因为我没有使用任何这些网站，所以你们都注意到了什么吗？
Louis: I think we had a little bit of latency here at SitePoint because we do use AWS services, but it wasn’t massive; I think most of the site was still online and functioning throughout it. It was, if I’m not mistaken, the outage was sort of restricted to one region, so the AWS East and a few availability zones within that, so that was one of the interesting things about this outage is it’s the first time that they’ve had, if I’m not mistaken, the first time they’ve had an outage that affected availability zones, so even if you had that multi-AZ setup which would usually protect you against outages you would still be affected in this case.
路易斯：我认为我们在SitePoint上有一点延迟，因为我们确实使用了AWS服务，但这并不庞大。 我认为大部分站点仍处于在线状态，并且在整个过程中均正常运行。 如果我没记错的话，停机是仅限于一个区域的，所以AWS East和其中的几个可用区，所以这是一次有关停机的有趣事情，因为这是他们第一次如果我没记错的话，他们第一次出现断电会影响可用性区域，因此，即使您具有通常可以保护您免受断电影响的多可用区设置，在这种情况下，您仍然会受到影响。
Patrick: Yeah, I didn’t notice much myself, just the news stories (laughter), it’s kind of funny because I don’t know, I’m not using the right services because I don’t check in on FourSquare, I’ve kind of forgotten about Quora right now. I did use AWS for serving audio to my music blog, but I don’t even spend that much time in that feature so I didn’t notice anything about it, and it is kind of surprising to hear that Amazon maybe didn’t have the backup system they should have just because obviously Amazon if they’re not on the ball then I don’t know if any of us are.
帕特里克：是的，我自己并没有注意到太多，只是新闻报道(笑声)，这很有趣，因为我不知道，我没有使用正确的服务，因为我没有检查FourSquare，我现在已经忘记了Quora。 我确实使用AWS为音乐博客提供音频，但我什至没有花太多时间在该功能上，因此我没有注意到任何事情，听到亚马逊也许没有他们应该拥有的备份系统，只是因为很明显，如果Amazon未能如愿以偿，那么我不知道我们当中是否有人。
Louis: Yeah.
路易斯：是的。
Stephan: There was a really good article, and I’ll need to find it and post it in the show notes, but there was a really good article on SAN storage, storage in networks in general and some of the issues they face. I’ll need to find the article because it went into great detail on how when you do backups sometimes if the backups are mirrored the problem is in the backup then it gets mirrored throughout all the different areas, and so when you try to restore you’re just restoring the issue. So no one really knows if that’s what the issue was or if, you know, because it took them a long time just to get things back online, so I wish Amazon would kind of come out and say what exactly happened and hopefully they will in the next few days because it’s worrisome for people who have websites with them or are running their websites with EC2 or any of the web services.
史蒂芬：有一篇非常不错的文章，我需要找到它并将其发布在展示笔记中，但是关于SAN存储，一般网络中的存储以及它们面临的一些问题，有一篇非常好的文章。 我需要找到该文章，因为它详细介绍了如何进行备份(有时如果对备份进行了镜像)，问题出在备份中，那么它将遍及所有不同区域，因此当您尝试还原时只是恢复问题。 所以没人真正知道这是问题的根源，还是因为他们花了很长时间才使事情恢复在线，所以我希望亚马逊能出来并说出到底发生了什么，并希望他们会接下来的几天，因为这对于那些拥有网站或正在使用EC2或任何Web服务运行其网站的人来说非常令人担忧。
Louis: Yeah. There’s a couple of things that have come out in the wake of this. A number of blogs have come out and sort of said that one main article that I see linked to a lot of places is an article on the O’Reilly blogs by a guy sort of talking about designing for failure and how it’s possible to design around this kind of event and that The Cloud sort of in theory should be forcing people to think about their application architecture in a way that it’s not dependent on any one virtual resource or availability zone to keep functioning. And a number of people have pointed out either on Twitter or in blogs that one of the interesting things about this is to look not at the websites that went down like FourSquare or Reddit, but to look at the websites that didn’t go down; there’s a lot of people using AWS that were unaffected and a lot of people have pointed at Netflix as one great example of that. There’s this blog post on the Netflix blog from the end of last year, so from December of 2010, talking about — it’s called Five Lessons We’ve Learned Using AWS, and they’re talking about the way they’ve handled their infrastructure. And I guess the most interesting thing in there for me is their system called the Chaos Monkey, are you guys familiar with the Chaos Monkey?
路易斯：是的。 随之而来的是几件事。 许多博客问世，我说与很多地方相关的一篇主要文章是O'Reilly博客上的一篇文章，由一个人谈论有关为失败进行设计以及如何进行围绕设计的讨论。这种事件，并且从理论上讲，云应该迫使人们以一种不依赖任何虚拟资源或可用性区域来保持运行的方式来思考他们的应用程序体系结构。 许多人在Twitter或博客上都指出，与此有关的有趣的事情之一是，不要看那些像FourSquare或Reddit这样的失败网站，而是要看那些没有失败的网站。 有很多使用AWS的人并没有受到影响，而且很多人都将Netflix视为一个很好的例子。 去年年底，Netflix博客上有此博客文章，因此从2010年12月开始谈论-这就是我们从AWS中学到的五个教训 ，他们正在谈论他们处理基础架构的方式。 我想对我来说最有趣的是他们的系统，叫做混沌猴子，你们熟悉混沌猴子吗？
Stephan: No.
斯蒂芬：不。
Patrick: No.
帕特里克：不。
Louis: So Netflix have this system which they say is one of the first systems that their engineers built when they started using AWS, and what it does is it’s a service that will randomly kill instances and services in their architecture, so at random it will just shut down an EC2 instance or kill an S3 bucket, and they use that as sort of a testing system to make sure that their architecture can still function if stuff goes away at random.
Louis：所以Netflix拥有这个系统，他们说这是工程师在开始使用AWS时构建的第一批系统之一，它的作用是将随机杀死其架构中的实例和服务的服务，因此它将随机地只是关闭一个EC2实例或杀死一个S3存储桶，然后他们就将其用作测试系统，以确保如果杂乱无章的架构仍然可以正常运行。
Patrick: That reminds me of the old SimCity games where you could just release a tornado in the middle of a city and just pop it down there and then see what happens (laughter) then rebuild.
帕特里克(Patrick)：这让我想起了旧的《模拟城市》游戏，您可以在城市中间放出龙卷风，然后将其放到那里，然后看看会发生什么(笑声)，然后重建。
Louis: Yeah, I guess that’s kind of the idea is they’ve set it up so that, I mean they’ve figured it out from the beginning okay we’re not going to assume that this stuff is going to be there forever or everything is going to survive so let’s make sure that everything will keep working. So it’s a lot of interesting stuff both in this article on O’Reilly and that Netflix article which was published last year so it’s not in response to this outage, but it’s interesting because it sort of covers what their approach to cloud computing is and it seems to have worked for them because they didn’t suffer any downtime at all because of this outage.
路易斯：是的，我想这是他们对其进行设置的想法，我的意思是他们从一开始就想出了办法，好吧，我们不会假设这些东西会永远存在或一切都会继续下去，所以让我们确保一切都会继续运作。 因此，在O'Reilly上的这篇文章以及去年发布的Netflix文章中，都有很多有趣的内容，因此它并不是针对这种中断的响应，但是很有趣，因为它涵盖了他们的云计算方法及其似乎为他们工作了，因为他们没有因为断电而遭受任何停机。
Patrick: I noticed a funny Tweet that Louis re-Tweeted from @jckhewitt who said: “OH in the office: It turns out the cloud is actually just some place in Virginia.” (Laughter) And this is a bit ironic because it was sort of a running gag on the show with Kevin and me where we don’t trust the cloud, and now this great opportunity and Kevin’s gone, so, you know, our fears have been justified! No, I’m just kidding.
帕特里克(Patrick)：我注意到路易(Louis)从@jckhewitt发来的一条有趣的推文中说：“办公室里的OH：原来云实际上只是在弗吉尼亚州的某个地方。” (众笑)这有点讽刺，因为这与Kevin和我一起在节目中放任自流，我们不信任云，而现在这个巨大的机会和Kevin消失了，所以，你知道，我们的恐惧被证明是合理的！ 不，我只是在开玩笑。
Stephan: That’s actually what I was going to ask was are you a little more hesitant now to use the cloud, Louis and Patrick; I know Patrick you’re probably going to say definitely yes.
史蒂芬：我实际上要问的是，路易斯和帕特里克，您现在是否还在犹豫是否要使用云？ 我知道帕特里克，您可能肯定会说是的。
Patrick: I think it’s always important to have your own backups and all your own things that you control and not be totally in the cloud, you always need to have something to fall back on, a single point of any kind of failure is not a good thing.
帕特里克(Patrick)：我认为拥有自己的备份和所有自己要控制的东西而不是完全在云中始终很重要，您总是需要依靠一些东西，任何形式的故障都不是好东西
Louis: Yeah. One of the things I guess that’s interesting about this I guess is that because Amazon is so huge and because they fail so infrequently, like they haven’t had a major outage in a very long time and I guess it comes across as a big shock to everyone because everyone just sort of trusted it like it was just this thing like it was air, like it was oxygen for the Web. But I guess this might have people thinking a bit differently about the way that they build their applications or their websites around cloud services and sort of understand that the stuff can fail and you have to have I guess fail-overs in place for when and if that happens; you can’t just put your whole business on top of someone else’s service and just assume that that’s always going to be there.
路易斯：是的。 我猜想对此很有趣的一件事是，因为亚马逊如此庞大，并且因为它们很少发生故障，就像他们在很长一段时间内没有发生大故障一样，所以我认为这是一个巨大的冲击对每个人来说，因为每个人都有点像它一样信任它，就像空气，网络氧气一样。 但是我想这可能会使人们对他们围绕云服务构建应用程序或网站的方式有所不同，并理解这些东西可能会失败，并且我必须确定何时以及是否进行故障转移那个会发生; 您不能仅仅将整个业务放在别人的服务之上，而只是假设那将永远存在。
Patrick: Yeah, and maybe to exemplify that is there’s this thread on the Amazon Web Service Discussion Forums that’s got a lot of play and it picked up all over the Web about this company that is a heart monitoring company that they monitors hundreds of cardiac patients at home, and this post says that they were unable to see their ECG signals since April 21st, this post has been out April 22nd, so in other words they’re using the EC2 or the AWS servers for heart monitoring. I was very surprised when I heard that.
帕特里克(Patrick)：是的，也许可以举例说明，亚马逊网络服务讨论论坛上有这个话题，它发挥了很多作用，并且在整个网络上都涉及到这家心脏监测公司，该公司可以监测数百名心脏病患者。在家里，和这个职位说，他们无法看到，因为4月21 日他们的心电信号，这个帖子已经出4月22日第二 ，所以换句话说，他们正在使用的EC2或心脏监测的AWS服务器。 当我听到那消息时，我感到非常惊讶。
Louis: Yeah. Using the cloud in that kind of thing doesn’t strike me as weird, but it does strike me as weird that if you’re doing something that’s sort of that vital where you actually need to be monitoring people’s heart rates that you would architect in a way that has a single point of failure.
路易斯：是的。 在这种情况下使用云技术并不会给我那么奇怪，但确实会给我带来奇怪的感觉，如果您正在做的事情如此重要，那么您实际上需要监视要构建的人的心率具有单点故障的方法。
Patrick: Amazon goes down, people die, that’s the headline.
帕特里克(Patrick)：亚马逊倒下了，人们死了，这就是标题。
Stephan: So do you think we should question websites then that use — if you’re box.net and you use The Cloud services should you make that public and what your technology is, because maybe you don’t want to put your trust in that web service necessarily.
斯蒂芬：那么您认为我们应该质疑网站的使用方式吗？如果您是box.net，并且使用云服务，那么您应该公开该网站以及您使用的技术是什么，因为也许您不想信任您该Web服务。
Louis: Yeah, I guess so. I mean a lot of these sort of bigger sites that have come out and said either oh we did something wrong, so one of the good examples I think is EveryBlock which was affected by the outage, and I’ve got a quote, I think it was on an article on Wired, on the Wired Web Monkey site, Paul Smith of EveryBlock they’ve got a quote saying, “Frankly we screwed up.” “AWS explicitly advises that developers should design a site’s architecture so that it is resilient to occasional failures and outages such as what occurred yesterday and we did not follow that advice.” So in this case he’s being transparent, he’s saying, you know, so a lot of these big services have blogs run by their engineers where they talk about the details of their systems and how they design for failure and how they architect their system, and I think being transparent with that stuff especially if you’re doing stuff that’s original and you’re actually, you know, because The Cloud is really young, so I guess there are a lot of people out there who just sort of assume that it works exactly the same way as hosting worked in the past, right, so you just get a virtual server and put your stuff on it in exactly the same way as you would with a physical server. But there are companies out there that are doing I guess more interesting stuff with it, so Netflix when they come out and post these are the details of how we’ve prepared ourselves for this I think it’s important for them to come out and explain what their approaches and their strategies are, and that’s people making informed decisions as well; if they’re not saying anything then maybe that’s a clue that they’re not totally up to speed.
路易斯：是的，我想是的。 我的意思是很多这类较大的站点都已经出现，并说要么哦，我们做错了，所以我认为其中一个很好的例子是EveryBlock，该站点受到了中断的影响，我想引用一个在Wired上的一篇文章中，在Wired Web Monkey网站上，EveryBlock的Paul Smith引用了一句话，“坦白说，我们搞砸了。” “ AWS明确建议开发人员应该设计站点的架构，以使其能够应对偶然的故障和中断，例如昨天发生的事情，而我们没有遵循该建议。” 因此，在这种情况下，他是透明的，他是说，您知道，因此，许多大型服务中都有许多由工程师运营的博客，他们在博客中讨论系统的详细信息，如何设计故障以及如何设计系统，以及我认为对这些东西要透明，特别是如果您正在做的是原始的东西，而实际上您知道的话，因为The Cloud真的很年轻，所以我猜那里有很多人只是假设它对，托管服务器的工作原理与过去的托管服务器完全相同，因此，您只需获得一台虚拟服务器，然后将其放置在虚拟服务器上，就像在物理服务器上一样。 但是，有些公司正在做这些事情，我想可能会有更多有趣的事情，所以Netflix出来并发布这些内容是我们为此做好准备的细节，我认为对他们来说重要的是要解释一下他们的方法和策略都是这样，那就是人们还要做出明智的决定； 如果他们什么也没说，那可能是他们没有完全掌握速度的线索。
Patrick: And I think that the explanation of whether or not it’s needed, and also the type of explanation you provide really depends on the service that you are, so box.net for example is this file kind of hosting service, it’s about keeping your files accessible, whatever those files may be, and collaboration and sharing things in The Cloud, and that certainly is about access, that’s a key selling point is that you’ll be able to access your stuff. So for them it makes a lot of sense to say this is way your stuff will be accessible, this is why your stuff will be secure, because we do this, this, this and this, because if they didn’t say that then people would wonder well how do I know that I’ll be able to access that document when I’m in Aruba on vacation, on Friday night at 2:00 a.m. or something. So that’s part of their business, where if you look at like a Walmart for example that’s not a conversation Walmart needs to have except in the nature of security; if people want to know why is my data secure with Walmart, why is my credit card information secure with Walmart, then that will be the conversation that they might want to have explaining how and why their website is safe, but no one cares about Walmart always being up necessarily other than to get and buy their stuff as soon as possible, so the different businesses kind of dictate that explanation and what it should contain.
帕特里克：我认为是否需要它的解释以及您提供的解释的类型实际上取决于您所使用的服务，因此例如box.net就是这种文件托管服务，它与保持您的服务有关。可以访问的文件(无论这些文件可能是什么)，以及在Cloud中进行协作和共享的东西，这当然与访问有关，这是一个关键卖点，那就是您将能够访问自己的东西。 因此，对于他们来说，说这是可以访问您的东西的方式很有道理，这就是为什么您的东西将被保护的原因，因为我们这样做，这样做，这样做和这样做，因为如果他们没有说那个人我想知道我怎么知道当我在假期，星期五晚上2:00到阿鲁巴时将能够访问该文档。 因此，这是他们业务的一部分，例如，如果您看上去像沃尔玛，那不是沃尔玛需要进行的对话，除了安全性之外； 如果人们想知道为什么我的数据在Walmart上是安全的，为什么我的信用卡信息在Walmart上是安全的，那么那将是他们可能想要解释他们的网站如何安全以及为什么安全的对话，但没人会在乎Walmart除了尽早获得和购买他们的东西外，总有必要提高自己的能力，因此，不同的企业决定了这种解释及其应包含的内容。
Louis: Yeah. And I guess if you’re doing heart rate monitoring then it’s more important to get out there and explain how you’ll handle this stuff or not handle it as the case may be.
路易斯：是的。 而且我想，如果您要进行心率监测，那么走到那里并解释如何处理这些东西(视情况而定)更重要。
Patrick: Cool, so I can take the next story here, I found an article at TechCrunch that I found interesting from kind of a moderation, community, technology standpoint, the CEO of myYearbook, which is a social network, I don’t use myYearbook, do either of you guys?
帕特里克：太酷了，所以我想在这里继续讲下一个故事，我在TechCrunch上发现了一篇文章，从节制，社区，技术角度以及myYearbook的首席执行官(这是一个社交网络)的角度来看，我都觉得很有趣，我不使用myYearbook，你们两个吗？
Louis: I’ve never heard of it before now.
路易斯：我之前从未听说过。
Patrick: Okay. Well, honestly I don’t think I’ve heard of this either, but they’re serving up to 750,000 video chats per day, live video chats, and so they have run into the problem that Chatroulette ran into which is for lack of a better term seeing a lot of private parts on their live video chat (laughter). And when the service launched, when myYearbook launched their live video chat, they found that one in every ten Chatroulette video chats was obscene, so 10% of all video chats was obscene, that might even seem a little low looking back on it (laughter), but they didn’t want that on their service. So they have kind of put together this system of monitoring their video chats that’s both human and algorithmic where they capture and analyze thousands of images a second from hundreds of thousands of daily video streams, and they sample the streams at random, and they have an algorithm that is based on many factors but one of the things they found is that an image with a face in it is five times less likely to contain nudity (laughter). Which makes sense I guess, but they don’t rely on just that because 20% of images that have nudity also have a face, so they use a lot of different things, chat reputation, social graph, motion in the video and other factors, and they pair that with a human element to take care of both false negatives and images that are simply decided to be safe, so they still do sample those images those images that are considered safe so that a human can lay eyes on it and really see if it is safe or not. And how they review that content is kind of a two-tier review system where if two reviewers find your behavior to be inappropriate you’re banned from the site, and those people are on staff 24 hours a day, 7 days a week, 365 days a year, and they have the goal of reviewing streams with a delay of no more than five minutes, so I almost think it’s an interesting conversation not only for moderation but for developers who are thinking of doing anything like this, the live nature of the Web, how there is kind of a responsibility to monitor your content.
帕特里克：好的。 好吧，说实话我也没有听说过，但是他们每天提供多达750,000个视频聊天，实时视频聊天，因此他们陷入了Chat遇到的问题，因为缺乏最好在直播视频聊天中看到很多私人部分(笑声)。 当该服务启动时，当myYearbook启动实时视频聊天时，他们发现每十个聊天视频聊天中就有一个是淫秽的，因此所有视频聊天中有10％是淫秽的，往后看甚至显得有点低(笑声) )，但他们不希望自己的服务如此。 因此，他们将这种监视他们的视频聊天的系统组合在一起，既是人工的又是算法的，他们每秒从数十万个每日视频流中捕获和分析每秒数千张图像，并随机采样这些流，并且该算法基于许多因素，但他们发现的一件事是，其中带有脸部的图像包含裸露(笑声)的可能性降低了五倍。 我想这是有道理的，但他们并不仅仅因为有20％的裸露图像也有脸，所以他们使用了很多不同的东西，聊天声誉，社交图谱，视频中的动作和其他因素，并且将它们与人为因素配对以处理假阴性和被简单认为是安全的图像，因此他们仍然对那些图像进行采样，将那些被认为是安全的图像进行采样，以使人类可以真正看到看看它是否安全。 而且他们如何查看内容是一种两层式的查看系统，其中如果有两个审阅者认为您的行为不适当，那么您将被禁止访问该网站，并且这些人每天365天，每周7天，每天24小时都在工作人员中一年之内，他们的目标是不超过5分钟的延迟来审核流，因此我几乎认为这是一次有趣的对话，不仅对于主持人，而且对于正在考虑进行此类操作的开发人员来说， Web上如何监视您的内容。
Louis: Yeah, that’s pretty — it’s a big, big effort on their part. I guess not a lot of sort of startup style companies could afford to put people in front of that much video to moderate it constantly, but it’s interesting that they do have that first algorithmic layer of protection which might be really useful, I mean assuming this sort of technology becomes more common; if you’re just starting out it might be a good thing to just throw in some automatic moderation to start with and then once you get to a point where you can afford to have a person look through the — to clear out any false positives or false negatives.
路易斯：是的，这很漂亮–这对他们来说是很大的努力。 我想没有多少类型的创业公司能够承受让人们一直在视频面前不断地对其进行调节，但是有趣的是，他们确实拥有第一算法保护层，这可能真的有用，我的意思是假设某种技术变得更加普遍； 如果您只是刚开始，最好先进行一些自动审核，然后到达某个点，您可以负担得起一个人浏览-清除所有误报或假阴性。
Patrick: And just to throw some images, I mean not images —
帕特里克(Patrick)：只是要扔一些图像，我的意思不是图像-
Louis: (Laughs) I’m not sure I want to click on this link now.
路易斯：(笑)我不确定现在是否要单击此链接。
Patrick: Just to throw some data behind this just to see how successful it’s been, they sampled a Chatroulette video stream, 1500 video streams from Chatroulette recently, and they found that 1.9% of them had some form of nudity in it, so one out of 50 basically. On their service they find one in 1,000 that have it, so that’s where they have found success, they’ve been able to limit that drastically. And another interesting thing that he pointed out is that he doesn’t necessarily believe that identity, like using Facebook Connect, plays much of a role in discouraging abuse because people did this on I guess there was an iPhone app called iChatter which you could be identified through and people still did this sort of thing. So, what he believes is having any sort of login at all discourages people, what they do is they actually fingerprint the devices people use to access the site through a service called ThreatMetrix, and then when they ban someone they ban both the user and their device so that they’re unable to access the site at all. So I thought that was interesting especially with the proliferation of Facebook Connect around the Web versus having more of a site-based login and you could have a little more control over.
帕特里克(Patrick)：为了在此基础上添加一些数据，以了解它的成功程度，他们对一个聊天视频流进行了采样，最近从聊天中获得了1500个视频流，他们发现其中1.9％的视频中包含某种形式的裸体，因此基本上是50 在他们的服务中，他们发现有千分之一的人拥有它，因此这就是他们取得成功的地方，他们已经能够大幅度地限制这一点。 他指出的另一件有趣的事情是，他不一定相信身份(例如使用Facebook Connect)在阻止滥用行为方面起着很大作用，因为人们这样做是因为我猜想有一个名为iChatter的iPhone应用程序，通过识别，人们仍然做这种事情。 因此，他认为所有登录都会使人们灰心，他们实际上是在对人们用来通过ThreatMetrix服务访问该网站的设备进行指纹识别，然后当他们禁止某人时，便同时禁止了该用户及其用户。设备，使他们根本无法访问该网站。 因此，我认为这很有趣，尤其是随着Facebook Connect在网络上的普及，而不是更多基于站点的登录，您可以对此进行更多控制。
Louis: Yeah, that’s pretty interesting.
路易斯：是的，这很有趣。
Patrick: And so as a community guy, I know no one’s really interested in this story as you can probably tell, but there was one other quote that I felt was really accurate, he said that, “Based on their findings we believe purely algorithmic approaches to moderation will never provide adequate safety.” And I found that interesting because there seems to be on the Web this push to automate so many different things, and especially in moderation, but really you’re always going to need that human discretion to be able to really achieve a really strong level of safety and of guideline enforcement.
帕特里克(Patrick)：作为一个社区人士，我可能不知道您对这个故事有什么真正的兴趣，但是我认为还有另一句话确实很准确，他说：“基于他们的发现，我们认为纯粹是算法上的节制的方法永远不会提供足够的安全性。” 我发现这很有趣，因为在网络上似乎有推动这种自动化的事情，尤其是在节制方面，但实际上，您总是需要人工判断才能真正达到很高的水平。安全和准则执行。
Stephan: That ties in kind of with the login thing, right, because he says as long as people can login they can be blocked, but at the same time you can’t block people based on an algorithm. So it’s these two, you know, he’s kind of taken technology two ways, he’s saying we’re going to force you to do one thing, right, and we’re going to also have human interaction. So it seems like a great approach to get rid of the crappy crap out there (laughs).
史蒂芬：这与登录有关，对，因为他说只要人们可以登录，他们就可以被阻止，但是同时您不能基于算法来阻止人。 所以这就是这两种，您知道，他在两种方面都接受了技术，他是说我们将迫使您去做一件事情，对，而且我们还将进行人与人之间的互动。 因此，这似乎是摆脱那里糟糕的垃圾的好方法(笑)。
Patrick: Right, because no one can be banned based on the algorithm, even the people that are flagged it takes two editors to say okay, yeah, that’s that thing we don’t need to see and then you’re banned.
帕特里克(Patrick)：是的，因为没有人可以基于该算法被禁止，即使被标记的人也需要两名编辑才能说好，是的，那是我们不需要看到的东西，那么您就被禁止了。
Louis: Yeah. Well that makes sense, it’s interesting because they’re dealing with something that’s just video so it’s very black and white whether someone is showing something inappropriate in a video or they’re not, whereas when you’re dealing with comment moderation sometimes it can be hard to draw the line whether someone’s being inappropriate or being abusive, I mean it’s easy to algorithmically detect spam if it’s just gibberish with links in it, but when someone’s just kind of being a dick that can be hard; if we come up with an algorithm for detecting that I’d be very impressed.
路易斯：是的。 很有道理，这很有趣，因为他们正在处理只是视频的内容，因此无论有人在视频中显示不适当的内容还是不显示内容都是非常黑白的，而当您处理评论审核时，有时可以无论是不当行为还是辱骂行为，都很难划清界线。我的意思是，如果垃圾邮件只是带有垃圾链接，那很容易通过算法检测出垃圾邮件，但是当某人只是个笨蛋而很难的时候； 如果我们想出一种算法来检测我会留下深刻的印象。
Patrick: Right. Well there you go, that’s the next idea. I’m sure a few developers listen to this show so get to work on that.
帕特里克：对。 好了，这就是下一个想法。 我敢肯定，有一些开发人员会听这个节目，所以请继续努力。
Louis: Yeah, that’s what we need, that’s the next thing. Alright, well I’ve got a story to throw in here; it will be my first contribution to the panel so hopefully it goes well. So the story I came up with was a blog post on Smashing Magazine from just this past week, and the title is CSS3 versus CSS, a Speed Benchmark. So we hear a lot about CSS3 and a lot of times what we hear has to do with just how much fun it is for developers to be able to do this stuff that used to be harder to do, so things like rounded corners or drop shadows or text shadows or gradients or anything like that, that used to take a lot of tweaking around and playing in Photoshop that now you can do easily with CSS3, yeah, okay that’s great. But what the author of this article has done is decided to try and do an actual comparative speed test, sort of a somewhat scientific approach to this process. So he’s come up with this fairly straightforward design for a one-page site, and he’s coded it up first of all using CSS3 so using new techniques like border-radius and box-shadow, and then he’s gone through and coded up the entire site again for the exact same look but using more traditional techniques, so using background images to fake rounded corners or fake drop shadows. And what he’s done is he’s come up with comparisons both in the time it took to code and on the load time of the two sites, and the results are pretty impressive. So first of all when he codes the site in CSS3 it takes 49 minutes to design up his site using CSS3, and using CSS, the regular image based method just takes 73 minutes, so it’s about 30% faster. And then to do with the file size there’s also a difference where CSS3 total file size download is about 10% smaller and about 45% fewer HTTP requests required because you don’t have all those little separate background images for the corners and such. And the results in terms of the load time, the CSS version loads in 3.3 seconds and the plain CSS version loads in 4.7 seconds, so above and beyond what we’re used to thinking about in terms of the advantages of CSS3 being it’s more fun to work with there’s also some really, really practical advantages in terms of page speed.
路易斯：是的，这就是我们所需要的，这是接下来的事情。 好吧，我这里有个故事要讲。 这将是我对小组的第一项贡献，因此希望一切顺利。 因此，我想出的故事是上个星期在Smashing Magazine上的博客文章，标题是CSS3 vs CSS，Speed Benchmark 。 因此，我们听到了很多关于CSS3的信息，而且很多时候我们听到的信息与开发人员能够做些以前很难做的事情对他们有多大的乐趣有关，例如圆角或阴影或文本阴影或渐变之类的东西，这些东西过去经常需要在Photoshop中进行调整和播放，现在您可以轻松地使用CSS3做到了，是的，这很好。 但是，本文的作者决定尝试进行实际的比较速度测试，这是对该过程的某种科学方法。 因此，他想出了一个非常简单的单页网站设计，他首先使用CSS3将其编码，因此使用了诸如border-radius和box-shadow之类的新技术，然后他遍历了整个网站并进行了编码再次使用完全相同的外观，但使用了更多传统技术，因此使用背景图像伪造圆角或伪造阴影。 他所做的是，他在代码编写时间和两个站点的加载时间上都进行了比较，结果令人印象深刻。 因此，首先，当他使用CSS3对网站进行编码时，使用CSS3来设计网站需要49分钟，而使用CSS时，基于图像的常规方法仅需73分钟，因此速度要快30％。 然后，要处理文件大小，还存在一个差异，即CSS3的文件总下载量要小大约10％，所需的HTTP请求则要少大约45％，因为您在拐角处并不需要所有那些单独的背景图像。 结果是在加载时间方面，CSS版本的加载时间为3.3秒，普通CSS版本的加载时间为4.7秒，因此，除了我们习惯于考虑CSS3的优势之外，它比以往更加有趣就页面速度而言，使用它还具有一些非常非常实用的优势。
Patrick: That’s pretty impressive across the board.
帕特里克(Patrick)：整个方面都给人留下深刻的印象。
Stephan: The speed differences in development time are huge and speed differences for load time are somewhat smaller and you’d think that it really scales, I mean I wish this was done on a bigger scale I guess, because it seems like it’s very limited and it would be negligible to a person loading the page, you know what I mean?
斯蒂芬：开发时间的速度差异很大，加载时间的速度差异较小，您会认为它确实可以扩展，我的意思是我希望这样做是在更大的范围内完成的，因为这似乎非常有限对加载页面的人来说可以忽略不计，您知道我的意思吗？
Patrick: Will they notice these fewer requests and fewer size, I don’t know, I’d have to see the browser studies, but I wouldn’t think that, you know, it’s probably one of those split second type of deals where only people who are hyper-aware of it would notice; you think that’s fair?
帕特里克：他们会注意到请求量减少，请求量减少吗？我不知道，我不得不看浏览器的研究，但是我不认为这可能是第二类交易中的一种只有非常了解它的人才会注意到； 你认为这很公平吗？
Louis: There’s an impact; so the article links to another article on Steve Souders’ webpage where he’s talking about the impact of performance optimizations like this on sort of traffic because you just get fewer bounces and a few extra clicks, so he’s got some statistics from search engines who did some studies on this. So if you look for example Yahoo did a study where they found a 400 millisecond slowdown resulted in a 5 to 9% drop in full page traffic. Shopzilla did a study, well, they optimized their site, they sped up their site by five seconds, increased their conversion rate by between 7 and 12%, Mozilla shaving 2.2 seconds off their landing pages increased downloading conversions by over 15%. So there is some data out there that would seem to indicate that these what seems like small differences, and it seems like if you’re trying to see okay which one loads faster and I load them both in my browser and they kind of look the same, like it’s a difference between what is this about 3 ½ seconds versus 4 ½ seconds for these two versions of the site? But the data seems to show that even those differences that can seem imperceptible to you will still affect the way you interact with the site even if it’s on a maybe not fully conscious level.
路易斯：有影响。 因此，该文章链接到了史蒂夫·索德斯(Steve Souders)网页上的另一篇文章，他在此谈论诸如此类的性能优化对流量的影响，因为您得到的跳动和点击次数较少，因此他从搜索引擎中获得了一些统计信息，这些人做了一些对此进行研究。 因此，例如，如果您查看Yahoo进行的一项研究，他们发现400毫秒的速度下降导致整页流量下降了5％至9％。 Shopzilla进行了一项研究，很好，他们优化了网站，加快了网站速度5秒钟，将转化率提高了7％至12％，Mozilla将登陆页面缩短了2.2秒，从而将下载转化率提高了15％以上。 因此，有一些数据似乎表明这些差异似乎很小，并且，如果您尝试查看可以加载的更快，并且我将它们同时加载到浏览器中，它们看起来像相同，就像这两个网站版本的大约3½秒与4½秒之间有什么区别？ 但是数据似乎表明，即使您看似无法察觉的那些差异也仍然会影响您与网站的交互方式，即使它可能不是完全有意识的。
Patrick: Yeah, and I mean three to five seconds is actually a pretty sizable amount, and maybe the answer is that maybe this changes or these changes won’t necessarily push you three to five seconds, but if you’re starting to optimize your pages then they can definitely be a part of that speeding up process.
帕特里克：是的，我的意思是说三到五秒钟实际上是相当大的一笔，也许答案是，也许这种变化或这些变化不一定会把你推到三到五秒钟，但是如果你开始优化自己的页面，那么它们绝对可以成为加速过程的一部分。
Louis: Yeah I guess it’s also fair to point out this is a fairly simple website, it’s a one-page thing, it’s got a few images on it, most of the weight comes from this one big — so it’s a sample website for Mercury automobiles, it’s got this very retro 50’s look to it. But most of the weight of the page comes from this one big honking car image in the center of the page, so you know tweaking a couple of rounded corners here and there or a button image that you don’t need to load in CSS3 because you’ve got gradients and rounded corners, it’s pretty minor, but if you had a bigger page that was using a lot of these different elements here and there you might see a bigger result.
路易斯：是的，我想指出这是一个相当简单的网站也很公平，这是一页纸的事情，上面有几张图片，大部分的重量都来自这个大网站，所以这是Mercury的示例网站汽车，它具有这种非常复古的50年代外观。 但是页面的大部分重量来自页面中央的一个巨大的鸣喇叭汽车图像，因此您知道在此处和那里调整了几个圆角或不需要在CSS3中加载的按钮图像，因为您有渐变和圆角，这是相当小的，但是如果您有一个更大的页面，并且在此使用很多这些不同的元素，那么您可能会看到更大的结果。
Patrick: Another story that crossed my browsing ritual I guess you could say is the launch of Facebook Send, now you can’t actually add a Facebook Send button to your webpage, not yet, there is a limited pool of about 50 sites that are participating with this feature but essentially what it is, is it’s just like the light button except it says send, first and foremost, and also it kind of gives you the ability to send to a specific group of people, a specific person on Facebook or a specific email address. So it’s just like if you were sharing a link or sending a message to people on Facebook, you know how you can type someone’s name and it will fill in the rest, you can type a group you’re a member of on Facebook and it will fill in the rest, that’s essentially what this feature allows you to do. Think of it as email to friend but more powerful where you can send to people on Facebook and also send to email addresses and share a link with them and also use the Facebook platform. I don’t know how successful email to friend features really still are these days; does SitePoint still have an email to friend feature, Louis, on the articles?
帕特里克：另一个与我的浏览习惯相冲突的故事，我想你可以说是Facebook Send的推出，现在您实际上无法向您的网页添加Facebook Send按钮，但是，目前只有大约50个网站是有限的参与此功能，但实际上是什么，它就像指示灯按钮一样，只不过它首先说要发送，而且还使您能够发送给特定人群，Facebook上的特定人员或特定的电子邮件地址。 因此，就像您在Facebook上共享链接或向他人发送消息时，您知道如何键入某人的姓名并将其填充其余部分，您可以键入您在Facebook上的成员的群组，将填充其余部分，这基本上就是您可以使用此功能执行的操作。 将其视为发送给朋友的电子邮件，但功能更强大，您可以在其中向Facebook上的人发送邮件，还可以发送到电子邮件地址并与他们共享链接，还可以使用Facebook平台。 我不知道最近这些天给朋友功能发送电子邮件的效果如何。 文章中，SitePoint是否仍然有“电子邮件给朋友”功能路易斯？
Louis: Great question, I don’t even know the answer to that question. We did a fairly recent redesign of blogs so I don’t actually know, I can try and pull that up and see.
路易斯：好问题，我什至不知道该问题的答案。 我们最近对博客进行了重新设计，所以我实际上并不知道，我可以尝试一下并进行观察。
Patrick: Yeah, the sharing images as far as I can see are just Facebook and the like button, the Tweet button and then the ShareThis icon.
帕特里克(Patrick)：是的，据我所知，共享图像只是Facebook和点赞按钮，Tweet按钮，然后是ShareThis图标。
Louis: Yeah, I think it’s possible that the ShareThis has an option for email, so it might still be there. Yeah, but I guess email this is pretty common on sort of mainstream news sites, you see it a lot, and I think for those types of sites it’s probably pretty common because a lot of people are at work and they may have for example Facebook blocked, but if they want to send around a link they can just use an email link. But I think it will definitely see some uptake because everybody loves Facebook, right?
路易斯：是的，我认为ShareThis可能有一个电子邮件选项，因此它可能仍然存在。 是的，但是我想在主流新闻网站上通过电子邮件发送电子邮件是很常见的，您会看到很多，而且我认为对于那些类型的网站，这可能很常见，因为很多人在工作，例如Facebook被阻止，但是如果他们想发送链接，则可以使用电子邮件链接。 但是我认为它肯定会有所普及，因为每个人都喜欢Facebook，对吗？
Patrick: Right. And the thing about it though that I noticed when I look at the two icons next to each other on this article is the Facebook like icon which just allows you to like a story on your Facebook wall, so that’s kind of the difference between the two, but it has the Facebook icon on it which may seem simple but that goes a long way toward getting people to actually click that button, because they’re on Facebook they know what Facebook is. The Send button just has like a little talk box, talk bubble I should say, in it where it looks like someone’s saying something like it’s a chat or a comment page almost, not necessarily send which might be more tied to email, an email icon, or a message, an envelope, so I don’t know if that’s going to hurt it just from a design perspective, but I guess it will be interesting as people play with it to learn how effective it is.
帕特里克：对。 而且，尽管我在这篇文章中看到彼此相邻的两个图标时注意到的是Facebook like图标，它只允许您喜欢Facebook墙上的一个故事，所以这就是两者之间的区别，但是上面带有Facebook图标，这看似简单，但对于让人们实际单击该按钮有很大帮助，因为他们在Facebook上就知道Facebook是什么。 “发送”按钮就像一个小的对话框，我应该说的是对话气泡，在该对话框中，好像有人在说类似聊天或评论页面之类的东西，不一定要发送，而发送可能与电子邮件，电子邮件图标更多相关或一条消息，一个信封，所以我不知道这是否会从设计的角度来伤害它，但是我想随着人们使用它来学习它的有效性，它会很有趣。
Louis: Yeah, that seems like something that they might wind up changing down the line because I think for someone who’s a Facebook user, and I’m not really a heavy Facebook user, I have a page but I don’t really use it, for someone who is a Facebook user it kind of makes sense; you see that Facebook icon and you’re like oh I can post this to my Facebook and I just hit like and now I don’t even have to think about it. But when it’s something like Send unless they do — unless Facebook does a sort of campaign to make their users more aware of this I don’t see how people would really tap into it and say, oh, that’s a way to send to people on Facebook.
路易斯：是的，似乎他们可能会改变思路，因为我认为对于一个Facebook用户来说，我并不是一个沉重的Facebook用户，我拥有一个页面，但我并没有真正使用它，对于使用Facebook的用户来说，这很有道理； 您会看到该Facebook图标，并且您就像哦，我可以将其发布到我的Facebook，然后按一下即可，现在我什至不必考虑它。 但是当它像“发送”时，除非他们这样做-除非Facebook进行某种运动以使用户更加意识到这一点，否则我看不出人们会如何真正地利用它并说，哦，这是一种发送给用户的方式脸书
Patrick: Yeah, so it’s almost like it’s going to take some time to catch on. I don’t know if I see this catching on as quickly as the like button.
帕特里克：是的，所以几乎要花一些时间才能赶上。 我不知道我是否能像“赞”按钮那样Swift流行。
Louis: Yeah. I can see the appeal from the point of view of web developers or people who run sites, especially if you previously have your own email to friend feature, and that takes time to develop, and if this can do email as well as sending Facebook messages then it sort of gives you that functionality for free even if people aren’t Facebook users. Does it work if you’re not signed in to Facebook, can you send it to — can you use the email functionality even if you don’t have a Facebook account, do you know that?
路易斯：是的。 从Web开发人员或运行网站的人的角度来看，我可以看到这种吸引力，尤其是如果您以前拥有自己的电子邮件给朋友功能，并且花了一些时间进行开发，并且这既可以发送电子邮件又可以发送Facebook消息，则尤其如此。 then it sort of gives you that functionality for free even if people aren't Facebook users. Does it work if you're not signed in to Facebook, can you send it to — can you use the email functionality even if you don't have a Facebook account, do you know that?
Patrick: That is a great question, and no I don’t think I do know that because I don’t know a whole lot of information available about it right now. The article at TechCrunch by Jason Kincaid says that you can share obviously to an email address but do you have to be signed in to Facebook, and I’m going to speculate here, total speculation on my part, that they will allow you to do that. I don’t know for sure but it’s easy enough where you type in an email address here and they can allow you to send it, now on the other hand, on the other hand I’m going to contradict myself, maybe not, because maybe being logged into Facebook is sort of even a spam prevention mechanism where they can tell, hey, you Stephan Segraves, you are logged in and you emailed this person, they reported that as spam so now you’re in trouble with us, that sort of thing, whereas if it’s just an unrestricted thing obviously that presents sort of a privacy, security type of issue.
Patrick: That is a great question, and no I don't think I do know that because I don't know a whole lot of information available about it right now. The article at TechCrunch by Jason Kincaid says that you can share obviously to an email address but do you have to be signed in to Facebook, and I'm going to speculate here, total speculation on my part, that they will allow you to do that. I don't know for sure but it's easy enough where you type in an email address here and they can allow you to send it, now on the other hand, on the other hand I'm going to contradict myself, maybe not, because maybe being logged into Facebook is sort of even a spam prevention mechanism where they can tell, hey, you Stephan Segraves, you are logged in and you emailed this person, they reported that as spam so now you're in trouble with us, that sort of thing, whereas if it's just an unrestricted thing obviously that presents sort of a privacy, security type of issue.
Louis: Yeah. I think it’s interesting in both senses. Like if they do let you use it just to email then that could sort of speed up adoption by site owners because it gives you that email to friend feature for free and you don’t really have to develop it yourself or do anything other than pop this Facebook thing. But on the other hand it seems like that’s not in Facebook’s interest, so in their interest they want everyone to be logged into the Facebook ecosystem all the time, so they might sort of pop you a prompt if someone clicks on send a friend, oh you can send this to your friend you just have to login to Facebook first which seems like what the approach they might more likely to take.
路易斯：是的。 I think it's interesting in both senses. Like if they do let you use it just to email then that could sort of speed up adoption by site owners because it gives you that email to friend feature for free and you don't really have to develop it yourself or do anything other than pop this Facebook thing. But on the other hand it seems like that's not in Facebook's interest, so in their interest they want everyone to be logged into the Facebook ecosystem all the time, so they might sort of pop you a prompt if someone clicks on send a friend, oh you can send this to your friend you just have to login to Facebook first which seems like what the approach they might more likely to take.
Patrick: Yeah, and actually you know what I’m going to test that right now. Let me log out of Facebook, I’m logging out right now and I’m on an Orbitz page which is one of the pages they have, refreshing it, so let me see if I can; I’m going to guess I can but let’s see. I’m logged out of Facebook, I press send and it wants me to login so there’s your answer, no you can’t send it without being logged in.
Patrick: Yeah, and actually you know what I'm going to test that right now. Let me log out of Facebook, I'm logging out right now and I'm on an Orbitz page which is one of the pages they have, refreshing it, so let me see if I can; I'm going to guess I can but let's see. I'm logged out of Facebook, I press send and it wants me to login so there's your answer, no you can't send it without being logged in.
Louis: Well I guess that’s interesting right, and we struggle with this here at SitePoint, you know whenever we do a new page or a new promotion or something we have to, you know, on the one hand you get a lot of uplift from those Facebook integration features, like when we did our December sale last year our whole comment system for the thing was powered by Facebook comments and it generated a lot of uplift, but on the other hand you want to be careful and not tie your whole thing too tightly in with these services, so it’s kind of a bit of a tightrope.
Louis: Well I guess that's interesting right, and we struggle with this here at SitePoint, you know whenever we do a new page or a new promotion or something we have to, you know, on the one hand you get a lot of uplift from those Facebook integration features, like when we did our December sale last year our whole comment system for the thing was powered by Facebook comments and it generated a lot of uplift, but on the other hand you want to be careful and not tie your whole thing too tightly in with these services, so it's kind of a bit of a tightrope.
Patrick: Yeah you don’t want to give them too much power over you or you end up with Google which we don’t want. No, I’m just kidding.
Patrick: Yeah you don't want to give them too much power over you or you end up with Google which we don't want. 不，我只是在开玩笑。
Louis: Yep, definitely interesting but I don’t think it’ll stop our concerns about these, I think we’re definitely in a minority with regards to this stuff. I always find myself this handwringing about oh Facebook’s taking over the Web or Twitter’s taking over the Web or whatever and nobody cares, they’ll still do it.
Louis: Yep, definitely interesting but I don't think it'll stop our concerns about these, I think we're definitely in a minority with regards to this stuff. I always find myself this handwringing about oh Facebook's taking over the Web or Twitter's taking over the Web or whatever and nobody cares, they'll still do it.
Patrick: Yeah, then you realize it’s really to .0001% of people that actually really care about those types of things, the rest don’t know what a search engine is, so yeah.
Patrick: Yeah, then you realize it's really to .0001% of people that actually really care about those types of things, the rest don't know what a search engine is, so yeah.
Louis: (Laughs) yep, so they’ll just keep clicking those like buttons and maybe those send buttons. Although I do think that that’s — the absence of the Facebook logo is a really interesting one, but maybe who knows, maybe they’ll get to the point where they can assert trademark over the word send.
Louis: (Laughs) yep, so they'll just keep clicking those like buttons and maybe those send buttons. Although I do think that that's — the absence of the Facebook logo is a really interesting one, but maybe who knows, maybe they'll get to the point where they can assert trademark over the word send.
Patrick: Yeah or maybe they’ll just use a little envelope with a very small Facebook button on it, maybe that’s the solution.
Patrick: Yeah or maybe they'll just use a little envelope with a very small Facebook button on it, maybe that's the solution.
Louis: So one more story this week that I found I think was just this morning, The jQuery team announced the release of the beta version of jQuery 1.6 so that’s of course interesting to just about everyone who does web development because just about everyone uses jQuery these days. Looking over the changelog really quickly it’s notable that this is probably the first release, or the first beta release of jQuery that hasn’t included any really show-stopping features, most of what’s on the changelog there is really just performance enhancements or bug fixes to do with specific browsers behaving in different ways and they’ve cleaned things out a little bit and rewritten a few methods for consistency, but overall I’m not seeing anything really major in that so obviously it’s good news for developers because it’s always good to have new versions of this stuff, but maybe jQuery’s just reaching the point where it’s so mature that there’s nothing really significant that needs to be added to it and it’s just all about fine-tuning from on out.
Louis: So one more story this week that I found I think was just this morning, The jQuery team announced the release of the beta version of jQuery 1.6 so that's of course interesting to just about everyone who does web development because just about everyone uses jQuery these days. Looking over the changelog really quickly it's notable that this is probably the first release, or the first beta release of jQuery that hasn't included any really show-stopping features, most of what's on the changelog there is really just performance enhancements or bug fixes to do with specific browsers behaving in different ways and they've cleaned things out a little bit and rewritten a few methods for consistency, but overall I'm not seeing anything really major in that so obviously it's good news for developers because it's always good to have new versions of this stuff, but maybe jQuery's just reaching the point where it's so mature that there's nothing really significant that needs to be added to it and it's just all about fine-tuning from on out.
Patrick: And there’s a disappointed kind of expression in your tone there, but it’s not a bad thing is it that it’s so mature?
Patrick: And there's a disappointed kind of expression in your tone there, but it's not a bad thing is it that it's so mature?
Louis: No, it’s not.
Louis: No, it's not.
Patrick: There’s no new features in this thing! It’s turned into IE6.
Patrick: There's no new features in this thing! It's turned into IE6.
Louis: (Laughs) man, that’s gonna bring on some fierce commenting. Yeah, jQuery’s the new IE6, let’s make that the title of the show and see how that goes over (laughter). But yeah I guess you always kind of want cool new toys, right, and if your toy has gotten to the point where it does everything you can think of wanting it to do and there’s nothing really to add other than to make it a little bit shinier and a little bit faster it’s a little bit less of a Christmas morning feel when you unwrap the new version of jQuery, right?
Louis: (Laughs) man, that's gonna bring on some fierce commenting. Yeah, jQuery's the new IE6, let's make that the title of the show and see how that goes over (laughter). But yeah I guess you always kind of want cool new toys, right, and if your toy has gotten to the point where it does everything you can think of wanting it to do and there's nothing really to add other than to make it a little bit shinier and a little bit faster it's a little bit less of a Christmas morning feel when you unwrap the new version of jQuery, right?
Patrick: Yeah it’s more like a day after Christmas.
Patrick: Yeah it's more like a day after Christmas.
Louis: Yeah, there’s leftovers in the fridge. Alright, well I think that’s a wrap for the news this week, so I guess we can move straight on to the host spotlights, Stephan do you want to start us off?
Louis: Yeah, there's leftovers in the fridge. Alright, well I think that's a wrap for the news this week, so I guess we can move straight on to the host spotlights, Stephan do you want to start us off?
Stephan: Sure, so here in Houston we have a university called Rice, it’s a really large school and a very well known school in the state, and these guys are doing some cool stuff to extend Wi-Fi up to a mile using empty TV channels, and so there’s an interesting article on Ars Technica about exactly what they’re doing and how they’re doing it, and basically they’re tapping into TV antennae and using them to broadcast a Wi-Fi signal over great distances. So we have a free Internet service here in Houston called Technology for All, and some people live on the outskirts of it and these guys have figured out a way to extend the range of their signal stronger, so very cool stuff.
Stephan: Sure, so here in Houston we have a university called Rice, it's a really large school and a very well known school in the state, and these guys are doing some cool stuff to extend Wi-Fi up to a mile using empty TV channels, and so there's an interesting article on Ars Technica about exactly what they're doing and how they're doing it, and basically they're tapping into TV antennae and using them to broadcast a Wi-Fi signal over great distances. So we have a free Internet service here in Houston called Technology for All, and some people live on the outskirts of it and these guys have figured out a way to extend the range of their signal stronger, so very cool stuff.
Louis: Hmm, that’s really interesting. It’s surprising that you’d think that at that point maybe, I don’t know anything about radio tech, bit of a disclaimer here, but you would think that at that point the limitation would be the antennae in your device, right, not the base station, but my phone or my computer still has to send data back to that base station so, you know, I guess I’m curious as to know how that works.
Louis: Hmm, that's really interesting. It's surprising that you'd think that at that point maybe, I don't know anything about radio tech, bit of a disclaimer here, but you would think that at that point the limitation would be the antennae in your device, right, not the base station, but my phone or my computer still has to send data back to that base station so, you know, I guess I'm curious as to know how that works.
Stephan: Well they’re doing it both ways, so the TV station that they use then ties in at that TV broadcasting tower into the WiFi network directly so they’re actually hardlined into the Wi-Fi network at the TV towers, so that’s actually probably what’s making it a little bit faster too.
Stephan: Well they're doing it both ways, so the TV station that they use then ties in at that TV broadcasting tower into the WiFi network directly so they're actually hardlined into the Wi-Fi network at the TV towers, so that's actually probably what's making it a little bit faster too.
Louis: Yeah, definitely. We can maybe look forward to improved public Wi-Fi in the future.
Louis: Yeah, definitely. We can maybe look forward to improved public Wi-Fi in the future.
Patrick: So my spotlight is New Media Accelerator, that’s newmeconference.com, New Media Accelerator is an accelerator for startups aimed at minority led startups, and they are going to house their conference this summer in San Francisco. One of the people behind it is my friend and friend of the show, been a guest a couple of times, Wayne Sutton, who’s always working hard to encourage diversity in the tech space where it’s much needed, and it’s just a really cool event out there for any startups that are led by a minority you should definitely check it out and go out there and present your startup and then work with their speakers and mentors, I think it’s a great opportunity.
Patrick: So my spotlight is New Media Accelerator, that's newmeconference.com, New Media Accelerator is an accelerator for startups aimed at minority led startups, and they are going to house their conference this summer in San Francisco. One of the people behind it is my friend and friend of the show, been a guest a couple of times, Wayne Sutton, who's always working hard to encourage diversity in the tech space where it's much needed, and it's just a really cool event out there for any startups that are led by a minority you should definitely check it out and go out there and present your startup and then work with their speakers and mentors, I think it's a great opportunity.
Louis: Yeah, it’s great to see people doing kind of innovative things to mix things up in the tech world which is, it’s surprising to think of tech startups as being kind of sort of this stagnant area, but sometimes it does feel that way and sometimes it feels like you need a bit of fresh air and this kind of thing is great for that. Awesome. Alright, my spotlight is a post that was written by Alex Walker who is our in-house designer here at SitePoint, he wrote a post a couple weeks ago that many people might have seen, but in case you didn’t it’s called the Cicada Principle and Why it Matters to Web Design, and what it is is basically this technique that Alex came up with using multiple background images, so kind of circling back around to the CSS3 thing, so CSS3 let’s you set multiple backgrounds on a single element. And what he’s done is using semi-transparent PNG images with widths that are prime numbers, I realize this is getting kind of complicated, but that way you can create these repeating tile backgrounds that really don’t look like they’re repeating because you’ve got this base layer that’s say 17 pixels wide and a layer on top of it that’s 13 pixels wide, and because those never fall into sync you can create these seamless tile backgrounds that seem to go on forever where you don’t notice a pattern. Because we’ve all had this experience where you’re on a website and you’re looking at the background and it’s a tiled background and you can kind of see, you can see the pattern repeating, right, you can see where the tile is and where you’re seeing the exact same thing over again. And there’s a couple of cool examples up there of backgrounds that he’s made and they’re really impressive because they really do look like they’re seamless and they can be done with not a lot of kilobyte weight in images because they’re all individually very small images. So, yeah, that’s my spotlight and they’re currently running I think a little bit of a competition if people want to try and submit their own there’s a bit of a contest going and some prize for that, so worth checking out.
Louis: Yeah, it's great to see people doing kind of innovative things to mix things up in the tech world which is, it's surprising to think of tech startups as being kind of sort of this stagnant area, but sometimes it does feel that way and sometimes it feels like you need a bit of fresh air and this kind of thing is great for that. 太棒了 Alright, my spotlight is a post that was written by Alex Walker who is our in-house designer here at SitePoint, he wrote a post a couple weeks ago that many people might have seen, but in case you didn't it's called the Cicada Principle and Why it Matters to Web Design, and what it is is basically this technique that Alex came up with using multiple background images, so kind of circling back around to the CSS3 thing, so CSS3 let's you set multiple backgrounds on a single element. And what he's done is using semi-transparent PNG images with widths that are prime numbers, I realize this is getting kind of complicated, but that way you can create these repeating tile backgrounds that really don't look like they're repeating because you've got this base layer that's say 17 pixels wide and a layer on top of it that's 13 pixels wide, and because those never fall into sync you can create these seamless tile backgrounds that seem to go on forever where you don't notice a pattern. Because we've all had this experience where you're on a website and you're looking at the background and it's a tiled background and you can kind of see, you can see the pattern repeating, right, you can see where the tile is and where you're seeing the exact same thing over again. And there's a couple of cool examples up there of backgrounds that he's made and they're really impressive because they really do look like they're seamless and they can be done with not a lot of kilobyte weight in images because they're all individually very small images. So, yeah, that's my spotlight and they're currently running I think a little bit of a competition if people want to try and submit their own there's a bit of a contest going and some prize for that, so worth checking out.
Louis: So that’s a wrap for the stories and the spotlights this week, do we want to go just quickly around the table.
Louis: So that's a wrap for the stories and the spotlights this week, do we want to go just quickly around the table.
Patrick: Absolutely, but first applause for your first episode (laughter). Oh, my God, wait a minute, redo, redo! I’m sorry. I said Lewis again.
Patrick: Absolutely, but first applause for your first episode (laughter). Oh, my God, wait a minute, redo, redo! 对不起。 I said Lewis again.
Louis: I survived! (Laughter)
Louis: I survived! (笑声)
Patrick: But first I just wanted to say great job, Louis, on your first show, it’s great to have you on board, yeah, get through those nerves and we’ll work through it, right?
Patrick: But first I just wanted to say great job, Louis, on your first show, it's great to have you on board, yeah, get through those nerves and we'll work through it, right?
Louis: Yeah, appreciate it.
Louis: Yeah, appreciate it.
Patrick: Good job, Louis, it’s great to have you on the show. My name is Patrick O’Keefe of the iFroggy Network, you can find me on Twitter@ifroggy, i-f-r-o-g-g-y.
Patrick: Good job, Louis, it's great to have you on the show. My name is Patrick O'Keefe of the iFroggy Network, you can find me on Twitter@ifroggy, ifroggy.
Stephan: I’m Stephan Segraves, you can find me on Twitter@ssegraves and my blog is badice.com.
Stephan: I'm Stephan Segraves, you can find me on Twitter@ssegraves and my blog is badice.com.
Theme music by Mike Mella.
Mike Mella的主题音乐。
Thanks for listening! Feel free to let us know how we’re doing, or to continue the discussion, using the comments field below.
谢谢收听！ 欢迎使用下面的评论字段让我们知道我们的状况，或者继续讨论。
翻译自: https://www.sitepoint.com/podcast-110-louis-first-show/
559
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
