Hubbry Logo
Slashdot effectSlashdot effectMain
Open search
Slashdot effect
Community hub
Slashdot effect
logo
7 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Contribute something
Slashdot effect
Slashdot effect
Slashdot effect
View on Wikipedia
from Wikipedia

The Slashdot effect, also known as slashdotting or the hug of death occurs when a popular website links to a smaller website, causing a massive increase in traffic. This overloads the smaller site, causing it to slow down or even temporarily become unavailable. Typically, less robust sites are unable to cope with the huge increase in traffic and become unavailable – common causes are lack of sufficient data bandwidth, servers that fail to cope with the high number of requests, and traffic quotas. Sites that are maintained on shared hosting services often fail when confronted with the Slashdot effect. This has the same effect as a denial-of-service attack, albeit accidentally. The name stems from the huge influx of web traffic which would result from the technology news site Slashdot linking to websites. The term flash crowd is a more generic term.[1]

The original circumstances have changed, as flash crowds from Slashdot were reported in 2005 to be diminishing due to competition from similar sites,[2] and the general adoption of elastically scalable cloud hosting platforms.

Terminology

[edit]

The term "Slashdot effect" refers to the phenomenon of a website becoming virtually unreachable because too many people are hitting it after the site was mentioned in an interesting article on the popular Slashdot news service. It was later extended to describe any similar effect from being listed on a popular site.[3]

The effect has been associated with other websites or metablogs such as Fark, Digg, Drudge Report, Imgur, Reddit, and Twitter, leading to terms such as being farked or drudged, being under the Reddit effect, or receiving a hug of death from the site in question.[4][5] Another generic term, "flash crowd,"[6] originates from Larry Niven's 1973 novella by that name, in which the invention of inexpensive teleportation allows crowds to materialize almost instantly at the sites of interesting news stories.

Cause

[edit]

Sites such as Slashdot, Digg, Reddit, StumbleUpon and Fark consist of brief submitted stories and a self-moderated discussion on each story. The typical submission introduces a news item or website of interest by linking to it. In response, large masses of readers tend to simultaneously rush to view the referenced sites. The ensuing flood of page requests from readers can exceed the site's available bandwidth or the ability of its servers to respond, and render the site temporarily unreachable.

Google Doodles, which link to search results on the doodle topic, also result in high increases of traffic from the search results page.[7]

Extent

[edit]
MRTG graph from a web server statistics generator showing a moderate Slashdot effect in action in 2005

Major news sites or corporate websites are typically engineered to serve large numbers of requests and therefore do not normally exhibit this effect. Websites that fall victim may be hosted on home servers, offer large images or movie files or have inefficiently generated dynamic content (e.g. many database hits for every web hit even if all web hits are requesting the same page). These websites often became unavailable within a few minutes of a story's appearance, even before any comments had been posted. Occasionally, paying Slashdot subscribers (who have access to stories before non-paying users) rendered a site unavailable even before the story was posted for the general readership.

Few definitive numbers exist regarding the precise magnitude of the Slashdot effect, but estimates put the peak of the mass influx of page requests at anywhere from several hundred to several thousand hits per minute.[8][9][10] The flood usually peaked when the article was at the top of the site's front page and gradually subsided as the story was superseded by newer items. Traffic usually remained at elevated levels until the article was pushed off the front page, which could take from 12 to 18 hours after its initial posting. However, some articles had significantly longer lifetimes due to the popularity, newsworthiness, or interest in the linked article.

By 2005, reporters were commenting that the Slashdot effect had been diminishing.[2] However, the effect has been seen involving Twitter when some popular users mention a website.[11]

When the targeted website has a community-based structure, the term can also refer to the secondary effect of having a large group of new users suddenly set up accounts and start to participate in the community. While in some cases this has been considered a good thing, in others it is viewed with disdain by the prior members, as quite often the sheer number of new people brings many of the unwanted aspects of Slashdot along with it, such as trolling, vandalism, and newbie-like behavior. This bears some similarity to the 1990s Usenet concept of Eternal September.

Assistance and prevention

[edit]

Many solutions have been proposed for sites to deal with the Slashdot effect.[12]

There are several systems that automatically mirror any Slashdot-linked pages to ensure that the content remains available even if the original site becomes unresponsive.[13] Sites in the process of being Slashdotted may be able to mitigate the effect by temporarily redirecting requests for the targeted pages to one of these mirrors. Slashdot does not mirror the sites it links to on its own servers, nor does it endorse a third party solution. Mirroring of content may constitute a breach of copyright and, in many cases, cause ad revenue to be lost for the targeted site.

See also

[edit]

References

[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Slashdot effect

View on Grokipedia
from Grokipedia
The Slashdot effect, also known as "slashdotting" or the "/. effect," refers to the phenomenon in which a website experiences a massive and often overwhelming surge in traffic after being linked or mentioned in an article on the technology news site Slashdot (slashdot.org), typically rendering the site temporarily inaccessible to visitors. This unintentional overload differs from a deliberate denial-of-service (DoS) attack, as it stems from genuine user interest driven by Slashdot's large readership of tech enthusiasts. The term originated in the late 1990s within the community, with early references appearing around the second quarter of , including a November 1998 article on the site itself. By February 1999, Slashdot editor Rob Malda (CmdrTaco) highlighted it as a daily occurrence, noting that links from the site frequently "knock down" targeted servers due to the platform's influence in the open-source and communities. Studies from the era, such as Adler's of spikes following announcements on Slashdot and similar sites like LinuxToday, documented rapid increases—such as hits jumping from 30 to 250 per minute within of a post—demonstrating the effect's measurable impact on patterns. The effect's consequences include server crashes, prolonged downtime lasting hours or days, escalated bandwidth costs for site owners, and lost potential ad revenue, particularly affecting smaller or underprepared websites. Real-world examples from the late 1990s and early 2000s involved sites like crashing under the influx, underscoring how Slashdot's aggregation of user-submitted stories could amplify visibility but at a high operational cost. Over time, the Slashdot effect has inspired mitigation strategies, such as content delivery networks like to distribute traffic, and services like Mirrordot, which temporarily mirrored affected sites while preserving original ads and links, though such tools were experimental and not universally adopted. Although 's influence has waned since the early due to improved web infrastructure and declining site popularity, the concept has generalized to analogous phenomena, including the "Reddit hug of death" from links on or traffic spikes from other high-traffic platforms like , reflecting broader challenges in handling viral web exposure as of 2025.

Definition and History

Core Definition

The Slashdot effect refers to a sudden and massive surge in website traffic triggered by a prominent link from .org, which can overwhelm servers and cause slowdowns, outages, or complete crashes. This phenomenon is often compared to an unintentional distributed denial-of-service (DDoS) attack, as the influx stems from organic user curiosity rather than malicious intent, yet it produces similar disruptive outcomes for unprepared infrastructure. Key characteristics of the Slashdot effect include its disproportionate impact on smaller or less-resourced websites, which typically lack the to absorb rapid, unpredictable visitor spikes from large audiences. Unlike targeted cyber threats, it arises from genuine community-driven interest, amplifying visibility but exposing vulnerabilities in web hosting and bandwidth management during the early era. The concept draws from the more general term "flash crowd," coined by science fiction author in his 1973 novella Flash Crowd, which depicted abrupt gatherings of people at event sites facilitated by instantaneous technology. In the digital context, this term was adapted to describe analogous traffic overloads, with the effect serving as a prominent real-world example. Initial instances of the effect were observed in the late , when hyperlinks featured on .org directed thousands of readers to external sites, frequently rendering them inaccessible due to the ensuing traffic deluge.

Historical Origins

The Slashdot effect emerged in the late alongside the rapid growth of .org, a news website founded in 1997 by Rob Malda (known online as CmdrTaco) and Jeff (known as Hemos). Initially launched as Malda's personal site "Chips & Dips," it evolved into .org with Bates providing financial backing for domain registration, focusing on , , and tech culture to attract a niche audience of enthusiasts. By the fall of 1998, the site had amassed approximately 300,000 daily readers, fueled by its community-driven format of user-submitted stories and discussions, which began amplifying traffic to linked external websites. The phenomenon was first widely recognized in 1998, when links from caused sudden surges in traffic that overwhelmed targeted sites, rendering them temporarily inaccessible. An early documented instance occurred in July 1998, when a Slashdot post about delays in Microsoft's 5.0 release drove tens of thousands of visitors to , contributing to downtime described contemporaneously as the "Slashdot Effect." This term gained further prominence on February 15, 1999, with a self-referential article titled "Beware of the Slashdot Effect," which warned niche web portals about the risks of sudden popularity from the site's links, explicitly naming the issue after the overload it caused. The effect arose during the dot-com boom of the late 1990s, a period of explosive internet growth and investment in tech startups, when 's dedicated readership of tech-savvy users could generate massive, uncoordinated visits to smaller sites lacking robust infrastructure. The name derives from the site's URL shorthand "/." (pronounced "slashdot"), commonly used by its community. By 1999, the term was formalized in Eric S. Raymond's , a comprehensive glossary of terminology, defining the "slashdot effect" as the inaccessibility of a due to excessive hits following a mention, distinguishing it from intentional attacks.

Mechanisms and Causes

Traffic Surge Mechanisms

The Slashdot effect begins when a high-traffic , such as , publishes a story featuring a to a smaller or less-prepared , prompting a rapid influx of visitors from its readership. This linking process typically involves editors selecting user-submitted stories that highlight niche topics, embedding direct URLs within the article text to encourage immediate exploration by readers. For instance, an announcement on around 4:00 PM can drive the initial wave of clicks, as the site's prominence in the tech community funnels tens to hundreds of thousands of potential visitors toward the target site in a short timeframe. The audience of platforms like contributes to the phenomenon's intensity by exhibiting prompt and synchronized browsing behavior. Unlike gradual traffic growth from search engines or social shares, these users often access linked content within minutes of publication, creating a "flash crowd" characterized by sharp spikes in request rates—such as escalating from baseline levels to over 250 hits per minute in under 15 minutes. This immediacy stems from the site's role as a timely news hub, where subscribers check updates frequently, leading to bulk arrivals of new ("") clients with short inter-arrival times of 1-3 seconds between requests. Amplification occurs through the open, user-generated nature of these aggregators, which lack paywalls or access delays, fostering rapid and secondary sharing among readers. Community features like comments and story submissions encourage further propagation, as engaged users discuss and repost links on forums or lists, extending the surge beyond the initial announcement. For example, a single story can sustain elevated traffic for hours due to its persistence on , compounded by cross-postings from related sites, resulting in prolonged overload from organic interest rather than isolated clicks. While resembling a distributed denial-of-service (DDoS) attack in its volume and suddenness—flooding servers with legitimate requests that mimic malicious overload—the Slashdot effect is fundamentally benign, arising from genuine curiosity rather than coordinated harm. This distinction highlights its non-adversarial origin, where the surge stems from collective enthusiasm for compelling content, yet it can still cause comparable disruptions through sheer concurrency of accesses.

Technical Overload Factors

The Slashdot effect often overwhelms websites due to bandwidth constraints inherent in smaller-scale hosting setups, where upload and download capacities are typically limited to 1-10 Mbps on shared or home servers, insufficient to handle abrupt influxes of concurrent connections. For instance, origin servers on DSL connections with capacities around 384 Kbit/sec can experience severe congestion during flash crowds, leading to packet drops and degraded performance as the network interface saturates. This bottleneck is exacerbated when the surge originates from a high-traffic aggregator like , directing thousands of users to under-provisioned sites in a short period. Server resource limits further compound the issue, as spikes in concurrent requests overload CPU and RAM, particularly for sites generating dynamic content through database queries or unoptimized scripts. Under such loads, CPU utilization can remain low (e.g., 15%) while memory approaches 98%, triggering swapping and halting effective request processing, which prevents the server from responding to legitimate traffic. These limitations are most pronounced in environments lacking efficient caching, where each hit requires resource-intensive operations, contrasting with static sites that primarily strain bandwidth rather than computational resources. Primarily affecting personal blogs, indie projects, and low-cost shared hosting without auto-scaling capabilities, the effect spares larger enterprise setups but devastates those on single-server configurations. Such hosting types, common for independent developers in the late and early , rely on fixed resources that cannot dynamically allocate during peaks, making them vulnerable to even moderate surges compared to static sites hosted on robust platforms. Network effects amplify these vulnerabilities through ISP throttling, routing inefficiencies, and resulting timeouts, often manifesting as HTTP 503 Service Unavailable errors when servers or intermediaries discard excess requests to prevent total collapse. Adaptive at the network edge can throttle 32-49% of incoming traffic, while congestion causes widespread and increased latency for unaffected "bystander" connections, further isolating the target site. In severe cases, bottlenecks propagate delays across ISPs, turning a localized overload into a broader failure.

Extent and Impacts

Scale and Duration

The Slashdot effect characteristically produces traffic peaks of 100 to over 1,000 requests per minute on targeted websites, equating to 10x to 100x surges above baseline levels for small to medium sites, with aggregate daily visits occasionally exceeding one million. In modeled scenarios, flash crowd peaks can reach 10,000 requests per minute, while real-world examples document hourly bursts up to 1,800 hits, representing over 30x normal volume. Duration patterns feature an acute initial spike lasting 1 to 2 hours, followed by sustained elevated for 12 to 18 hours as the originating story remains prominent. Events may extend further with secondary waves triggered by shares on secondary sites, though primary effects typically subside within a day. Variability in scale and longevity hinges on the linking platform's audience—Slashdot drew millions of monthly unique visitors at its early-2000s zenith—and the story's inherent virality, which amplifies referral chains. Larger audiences and highly engaging content yield more intense, prolonged surges, with peak-to-average ratios up to 1,000x in extreme cases. Precise measurement poses significant challenges, as overload often causes server crashes that truncate logs, though preserved records from resilient events illustrate exponential ramp-up curves, with traffic growing logarithmically before plateauing.

Site-Level Consequences

The Slashdot effect frequently causes temporary downtime for targeted websites, ranging from hours to several days, as servers struggle to handle the abrupt influx of visitors. For instance, in one early 1999 case, a site hosting a collection of fun video clips was forced offline shortly after being linked on Slashdot, resulting in the owner receiving a personal intervention call from their internet service provider (ISP). In the early 2000s, DVDFile.com's web server "melted down" under the load despite having sufficient bandwidth capacity of 10 Mbps—far exceeding its typical 1-2 Mbps usage—leading to complete inaccessibility. Another example from 1999-2000 involved a site displaying micro-photographs of silicon art, where the initial Microsoft IIS server on Windows NT crashed entirely, necessitating a rebuild on Linux to manage static content delivery, though bandwidth limits still constrained performance. Such outages directly result in lost revenue, as unavailable pages prevent user interactions, while frustrated users often abandon the site without completing visits. Resource strain extends beyond immediate crashes, with affected sites facing elevated hosting costs due to bandwidth overages and the need for temporary scaling or upgrades to recover. On the positive side, surviving a Slashdot effect can provide a long-term visibility boost, attracting sustained interest from tech-savvy audiences and potentially increasing subscribers or users if the site recovers swiftly. For example, after a 2007 Slashdot mention, the blog Fractals of Change experienced over 100 times its normal hourly traffic, converting a small but notable portion of new visitors into regular readers via RSS or email subscriptions, alongside heightened exploration of related content and even book sales. Within tech communities, enduring the effect is often viewed as a "badge of honor," signaling credibility and relevance among enthusiasts.

Responses and Mitigation

Prevention Strategies

To withstand the Slashdot effect, website owners can implement infrastructure upgrades focused on scalable architectures. Content delivery networks (CDNs) such as or Akamai distribute incoming traffic across a global network of edge servers, caching and delivering content closer to users to alleviate load on the primary server during sudden surges. Auto-scaling cloud hosting platforms, including (AWS) and Google Cloud, enable dynamic resource provisioning by automatically adding or removing compute instances based on real-time demand metrics, ensuring capacity matches traffic without manual intervention. These measures are particularly effective for small to medium sites, where free or low-cost tiers—such as 's basic plan—provide accessible entry points for enhanced resilience. Optimization techniques further bolster defenses by reducing server strain and controlling access. Caching static assets with in-memory systems like or database query caches in minimizes repeated computations and database queries, serving pre-loaded content rapidly even under high load. Rate limiting configurations, for instance using directives to cap requests at a defined rate per client IP (e.g., 3 requests per second), prevent any single source from overwhelming resources while allowing legitimate traffic to flow. Additionally, enabling content compression via modules like mod_deflate in or in shrinks payload sizes, and integrating DDoS protection services from providers like Akamai filters malicious or excessive requests at the network edge, distinguishing flash crowds from attacks. Preparation steps are essential for proactive readiness, involving ongoing monitoring and testing. Site administrators should track patterns using tools like AWS CloudWatch or 's monitoring dashboards to establish baselines and detect anomalies early. Stress-testing servers with benchmarks such as Bench simulates surge scenarios, identifying bottlenecks like network latency—addressed by selecting low-hop hosting providers via analysis—and informing optimizations like aggregating CSS/ files. plans, including reverse proxies like for quick content delivery, ensure continuity; for resource-constrained small sites, leveraging free scaling tiers from AWS or allows cost-effective handling of unexpected spikes without upfront investment. The evolution of these tools has significantly diminished the Slashdot effect's severity over time. By the mid-2000s, the widespread adoption of broadband internet and early CDNs like Akamai reduced overall vulnerability, as higher connection speeds and distributed caching absorbed traffic that once overwhelmed modest servers. As of 2025, additional strategies include machine learning-driven in-network to distinguish legitimate surges from attacks and platforms like for instantaneous scaling without server management.

Community and Platform Assistance

One early collaborative solution to mitigate the Slashdot effect was the Mirrordot project, launched in 2004 by Jay Jacobson, a Slashdot user and founder of the network security firm Edgeos. Mirrordot automatically copied the full content of websites linked on 's homepage to distributed servers hosted by Deru Internet, which donated bandwidth for the initiative, allowing the mirrors to remain active for approximately two days. This service framed mirrored pages to clearly indicate they were copies, while preserving original advertisements and referral links to support the affected site's revenue. Community volunteers have also stepped in to host temporary mirrors for overwhelmed sites, drawing from the tech-savvy user base of platforms like to distribute load during surges. For instance, in cases of severe overload, individuals with available server capacity offered to replicate content, enabling visitors to access information without further straining the original host. Such volunteer efforts, often coordinated through forum discussions, provided ad-hoc relief but relied on quick coordination among participants. Platform interventions have included proactive measures to soften traffic impacts. These steps help distribute awareness and encourage self-mitigation without halting coverage. Tech communities, including forums like , frequently respond to traffic spikes by sharing practical advice and resources for rapid recovery. Users often suggest temporary hosting solutions, such as spinning up elastic cloud instances on platforms like or AWS EC2 for quick scaling, which can handle surges without long-term commitments. Open-source tools like for caching static content or for load balancing are commonly recommended and shared post-event, allowing affected sites to implement defenses like reduced timeouts or pre-baked static pages to absorb future loads. These collaborative exchanges turn individual crises into broader learning opportunities within the developer ecosystem. Despite these benefits, and community assistance carry risks and limitations. Unauthorized copying can raise concerns, as seen in early discussions between and Mirrordot to ensure compliance, potentially leading to legal disputes if content is replicated without permission. Additionally, diverted traffic to mirrors may dilute ad revenue for the original site by bypassing its and . Overall, such aid remains largely ad-hoc, effective for tech-oriented victims but less scalable for non-technical or resource-poor operators facing unpredictable surges.

Historical Decline and Modern Relevance

The Slashdot effect began to wane in the mid-2000s as 's influence in aggregating tech news diminished amid the rise of competing social news platforms. This shift reduced the frequency and intensity of traffic surges originating from links, as its audience fragmented across newer sites. Concurrently, advancements in web infrastructure, including the launch of in , enabled scalable cloud hosting that allowed websites to dynamically allocate resources during sudden spikes, making overloads less common. Key factors in this decline included the widespread adoption of content delivery networks (CDNs) such as Akamai, which distributed traffic across global servers to prevent bottlenecks, alongside improvements in speeds and server optimization techniques. These developments collectively enhanced site resilience, transforming the web from a landscape vulnerable to flash crowds into one better equipped to handle viral attention. For instance, cloud-based elasticity models, as explored in research on autonomic , demonstrated how platforms could automatically scale to mitigate effects akin to the phenomenon without revenue loss from non-commercial surges. In the , the original effect remains an occasional concern primarily for under-resourced websites. While comprehensive studies on outage reductions are limited, analyses of service disruptions from to indicate load-related outages, including those from spikes, accounted for about 9% of incidents, with broader improvements in resilient architectures reducing overall . As of 2025, no major recent instances of the effect have been widely documented, underscoring its evolution from a pervasive to a rare occurrence, particularly for non-commercial or hobbyist sites.

Analogous Effects from Other Platforms

The Reddit hug of death refers to the sudden influx of traffic to a website following a link shared on Reddit, often overwhelming servers and causing downtime; this phenomenon has been documented since the late 2000s, analogous to the Slashdot effect but driven by subreddit communities. Similarly, the Fark effect describes comparable overloads from links posted on Fark.com, a humor and news aggregation site active since the early 2000s, where user submissions lead to rapid visitor spikes targeting niche or viral content. The Drudge Report effect, stemming from the high-traffic political news aggregator Drudge Report, involves massive referral surges that can dominate site analytics, as seen in cases where a single link drives significant portions of daily visits to linked outlets. Mentions on (now X) have formalized the "Twitter effect" for traffic spikes since around 2009, where viral tweets propagate links exponentially, leading to short bursts of overload on targeted sites, particularly during real-time events. Doodles, interactive homepage features, have triggered up to 10-fold traffic increases; for instance, a 2012 Doodle honoring synthesizer inventor Bob Moog caused a substantial surge to the website, challenging its capacity to remain operational amid the influx. In contrast to the Slashdot effect's tech-focused, sustained surges, effects from social media platforms like are typically briefer, lasting minutes to hours, yet more prone to virality through retweets and algorithms. By 2025, and amplify this via recommendation engines, where a single or linking to an external site—such as a 2023 clip about an AI tool causing a "flood of "—can overload e-commerce or indie sites unprepared for the algorithmic push. These phenomena collectively fall under the broader "flash crowd" category in , defined as abrupt, high-volume access spikes that mimic legitimate interest but strain resources, differing by platform audience—Reddit's younger, diverse users versus Slashdot's tech enthusiasts—and lacking a unified "hug of death" label across all.

References

  1. http://catb.org/jargon/html/S/slashdot-effect.html
  2. https://www.computerhope.com/jargon/s/slashdot.htm
  3. https://slashdot.org/story/99/02/15/1249237/beware-of-the-slashdot-effect
  4. https://mason.gmu.edu/~lvera1/slashdot.html
  5. https://www.wired.com/2004/10/solution-for-slashdot-effect/
  6. https://www.linkedin.com/pulse/slashdot-still-relevant-2024-unveiling-current-state-legendary-kumar-y9u2c
  7. https://news.ycombinator.com/item?id=43242301
  8. https://users.soe.ucsc.edu/~scott/papers/MASCOTS03b.pdf
  9. http://www.catb.org/jargon/html/F/flash-crowd.html
  10. https://news.slashdot.org/story/17/10/03/2330258/slashdots-20th-anniversary-history-of-slashdot
  11. https://spectrum.ieee.org/the-slashdot-supremacy
  12. https://wordspy.com/words/slashdot-effect/
  13. https://internationalbanker.com/history-of-financial-crises/the-dotcom-bubble-burst-2000/
  14. http://www.catb.org/jargon/html/S/slashdot-effect.html
  15. https://linuxgazette.net/issue38/adler1.html
  16. https://slashdot.org/faq/editorial.shtml
  17. https://users.soe.ucsc.edu/~sbrandt/papers/MASCOTS03b.pdf
  18. https://ant.isi.edu/~johnh/PAPERS/Chen02a.pdf
  19. https://tldp.org/LDP/LG/issue38/adler2.html
  20. https://www.cs.princeton.edu/~mfreed/docs/coral-nsdi04.pdf
  21. https://ant.isi.edu/~johnh/PAPERS/Chen05a.pdf
  22. https://mice.cs.columbia.edu/getTechreport.php?techreportID=68&format=pdf
  23. https://users.soe.ucsc.edu/~elm/Papers/mascots03flash.pdf
  24. http://mice.cs.columbia.edu/getTechreport.php?techreportID=68&format=pdf&
  25. https://www.cs.princeton.edu/~mfreed/docs/flash-imc11.pdf
  26. http://www.dynamoo.com/diary/slashdot-effect.htm
  27. https://thenextweb.com/news/slashdot-15th-birthday-retrospectiveprofile
  28. https://tech.slashdot.org/story/24/01/03/0017242/25-years-since-the-first-real-slashdot-effect
  29. https://blog.codinghorror.com/the-popularity-tax/
  30. https://www.cbsnews.com/news/slashdotted-and-why-the-rich-get-richer/
  31. https://www.datacenterknowledge.com/business/blog-traffic-crashes-site-launches
  32. https://www.computer.org/csdl/journal/tq/2024/04/10380450/1Tpz79rXyqQ
  33. https://www.forbes.com/asap/2000/0221/043_print.html
  34. https://news.ycombinator.com/item?id=14338252
  35. https://news.ycombinator.com/item?id=5183983
  36. https://www.bloomberg.com/news/articles/2004-10-18/why-web-publishers-fear-a-little-sharing
  37. https://www.usenix.org/system/files/conference/icac14/icac14-paper-barna.pdf
  38. https://ucare.cs.uchicago.edu/pdf/socc16-cos.pdf
  39. https://www.cnet.com/tech/services-and-software/the-twitter-effect-possibilities-and-limits/
  40. https://science.slashdot.org/story/06/09/05/1259225/mining-neologisms-from-wikipedia
  41. https://www.nytimes.com/2011/05/16/business/media/16carr.html
  42. https://blog.cloudflare.com/moog-music-staying-online-when-google-doodles/
  43. https://www.cbsnews.com/news/the-drudge-effect-23-10-2007/
  44. https://techcrunch.com/2023/06/02/yc-backed-dumme-raises-3-4m-for-its-ai-video-editor-turns-long-form-youtube-videos-into-shorts/
  45. http://nms.lcs.mit.edu/papers/flash-crowds02.pdf
Add your contribution
Related Hubs
Contribute something
User Avatar
No comments yet.