如何使用StumbleUpon:分步指南

Today I begin a series of articles that will teach you how to use StumbleUpon efficiently to maximize traffic to your site, and to all the sites you discover. I assume some of our readers are already StumbleUpon members, and for those who are not SU already has a page that helps as well – getting started. The topic of today’s article is: Things that Kill SU Traffic

今天,我开始撰写一系列文章,这些文章将教您如何有效地使用StumbleUpon,以最大程度地增加您网站和您发现的所有网站的访问量。 我假设我们的某些读者已经是StumbleUpon的成员,对于那些不是SU的人来说,他们已经拥有一个可以帮助您的页面- 入门今天这篇文章的主题是:阻止SU流量的事物

Stumbleupon Logo

StumbleUpon is a browser based social media community. I use “browser-based” in the absence of a better term. Although SU has a site where interaction between members is possible, the StumbleUpon Toolbar is the lifeblood of the network – it helps you browse the SU bookmarks, search, send messages to your SU friends, vote for web pages and much more. The toolbar is available for IE, Flock and Firefox – other browsers are not currently available.

StumbleUpon是一个基于浏览器的社交媒体社区 。 在没有更好的术语的情况下,我使用“基于浏览器的浏览器”。 尽管SU拥有一个可以在成员之间进行交互的站点,但是StumbleUpon工具栏是网络的命脉–它可以帮助您浏览SU书签,搜索,向SU朋友发送消息,为网页投票等。 该工具栏可用于IE,Flock和Firefox –其他浏览器当前不可用。

The most important thing you need to learn in order “not” to “kill” potential SU traffic is how to use the toolbar correctly.

为了“不”“杀死”潜在的SU流量,您需要学习的最重要的事情是如何正确使用工具栏。

Stumbleupon Toolbar

To better understand the terms below, here is a small glossary:

为了更好地理解以下术语,这里有一个小的词汇表:

  • To vote/stumble: to click on the “thumbs up” or “thumbs down” buttons to vote for a story; to click on the “stumble” button to browse the StumbleUpon database

    投票/绊倒 :单击“竖起大拇指”或“竖起大拇指”按钮为故事投票; 单击“ stumble”按钮浏览StumbleUpon数据库

  • To discover: when you click “thumbs up” (and a page does not exist in the SU database) a pop-up appears telling you that you’ve discovered a new page. A discovery is not complete without a review, proper categorizing and tagging.

    发现 :单击“竖起大拇指”(并且SU数据库中不存在某个页面)时,将显示一个弹出窗口,告诉您已发现新页面。 没有审查,正确的分类和标记,发现是不完整的。

  • To review: to write your personal comments about the page you vote for, or against; or to copy/paste a fragment of the content of the page

    评论 :针对您支持或反对的页面发表您的个人评论; 或复制/粘贴页面内容的一部分

  • To send to: to share a webpage with your friends, via SU toolbar or email

    发送至 :通过SU工具栏或电子邮件与您的朋友共享网页

Sounds easy? Well, things get tricky if you don’t know the following rules:

听起来容易吗? 好吧,如果您不知道以下规则,事情就会变得棘手:

首先发现,然后查看然后提交 (First Discover, Then Review and Then Submit )

For maximum traffic potential a page needs to be “discovered” from the browser toolbar and reviewed. To “discover” a page you click on the “thumbs up” icon. A pop-up will then appear asking you to review your discovery, to select the appropriate category for it, to tag it, to specify whether it contains adult content and only then to submit it.

为了获得最大的流量潜力,需要从浏览器工具栏“发现”页面并进行查看。 要“发现”页面,请单击“竖起大拇指”图标。 然后将出现一个弹出窗口,要求您检查发现,选择相应的类别,对其进行标记,指定其是否包含成人内容并随后提交。

StumbleUpon Discovery

This is the first review, and it is critical for the traffic volume a page might get. The new discovery will only enter the StumbleUpon queue of pages shown to the SU community if it has a review. Not reviewing condemns the page you discover to a slow death, especially if no other stumblers after you bother to write a review. Chances are , if you don’t write a review, no other stumbler will ever see that page.

这是第一篇评论,对于页面可能获得的访问量至关重要。 如果有发现,新发现将仅进入显示给SU社区的StumbleUpon页面队列。 不审阅将发现的页面判为缓慢死亡,尤其是当您烦恼撰写评论后没有其他绊脚石时。 很有可能,如果您不撰写评论,则其他任何绊脚石都不会看到该页面。

A Dead Page at StumbleUpon

Having these “dead” discoveries is also bad for your “Stumble karma.” The main interest of SU is to have active members. Simply clicking “thumbs up” and “thumbs down” does not make you an active member. The most popular stumblers have an impressive number of stumbles (votes), an impressive number of reviews, and also many subscribers (how to get subscribers in a future article). While it is not crucial to write a review each time you “stumble”, it is very important to write one when you “discover” a page obviously.

拥有这些“死”发现也不利于您的“绊倒业障”。 SU的主要兴趣是拥有活跃的成员。 仅仅单击“竖起大拇指”和“竖起大拇指”并不能使您成为活跃成员。 最受欢迎的stumbler拥有不胜枚举的数量(投票),不胜枚举的评论以及许多订阅者(如何在以后的文章中获得订阅者)。 虽然每次“绊脚”都写一篇评论并不重要,但显然当“发现”页面时写一篇评论很重要。

Pages that eventually receive reviews are “rescued”, but their chances of getting good traffic remain very low.

最终收到评论的页面被“拯救”,但是获得良好流量的机会仍然很小。

不要先发现新页面就“发送”到新页面 (Don’t “Send to” New Pages without Discovering Them First)

The easiest way to “kill” traffic chances for a page is to use the “send to” button in the StumbleUpon toolbar before discovering a page, and even before thumbing it up. SU allows its users to share (“send to”) pages regardless of their votes for the page. Sharing is a great thing, but not when you do it to the detriment of the page you want to share.

“杀死”页面访问机会的最简单方法是在发现页面甚至翻阅页面之前,使用StumbleUpon工具栏中的“发送至”按钮。 SU允许其用户共享(“发送到”)页面,而不考虑其对该页面的投票。 共享是一件很了不起的事情,但如果这样做却不利于您要共享的页面,那不是一件好事。

The page you “sent to” without reviewing enters the StumbleUpon database, but not the queue that will ensure that other SU users will see it.

您“发送到”未经检查的页面将进入StumbleUpon数据库,但不会进入确保其他SU用户可以看到它的队列。

The negative effects of "send to"
不要将StumbleUpon按钮添加到您的网站 (Don’t Add StumbleUpon Buttons to Your Site)
Don't add SU buttons to your site.

Social sharing buttons and widgets are great: they help your visitors to submit your stories fast to the social and bookmarking sites of their choice. But did you know that onsite SU buttons could be detrimental? They are detrimental for the site they are published on, and they are also detrimental for the unsuspecting SU users who click on them. Why You ask?

社交共享按钮和小部件很棒:它们可以帮助访问者将您的故事快速提交到他们选择的社交和书签站点。 但是您知道现场的SU按钮可能有害吗? 它们对发布它们的网站有害,也对单击它们的毫无戒心的SU用户有害。 你为什么问?

Because StumbleUpon wants you to use the toolbar. Sure, they have some buttons that you could add to your site, but it is better to link these directly to your SU profile, rather than using special widgets that “stumble” automatically.

因为StumbleUpon希望您使用工具栏。 当然,它们具有一些可以添加到站点的按钮,但是最好将这些按钮直接链接到您的SU配置文件,而不是使用自动“绊倒”的特殊小部件。

The main advice SU gives to those who want to become “top stumblers” is:

SU给想要成为“顶级绊脚石”的人的主要建议是:

To become a Top Stumbler, simply use the toolbar on a regular basis, clicking I-like-it at any page other members would like to stumble upon.

要成为“顶级stumbler”,只需定期使用工具栏,在其他成员想要绊倒的任何页面上单击“我喜欢”即可。

I would add: use the toolbar correctly if you want to enjoy a full SU experience with all its benefits. Traffic is directly proportionate to the proper methodology and practice of the experienced user in most cases. There are any number of other “techniques” to improve traffic we will discuss later, but for a start, at least avoid the mistakes described above.

我要补充一点:如果您想充分享受SU带来的所有好处,请正确使用工具栏。 在大多数情况下,流量直接与经验丰富的用户的正确方法和做法成比例。 还有许多其他“技术”可以改善流量,我们将在后面讨论,但是首先,至少要避免上述错误。

翻译自: https://www.sitepoint.com/things-that-kill-stumbleupon-traffic/

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
There may be many reasons that brought you here, it could be because you heard all about Hadoop and what it can do to crunch petabytes of data in a reasonable amount of time. While reading into Hadoop you found that for random access to the accumulated data there is something call HBase. Or it was the hype that is prevalent these days addressing a new kind of data storage architecture. It strives to solve large scale data problems where traditional solutions may either be too involved or cost prohibitive. A common term used in this area is NoSQL. No matter how you have arrived here, I presume you want to know and learn - like me not too long ago - how you can use HBase in your company or organization to store a virtually endless amount of data. You may have a background in relational databases theory or you want to start fresh and this "column oriented thing" is something that seems to fit your bill. You also heard that HBase can scale without much effort and that alone is reason enough to look at it since you are building the next web-scale system. I was at that point in late 2007 facing the task of storing millions of documents in a system that needed to be fault tolerant and scalable while still being maintainable by just me. I have decent skills in managing a MySQL database system and was using it to store data that would ultimately be served to our website users. This database was running on a single server, with another as a backup. The issue was that it would not be able to hold the amount of data I needed to store for this new project. I either invest into serious RDBMS scalability skills, or find something else instead. Obviously I went the latter route and since my mantra always was (and still is) "How does someone like Google do it?", I came across Hadoop. After a few attempts of using Hadoop directly I was faced with implementing a random access layer on top of it - but that problem had been solved already: in 2006 Google had published a paper called BigTable [1] and the Hadoop developers had an open-source implementation of it called HBase (the Hadoop Database). That was the answer to all my problems. Or so it seemed... What follows is a blur to me. Looking back I realize that I would have wished for this customer project to start today. HBase is now mature, nearing a 1.0 release and is used by many high profile companies, such as Facebook, Adobe, Twitter, and StumbleUpon. Mine was one of the very first clusters in production (and is still in use today!) and my use-case triggered a few very interesting issues (let me refrain from saying more). But that was to be expected betting on a 0.1x version of a community project. And I had the opportunity over the years to contribute back and stay close to the development team so that eventually I was humbled by being asked to become a full-time committer as well. I learned a lot over the last few years from my fellow HBase developers and am still learning more every day. My belief is that we are by far not at the peak of this technology and it will evolve further over the years to come. Let me pay my respect to the entire HBase community with this book which strives to cover not just the internal workings of HBase or how to get it going but more specifically how to apply it to your use-case. In fact, I strongly assume that this is why you are here right now. You want to learn how HBase can solve your problem. Let me help you trying to figure this out.

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值