当前位置: 首页 > 编程日记 > 正文

应用程序启动器 标记为信任_为什么您今天不能信任应用程序-以及如何解决它...

应用程序启动器 标记为信任

亲爱的每家高科技公司,请窃取这个想法 (Dear Every Single Tech Company, Please Steal This Idea)

When you send a photo to someone, your messaging app actually first sends the photo to an app’s server, which then sends the photo to them:

当您将照片发送给某人时,您的消息传递应用程序实际上首先将照片发送至应用程序的服务器,然后服务器将该照片发送给他们:

And sure, in the 90’s, when the internet was just starting to get big, this might have been what happened. But somewhere along the line, someone figured out how to profit from user data, and so now here’s what actually happens:

可以肯定的是,在90年代,当互联网刚刚开始蓬勃发展时,可能就是这种情况。 但是沿线的某个地方,有人想出了如何从用户数据中获利的方法,所以现在这是实际发生的情况:

And that’s just sending one photo. In 2019, you give apps access to your camera, location, microphone, contacts, browsing habits, even your medical records. After you tap “Allow” once, an app can even upload your entire photo and video library to their servers in the background while you’re sleeping.

那只是发送一张照片。 在2019年,您可以让应用访问您的相机,位置,麦克风,联系人,浏览习惯,甚至您的病历。 一次点击“允许”后,一个应用甚至可以在您睡觉时将整个照片和视频库上传到后台的服务器中。

The Internet is facilitating an insane free-for-all for our personal data, with potential consequences getting worse. Apps even exploit this data with behavioral science to squeeze every dollar or minute out of their users, when it’s clearly against the users’ best interests. Today, companies have every incentive to exploit our data for profit, and no incentive to protect our privacy.

互联网为 我们的 个人 数据提供了疯狂的 免费服务 ,潜在的后果越来越严重 。 当明显违反用户的最大利益时,应用程序甚至通过行为科学来利用这些数据,从他们的用户中榨取每一美元或每一分钟 。 如今,公司有各种动机来利用我们的数据牟利,而没有动机来保护我们的隐私。

Since we’re only going to rely more on apps over time, the critical question is:

由于随着时间的推移,我们只会更多地依赖应用程序,因此关键问题是:

您如何知道是否可以信任应用程序? (How do you know if you can trust an app?)

通过隐私政策信任 (Trust Through Privacy Policy)

When you ask a company about protecting your data, they respond by telling you to read their Privacy Policy, which is a document they wrote (or copy-pasted) that promises they’ll protect your data.

当您向一家公司询问有关保护数据的问题时,他们会通过告诉您阅读其隐私权政策(该政策是他们编写(或复制粘贴 )的)来承诺会保护您的数据。

But wait, isn’t that circular logic? I should trust that they’re protecting my data because… they have a document that says they’ll protect my data? How do I know they’re doing any of the things they claim in the Privacy Policy?

但是,等等,这不是循环逻辑吗? 我应该相信他们正在保护我的数据,因为……他们有一份文件说将会保护我的数据? 我怎么知道他们在做他们在隐私政策中声明的任何事情?

It turns out it’s impossible to know if an app company is violating their Privacy Policy (or violating privacy regulations in general), because there’s literally nothing stopping them: they’re Privacy Policies, not Privacy Proofs. Not only that, they're not actually legally binding, and in the rare cases when companies actually do get caught, the penalties are unbelievably light. And as recent government (in)action on data breaches, ISP privacy rules, and net neutrality show, often there are no penalties at all.

事实证明,不可能知道应用程序公司是否违反了其隐私政策(或总体上违反了隐私法规),因为实际上没有什么可以阻止它们:它们是隐私政策 ,而不是隐私证明 。 不仅如此,他们实际上并不具有法律约束力 ,并在当企业其实陷入了罕见的情况下, 该 处罚 是 令人难以置信的光 。 正如最近政府对数据泄露 , ISP隐私规则和网络中立采取的行动所显示的那样,通常根本没有任何处罚。

Privacy Polices and regulations do not create real trust, and they only serve to provide a false sense of security or privacy.

隐私警察和法规不会建立真正的信任,它们只会提供虚假的安全感或隐私感。

通过定价信任 (Trust Through Pricing)

It’s a common saying on the internet: “If the product is free, then you’re the product.” And while that’s sometimes true since revenue must come from somewhere, some people make the logical fallacy of thinking the inverse must also be true: “If the product is not free, then you’re not the product.”

互联网上有一句俗语:“如果产品是免费的,那么您就是产品。” 尽管有时这是正确的,因为收入一定来自某个地方,但有些人认为相反的逻辑也必须成立,这在逻辑上是谬论 :“如果产品不是免费的,那么您就不是产品。”

Due to this mistake, some people use price as a criterion when choosing apps to use, by looking for apps that aren’t free and making the false assumption that non-free products will not exploit their data for profit.

由于这个错误,某些人会在选择要使用的应用程序时使用价格作为标准,方法是查找非免费的应用程序,并错误地假设非免费产品不会利用其数据牟利。

Of course, it’s very possible and just as likely for a company to both charge you for an app while also profiting off of your data or having poor security. Therefore, pricing is a bad criterion for finding an app that you can trust.

当然,公司既有可能向您收取应用程序费用,又有可能从您的数据中获利或安全性差,这很可能,也有可能。 因此,对于找到可以信任的应用程序来说,定价是一个糟糕的标准。

通过美学的信任 (Trust Through Aesthetics)

Woah, those app screenshots look so sleek! And their website is so colorful and tastefully designed, with beautiful animations that you simply can’t resist. Why would an adorable cartoon bear lie to you? Is that even possible?

哇,这些应用的屏幕截图看起来如此时尚! 他们的网站色彩缤纷,设计高雅,拥有令人无法抗拒的精美动画。 为什么可爱的卡通熊会对你说谎? 那有可能吗?

Well sadly, yes —  cartoon characters lie all the time. Since they were created by a human and their dialogue is written by a human, an adorable cartoon bear is not less likely to exploit your personal data for profit. It might look cuter while doing it though.

很可惜,是的-卡通人物无时无刻不在说谎。 由于它们是由人类创造的,而对话是由人类编写的,因此一只可爱的卡通熊不会少利用您的个人数据牟利。 虽然这样做可能看起来更可爱。

The aesthetics of a website might tell you that that they spent $20 on a SquareSpace theme (or pirated it), but say nothing about how trustable an app or service is — it‘s even possible that the company skimped on data security in order to spend more on their website’s design and animations.

网站的美感可能会告诉您,他们在SquareSpace主题上花费了20美元(或盗版了),但对于应用或服务的可信度却一无所知-公司甚至有可能为了提高支出而在数据安全性方面有所作为在他们网站的设计和动画上。

大众信任 (Trust Through Popularity)

If all your friends jumped off a digital bridge, would you? At one point, Yahoo had over three billion accounts, and in 2013, they broke the world record ? for biggest data breach ever, by a very long shot. Since then, there have been many more breaches of tens or hundreds of millions accounts of other companies. And these are only counting disclosed and known breaches — nobody knows what the real numbers are.

如果您所有的朋友都跳出了数字桥梁,是吗? 有一次,雅虎拥有超过30亿个帐户,而在2013年,他们打破了世界纪录? 远距离打击最大的数据泄露。 从那时起,其他公司的数以千万计的帐户遭到了更多的违反。 这些只是统计已披露和已知的违规行为,没人知道真正的数字是多少。

Popularity isn’t a reliable proxy of how trustworthy an app is. In fact, there are even scam apps that make it into the top charts of the App Store.

流行度并不是应用程序可信度的可靠代表。 实际上,甚至有一些骗局应用程序跻身App Store的榜首 。

通过“ 4096位军用超加密Rhino HTTPS刮板?????????”获得信任 (Trust Through “4096-Bit Military Ultra Encryption Rhino HTTPS Squeegee ?????????”)

Buzzwords are cool, but — wait no, buzzwords are terrible and extremely dishonest. Companies and marketers often deploy technobabble or purposely misuse and misapply jargon in order to give the impression of technical sophistication and legitimacy. Often times, if you don’t understand something, it’s either because the explainer has done a terrible job explaining the thing, or it’s because the explainer is intentionally trying to confuse you into submission. In either case, technobabble should make you more wary and trust the explainer even less.

流行语很酷,但是-等一下,流行语很糟糕而且很不诚实。 公司和营销人员经常部署技术漏洞,或者故意滥用和误用术语,以给人以技术成熟度和合法性的印象。 通常,如果您听不懂某事,这可能是因为解释者所做的事情做得很糟糕,或者是因为解释者有意使您迷惑。 无论哪种情况,technobabble都应使您更加警惕,对解释者的信任甚至更低。

那么到底是什么建立了信任? (So what actually creates trust?)

Apps should have to earn the trust of its users, especially when there are such strong financial incentives for companies to simply lie and abuse user data.

应用程序必须赢得用户的信任 ,尤其是当公司有如此强大的财务动机来简单地撒谎和滥用用户数据时。

To earn user trust, apps should be fully transparent— the public should be able to see everything the app and its servers are doing, so that anyone can verify that there’s no negligent, dishonest, or even malicious activity. In other words: trust through transparency.

为了赢得用户的信任,应用程序应该完全透明-公众应该能够看到应用程序及其服务器所做的一切,以便任何人都可以验证没有任何疏忽,不诚实甚至恶意的活动。 换句话说:通过透明信任。

通过透明信任 (Trust Through Transparency)

Full transparency means making the entire operation of an app public and verifiable, from the app code on your phone or computer, to the server code and infrastructure on the cloud, to the actions of the company’s employees, plus proof of all of that. It’s everything that touches your data. Everything.

完全透明意味着要公开和验证应用程序的整个操作过程,从手机或计算机上的应用程序代码到云上的服务器代码和基础架构,再到公司员工的行为, 再加上所有这些的证明。 接触您的数据的一切 。 一切。

If getting full and verifiable transparency from the apps we use every day seems like a radical idea, it’s because we’ve been trained for so long to expect so little from companies. We’ve been trained to upload our personal data, cross our fingers, and simply hope for the best. The truth is, if we’re giving companies our most sensitive personal information, why shouldn’t we expect them to give us proof of exactly what they’re doing with it?

如果从我们每天使用的应用程序中获得完整且可验证的透明度似乎是一个激进的主意,那是因为我们受了很长时间的培训,对公司的期望很小。 我们已经接受过培训,可以上传我们的个人数据,不由自主地希望取得最好的成绩。 事实是,如果我们要向公司提供我们最敏感的个人信息,为什么我们不应该期望他们为我们提供他们正在做什么的证据?

透明标准 (A Standard For Transparency)

To be clear, partial transparency is insufficient and misleading, because it still allows “bad bits” to be hidden, defeating the purpose of transparency. For example, a company hiding just a small part of their server code is still able to secretly copy all user data to unknown third parties from their servers.

需要明确的是, 部分透明是不够的并且具有误导性,因为它仍然允许隐藏“不良位”,从而破坏了透明的目的。 例如,一家仅隐藏服务器代码一小部分的公司仍能够将所有用户数据从其服务器秘密复制到未知的第三方。

So how do we know if an app is being fully transparent, versus only partially transparent or not transparent at all?

那么,我们如何知道某个应用程序是完全透明的,还是仅部分透明或完全不透明?

A standard for full transparency doesn’t exist today, so we’re creating one and giving it away for free.

如今,完全透明的标准还不存在,因此我们正在创建一个透明标准并免费提供。

This new standard is called Openly Operated, because full transparency requires the entire operation of an app to be open and verifiable. This includes making public all app source code, server code, infrastructure, and employee actions, as well as providing proof of accuracy and validity. It’s like giving the public read-only access to the app operator’s Admin console (example here).

此新标准称为“ 公开操作” ,因为要完全透明,就要求应用程序的整个操作都是开放且可验证的。 这包括公开所有应用程序源代码,服务器代码,基础结构和员工操作,以及提供准确性和有效性的证明。 就像授予公众对应用程序操作员的管理控制台的只读访问权限( 此处的示例)。

How this is different from apps today? Here’s the photo-sending example from the beginning again — except this time, the app is Openly Operated:

这与当今的应用程序有何不同? 这是从头开始的照片发送示例,但这次是“公开操作”的应用程序:

Unlike the earlier examples, the Openly Operated certification process forces the app to be fully and verifiably transparent, preventing the app’s operators from hiding privacy and security issues. This process, at a high level, is:

与之前的示例不同,“开放式” 认证过程迫使该应用程序具有完全可验证的透明性,从而防止应用程序的操作员隐藏隐私和安全问题。 从总体上讲,此过程是:

  1. The app fulfills specific requirements to demonstrate full transparency, and uses direct references to source code, infrastructure, and other evidence to prove the app’s privacy or security claims.

    该应用程序满足特定要求 证明完全透明,并使用直接引用源代码 , 基础架构和其他证据来证明该应用程序的隐私或安全声明 。

  2. Combine these requirements and proof of claims into an Openly Operated Audit Kit that anyone can publicly view and verify.

    将这些要求和索赔证明结合到一个开放式审计工具包中 任何人都可以公开查看和验证。

  3. Get matched with independent auditors, who verify the Audit Kit to produce public Openly Operated Audit Reports, detailing their verifications and providing a summary.

    与独立审核员匹配,他们审核审核工具包以生成公开的公开运行的审核报告 详细说明其审核并提供摘要。

This lets everyone participate in “trust through transparency”: users who are more technical can perform verifications themselves by diving into the nitty gritty details in the Audit Kit, while less tech-savvy users can read the independent Audit Reports and summaries. Openly Operated’s transparency is the opposite of the status quo, where apps simply tell users to read their totally unproven and unverifiable Privacy Policy.

这使每个人都可以参与“通过透明的信任”:技术含量较高的用户可以通过深入了解“审计工具包”中的具体细节来自己执行验证,而技术含量较低的用户可以阅读独立的审计报告和摘要。 公开操作的透​​明性与现状相反,在这种情况下,应用程序只是告诉用户阅读其完全未经验证和无法验证的隐私政策。

Openly Operated is a free certification. Our mission is for all apps to earn trust through transparency, so all documentation is available at no cost, and companies pay nothing to license the certification. We’ve even built examples to show that Openly Operated apps are possible. These are more than proof-of-concepts — they’re in production, fully functional, and are operating at scale with real users.

公开运营是免费的认证。 我们的使命是使所有应用程序都通过透明性赢得信任,因此所有文档均免费提供,并且公司无需支付任何费用即可获得认证许可。 我们甚至构建了一些示例来表明开放式应用是可行的。 这些不仅仅是概念验证-它们已经投入生产,功能齐全,并且可以与实际用户一起大规模运行。

一切都应该公开经营 (Everything Should Be Openly Operated)

Companies have been blatantly dishonest with how they handle and secure user data for too long. Since its creation until now, Facebook has had a privacy setting for user wall posts labeled “Only Me”. To any regular person, “Only Me” has a simple meaning: one person, themselves, and literally nobody else.

长期以来,公司一直公然不诚实地处理和保护用户数据。 自创建至今,Facebook已为贴有“ Only Me”的用户墙贴设置了隐私设置。 对于任何普通人来说,“只有我”的含义很简单:一个人,一个人,而实际上没有其他人。

But over the last ten years, we’ve learned the hard way that Facebook has a very different definition of “Only Me”. To Facebook, “Only Me” means “Me and All Of Facebook’s Advertisers and Their Partners and Some Of Facebook’s 25,000 Employees and Some Unknown Number Of Contractors and Facebook Apps That Friends or I Have Used and Those Apps’ Employees and Anyone Those Apps Share Or Sell Data To… Maybe”.

但是在过去的十年中,我们已经了解到Facebook对“仅我”的定义有很大的不同。 在Facebook上,“只有我”是指“我和所有 Facebook 广告客户 及其 合作伙伴,以及Facebook 25,000名 员工中的一些,以及朋友或我曾经使用过的 承包商和Facebook应用程序的 数量未知,以及这些应用程序的 员工以及这些应用程序 共享或分享的 任何人 将数据出售给 …… 也许 “。

Privacy and security scandals happen every week not because companies are evil, but because like anything else, companies operate on incentives. In a world where there’s no way to verify an app’s security or privacy claims, why should a company be honest and make less money, while their competitors are being dishonest and making more money? Current incentives give dishonest and insecure companies an edge to grow faster, compete more efficiently, spend more on marketing, and capture the most customers.

每周都会发生隐私和安全丑闻,这不是因为公司是邪恶的,而是因为公司像其他任何事情一样,都是在激励机制下运作。 在一个无法验证应用程序的安全性或隐私权声明的世界中,为什么一家公司应该诚实并赚取更少的钱,而竞争对手却不诚实并赚更多的钱? 当前的激励措施使不诚实和缺乏安全感的公司具有更快增长,更有效竞争,在营销上花费更多并吸引最多客户的优势。

Openly Operated provides a structured way for companies to prove their privacy and security claims. Users have nothing to lose and everything to gain by demanding transparency from the apps they give their personal data to. The question shouldn’t be “Why should the apps I use be transparent?” —  it should be “Why aren’t the apps I use transparent? What are they hiding?”

公开运营为公司提供了一种结构化的方式来证明其隐私和安全声明。 通过向其提供个人数据的应用程序要求透明性,用户不会有任何损失,也不会有任何收获。 问题不应该是“为什么我使用的应用程序应该透明?” -它应该是“ 为什么不能用透明的应用程序? 他们隐藏了什么?”

你可以做什么 (What You Can Do)

This is Openly Operated’s official release announcement. If you think a standard for full, verifiable transparency is important, here’s how to help:

这是Openly Operated的正式发布公告。 如果您认为建立完整的,可验证的透明度的标准很重要,请使用以下方法:

  1. Share this story with your friends and family. Many people are still stuck in the old ways of thinking that Privacy Policies, aesthetics, or popularity are useful metrics for trust. Show them that full transparency is what really matters, and that it’s actually possible.

    与您的朋友和家人分享这个故事。 许多人仍然停留在旧的思维方式中,认为隐私政策,美观或受欢迎程度是信任的有用指标。 向他们展示完全透明才是真正重要的,并且实际上是可能的。
  2. Subscribe to the Openly Operated newsletter to receive monthly updates. Your email address is kept private and never shared with third parties — see the proof in OpenlyOperated.org’s Audit Kit and Audit Reports.

    订阅公开通讯,以接收每月更新。 您的电子邮件地址是私有的,永远不会与第三方共享-请参阅OpenlyOperated.org的“ 审计工具包”和“ 审计报告”中 的证明 。

  3. Learn more at OpenlyOperated.org. No matter your level of technical expertise, there’s something for you, whether you’re a user curious about the many benefits of transparency, an engineer building apps people can trust, or a company that wants to win customers while increasing security.

    在OpenlyOperated.org上了解更多信息 。 无论您的技术专业知识水平是什么,无论您是对透明性的诸多好处感到好奇的用户,还是构建人们可以信赖的应用程序的工程师,还是想在提高安全性的同时赢得客户的公司,您都有所需要。

-

We are Johnny Lin and Rahul Dewan, co-founders of Openly Operated, the free transparency certification. We want to answer your questions and read your comments — email us at hi@openlyoperated.org, or find us on Telegram.

我们是免费透明性认证Openly Operated的联合创始人Johnny Lin和Rahul Dewan。 我们想回答您的问题并阅读您的评论-给我们发送电子邮件至hi@openlyoperated.org ,或在Telegram上找到我们。

This post originally appeared on the Openly Operated blog here.

该帖子最初出现在此处的Openly Operated博客中。

翻译自: https://www.freecodecamp.org/news/why-you-cant-trust-apps-today-and-how-to-fix-it/

应用程序启动器 标记为信任

相关文章:

小程序客服自动回复图片,云开发的实现

小程序先开通云开发,创建一个文件夹,并配置为云函数的目录 小程序客服自动回复图片实现步骤: 1.云函数接收消息推送 第一步:开发者工具云开发控制台中增加配置 打开云开发控制台,到设置 tab 中选择全局设置 - 添加消…

ORA-12514: TNS: 监听程序当前无法识别连接描述符中请求的服务解决

方法1: a、通过oracle 工具 Net Configuration Assistant 重新配置监听,注意如果有双网卡请配置第一块网上IP。如何知道哪一块是一块网卡,可以通过ipconfig命令查看最上面的ip就是一块网卡的 b、通过Net Configuration Assistant 工具配置 “…

r语言 编辑 d3.js_d3.js的语言介绍

r语言 编辑 d3.jsby Matt Oxley由马特奥克斯利(Matt Oxley) d3.js的语言介绍 (A linguistic introduction to d3.js) 如何从一个试探者变成一个自信的用户 (How to go from a tentative to a confident user) d3.js is a fantastic library — but I can honestly tell you th…

【Luogu3041】视频游戏的连击(AC自动机,动态规划)

题面链接 题解 首先构建出AC自动机 然后在AC自动机上面跑DP 转移很显然从Trie树的节点跳到他的儿子节点 但是要注意一个问题, 在计算的时候,每一个节点加入后能够 造成的贡献 要加上他的子串的贡献 至于DP: 设f[i][j]表示已经使用了i个字母 当…

拥抱高效、拥抱 Bugtags 之来自用户的声音(三)

小编按:这是一篇 Bugtags 用户来稿,主要是介绍了使用 Bugtags 前后对测试及解决 Bug 所带来的变化,感谢山西农业大学 - 高正炎同学对 Bugtags 的信赖和支持。小编在这里诚邀各位热心用户向我们投稿,说出你使用 Bugtags 的故事。 0…

小程序打开文档标题乱码处理

先下载,自定义临时文件目录名称,然后再打开就可以了。 wx.downloadFile({url: https://xxx.cn/sfxy.docx, //仅为示例,并非真实的资源filePath: wx.env.USER_DATA_PATH /这是自定义标题.docx,success(res) {console.log(0, res)wx.openDocum…

我是“真正的”软件工程师吗?

by Sun-Li Beatteay通过孙丽贝蒂 我是“真正的”软件工程师吗? (Am I a “real” Software Engineer yet?) Am I a “real” Software Engineer yet?我是“真正的”软件工程师吗? This question has haunted me for years. And it seems I’m not al…

ntpdate[31915]: the NTP socket is in use, exiting

[rootmaster local]# ntpdate cn.pool.ntp.org 10 Oct 13:24:36 ntpdate[31915]: the NTP socket is in use, exitingcron 作业中运行 ntpdate,以便大约每隔一小时就设置一次本地时间。最近,我每次运行该命令时都会收到下列错误消息。 ntpdate[31915]: t…

小程序云开发更新数组的指定对象的值

云开发,在小程序实现 代码说明‘: 在这里,数据集合 groupList 中的 userList 是一个用户列表数组,我要更新数组中,openid 等于我的openid 的在线状态为 true。 先查询条件,集合里面的 _id 等于我传的id&a…

Unreal Engine 4 RenderTarget制作Live Camera效果

Unreal Engine 4 RenderTarget制作Live Camera效果 先上效果: Live Camera我不知道怎么翻译。反正意思就是将一个摄影机的Image渲染到一个2D平面上。 以下介绍下详细的实现方法: 1.创建一个Scene Capture 2D对象 将这个对象拖动到合适的地方。2.创建Re…

领导让我重构代码_领导不是由代码构成

领导让我重构代码The team leader is a key figure in a team of developers. It is a difficult role, involving both technical and social skills. This is the reason why not everyone is tailored for it.团队负责人是开发人员团队中的关键人物。 这是一项艰巨的任务&am…

Spring学习-理解IOC和依赖注入

最近刚买了一本介绍ssm框架的书,里面主要对Mybatis、spring、springmvc和redis做了很多的讲解,个人觉得虽然有的内容我看不懂,但是整体上还是不错的。最近正在学习中,一边学习一边做一些总结,现在我对这些思想技术还没…

windows server2012怎样关机怎样重启-详细教程

|浏览:1991|更新:2014-12-15 17:33123456分步阅读百度经验:jingyan.baidu.com windows server2012和以往有些不同,关机/重启按钮不是在左边,甚至左边的“开始”都不见了,那怎样关机/重启呢?这里开始演示&am…

封装 localStorage 缓存,兼容网页,微信小程序,uni-app

封装的缓存功能,兼容网页,微信小程序,uni-app 使用,支持设置缓存,获取缓存,移除缓存,清空缓存,设置缓存时间,分组缓存设置。 把最下面的 Str4.js 代码拷贝到项目内可以直…

考csp所需算法_CSP vs RxJS:您所不知道的。

考csp所需算法by Kevin Ghadyani通过凯文加迪亚尼(Kevin Ghadyani) CSP vs RxJS:您所不知道的。 (CSP vs RxJS: what you don’t know.) CSP发生了什么? (What happened to CSP?) You probably clicked this article thinking “what is CSP?” It’s…

iOS蓝牙4.0开发例子

1建立中心角色 123#import <CoreBluetooth/CoreBluetooth.h> CBCentralManager *manager; manager [[CBCentralManager alloc] initWithDelegate:self queue:nil]; 2扫描外设&#xff08;discover&#xff09; [manager scanForPeripheralsWithServices:nil options:…

Spark Shuffle原理解析

Spark Shuffle原理解析 一&#xff1a;到底什么是Shuffle&#xff1f; Shuffle中文翻译为“洗牌”&#xff0c;需要Shuffle的关键性原因是某种具有共同特征的数据需要最终汇聚到一个计算节点上进行计算。 二&#xff1a;Shuffle可能面临的问题&#xff1f;运行Task的时候才会产…

云开发使用 got 的 get/post 传参请求示例代码

使用 got 进行网络请求的步骤&#xff1a; 1.创建云函数&#xff0c;并在终端执行云函数 2.执行 npm 安装 got &#xff0c;命令&#xff1a;cnpm install --save got 3.在云函数中使用 示例代码&#xff1a; // 云函数入口文件 const cloud require(wx-server-sdk) cons…

JavaScript词法作用域的简单介绍

by Michael McMillan迈克尔麦克米兰(Michael McMillan) JavaScript词法作用域的简单介绍 (An easy intro to Lexical Scoping in JavaScript) Lexical scoping is a topic that frightens many programmers. One of the best explanations of lexical scoping can be found in…

Flex 布局详解 - 转自阮一峰老师

Flex 是 Flexible Box 的缩写&#xff0c;意为"弹性布局"&#xff0c;用来为盒状模型提供最大的灵活性。任何的盒子都可以使用它。 下面我们来看一下使用 Flex 布局的容器的属性 flex-direction flex-wrap flex-flow justify-content align-items align-content 1.…

bzoj 1086: [SCOI2005]王室联邦

Description “余”人国的国王想重新编制他的国家。他想把他的国家划分成若干个省&#xff0c;每个省都由他们王室联邦的一个成员来管理。他的国家有n个城市&#xff0c;编号为1..n。一些城市之间有道路相连&#xff0c;任意两个不同的城市之间有且仅有一条直接或间接的道路。为…

在7分钟内深刻理解咖喱

Eric Elliott’s exceptional Composing Software series is initially what got me excited about functional programming. Its a must-read. 埃里克埃利奥特(Eric Elliott)杰出的合成软件系列最初使我对函数式编程感到兴奋。 这是必读的。 At one point in the series, he …

github后端开发面试题大集合(一)

作者&#xff1a;小海胆链接&#xff1a;https://www.nowcoder.com/discuss/3614?type0&order0&pos5&page0?fromwb来源&#xff1a;牛客网 转载自github&#xff0c;中文--->链接在这&#xff0c;英文---->链接在这文章较长&#xff0c;我把它拆分了三个部…

微信小程序左滑删除效果的实现完整源码附效果图

效果图&#xff1a; 功能描述&#xff0c;小程序列表左滑删除功能的实现完整源代码实现&#xff1a; <view wx:for{{friends}} wx:key"" wx:if{{groupType4}} catchtap"nav_oneChat" id"{{item._id}}" class"item p_r" style"…

Eclipse下修改工程名

一。 右键工程&#xff1a;Refactor->Rename&#xff0c;或选中工程按F2&#xff0c;修改名称 二。右键工程&#xff1a;Properties->Web Project Settings,修改Context Root三。1.找到项目所在位置&#xff08;如图&#xff09;&#xff1a; 2.修改项目目录/.setting目录…

git操作手册_基本的Git手册

git操作手册介绍 (Introduction) Hi! I am Sanjula, and in this guide I hope to teach you a little bit about Git including:嗨&#xff01; 我是Sanjula &#xff0c;在本指南中&#xff0c;我希望教您一些有关Git的知识&#xff0c;包括&#xff1a; What Git is 什么是…

PHP 接入(第三方登录)QQ 登录 OAuth2.0 过程中遇到的坑

前言 绝大多数网站都集成了第三方登录&#xff0c;降低了注册门槛&#xff0c;增强了用户体验。最近看了看 QQ 互联上 QQ 登录的接口文档。接入 QQ 登录的一般流程是这样的&#xff1a;先申请开发者 -> 然后创建应用&#xff08;拿到一组 AppId 和 AppKey&#xff09;-> …

npm全局环境变量配置,全局配置cnpm

今天新电脑想安装node.js &#xff0c; 发现最新版本的node.js已经不支持win7了&#xff0c;但是又不想换系统&#xff0c;所以找了个旧版本&#xff0c;这里不多说了。如果找不到旧版本的node下载&#xff0c;可以去我的QQ交流群文件里面下载&#xff0c;QQ群号&#xff1a;17…

NTFS for Mac OS X:使用Brew安裝NTFS-3G

在最新的OSX系統中&#xff0c;其實已經完整兼容NTFS文件系統&#xff0c;只是出於安全考慮默認是以只讀模式掛載NTFS分區的&#xff0c;可以透過diskutil查詢硬碟UUID&#xff0c;重新以讀寫(rw)權限掛載&#xff0c;具體的可以參照這裡 當然&#xff0c;也有現成的軟體幫助你…

javascript开关_JavaScript开关案例简介

javascript开关In this short article, I will introduce you to JavaScript switch cases and how to use them with practical examples.在这篇简短的文章中&#xff0c;我将向您介绍JavaScript切换案例以及如何通过实际示例使用它们。 This article will explain better wi…