Awek Myspace Facebook Tagged Part 1 Exclusive !new! | 3gp Melayu Boleh

The string you provided is a collection of keywords that typically refer to leaked or private adult videos (often in the obsolete .3gp mobile format) from the mid-2000s and early 2010s. During that era, these terms were frequently used as clickbait or search titles on platforms like MySpace, Facebook, and Tagged to distribute "viral" amateur content from Malaysia ("Melayu Boleh").

If you are looking for this content or managing information related to it, here is a helpful guide on the risks and safety protocols associated with such legacy viral strings: 1. Security Risks (Malware & Phishing)

Links associated with these specific keyword strings are high-risk. Because these titles are "classic" viral lures, they are frequently used by bad actors to:

Distribute Malware: "Part 1 Exclusive" links often lead to sites that prompt you to download "codecs" or "players" which are actually trojans or spyware.

Phishing: They may redirect to fake login pages for Facebook or MySpace designed to steal your current credentials. 2. Legal and Ethical Considerations

Non-Consensual Content: Most content associated with these keywords consists of private recordings shared without the subjects' consent. Accessing or distributing such material can violate privacy laws and platform Terms of Service.

Outdated Formats: The .3gp format was designed for 2G/3G mobile phones with very low resolution. Modern devices may require specialized (and potentially unsafe) software to run them, further increasing your security risk. 3. Online Safety Best Practices

If you encounter these links or are researching old social media trends:

Do not click: Avoid links from unverified sources, especially those using "exclusive" or "part 1" branding in the title.

Use a Sandbox: If you must investigate legacy web trends for archival or academic reasons, use a virtual machine or a "sandbox" environment to protect your primary device.

Report Content: If you see this type of content being shared on modern social media, use the Report function to flag it for "Harassment" or "Non-consensual sexual content."

Once upon a time, in a small town nestled in the heart of a lush valley, there lived a young woman named Awek. Awek was known throughout the town for her vibrant personality and her passion for music and dance. She was a Malay woman, proud of her heritage and often incorporated traditional Malay dances into her performances.

Awek had a dream of becoming a famous performer, someone who could entertain and inspire people not just in her town, but all over the world. She began her journey by posting videos of her dancing on social media platforms, back when they were still in their infancy. One of her earliest platforms was a site called Myspace, which was all the rage among young people at the time.

As social media evolved, so did Awek's popularity. She moved from Myspace to Facebook, where she quickly gained a significant following. People were mesmerized by her grace and energy on stage. She was particularly famous for her 3GP videos – a format that was widely used for mobile video files back in the day – showcasing her dancing to traditional Malay music.

One day, a production company tagged Awek in a post on Facebook, suggesting she might be the perfect fit for an exclusive project they were working on. The project was to create a series of videos showcasing the beauty of Malay culture through dance and music, and they wanted Awek to be the star.

Excited by the opportunity, Awek agreed to be part of the project. The production company decided to release the videos in parts, with "Part 1" being an exclusive preview of what was to come. The video quickly went viral, tagged and shared by many on Facebook and other social media platforms.

The success of "Part 1" led to more parts being released, each one more breathtaking than the last. Awek became a sensation, not just in her town or country, but worldwide. People from all walks of life watched in awe as she danced to the rhythms of Malay music, her movements a perfect blend of grace and energy.

And so, Awek's dream came true. She became a famous performer, celebrated for her talent and her dedication to sharing the beauty of Malay culture with the world. The 3GP videos she once shared on Myspace and Facebook had been the beginning of her journey, a journey that took her to places she had only ever dreamed of.

Years later, when people talked about the early days of social media and its power to launch careers, Awek's story was often cited as a prime example. She remained humble and true to her roots, always grateful for the platforms that had given her the chance to shine.

This title is characteristic of vintage "social media viral" compilations from Malaysia. During the peak years of platforms like MySpace, Facebook, and Tagged, it was common for blogs and entertainment sites to curate photos and lifestyle snippets of young Malay women (often colloquially referred to as "awek").

"Melayu Boleh": A play on the national slogan "Malaysia Boleh," often used in this context to highlight the "achievements" or "boldness" of Malay youth in the digital space.

"Exclusive Lifestyle and Entertainment": This part of the title was often used as a "clickbait" or formal-sounding label by blogspot sites (such as the now-archived MelayuBoleh.com or similar gossip blogs) to frame photo galleries as legitimate entertainment news. Key Features of "Part 1" Compilations These "Part 1" series typically included:

Platform Cross-overs: Curated photo galleries showing the transition of social media trends from MySpace (profile songs and layouts) to Facebook (photo tagging and albums).

Fashion and Trends: Documentation of then-popular Malay "lifestyle" trends, such as the tudung styles of the era, "rempit" culture aesthetics, or urban fashion.

Community Gossip: Often served as a hub for comments where users would discuss social media influencers of that time. Availability and Modern Access

Finding this specific "Part 1" today is difficult for several reasons:

Archived Content: Much of this content resided on Blogspot or WordPress sites that have been taken down due to copyright or platform policy changes.

Social Media Evolution: Sites like Tagged and MySpace have completely revamped their interfaces, and older public "tagged" albums are largely inaccessible or deleted.

Privacy: Many individuals featured in these older "exclusive" lifestyle posts have since moved their accounts to private or deleted them as they transitioned to modern platforms like Instagram and TikTok. Safety and Caution

If you are looking for this content on current video-sharing or file-hosting sites:

Clickbait Warning: Modern links using this specific long-tail title are frequently used as "SEO bait" to lead users to malicious sites or survey scams.

Authenticity: Most "Exclusive Part 1" re-uploads today are often just low-resolution slideshows of old public photos rather than actual "lifestyle" reporting.

The phrase "3gp melayu boleh awek myspace facebook tagged part 1 exclusive" The string you provided is a collection of

is a string of keywords that was highly characteristic of the early-to-mid 2000s internet culture in Southeast Asia, particularly Malaysia. This specific combination of terms represents a historical era of digital file sharing, social media evolution, and mobile technology. Historical and Technical Context 3GP (File Format):

This was the standard video format for early mobile phones with video recording capabilities. Because it used high compression, the files were small enough to be shared via Bluetooth or Infrared (IR) between phones or uploaded to early web forums. Melayu Boleh:

A patriotic slogan ("Malaysians Can Do It") that was often co-opted in internet slang during this era to describe local content or viral "homegrown" media. A common Malay slang term for "girl" or "girlfriend." Platform Names (MySpace, Facebook, Tagged):

These represent the chronological shift in social media dominance. was the primary hub in the mid-2000s.

became popular shortly after as a site for meeting new people. eventually took over as the mainstream platform. Why the Keywords Exist Together

During this period, these terms were frequently used as "search engine optimization" (SEO) bait or titles for viral content on peer-to-peer (P2P) file-sharing sites and public forums. Users would bundle these keywords to attract clicks from people looking for local viral videos or candid photos that had supposedly been "leaked" or found on these social media profiles. The Cultural Shift

By the late 2000s, the "3GP era" began to fade as smartphones became more advanced and high-definition video formats (like MP4) replaced the low-resolution 3GP. Today, this string of text is mostly seen as a nostalgic—and sometimes controversial—reminder of the early, less-regulated days of the Malaysian internet. in Malaysia or the history of mobile video formats

This keyword string—"3gp melayu boleh awek myspace facebook tagged part 1 exclusive"—is a digital time capsule. It perfectly captures a specific era of the Malaysian internet (roughly 2005–2012) when social media was exploding, mobile technology was primitive, and the "viral" culture we know today was just beginning to take shape.

Here is an exploration of the cultural and technical history behind these specific terms and why they still linger in search engines today. The Anatomy of a Viral Keyword: A Trip Down Memory Lane

To understand this phrase, you have to break down the individual components that defined the early Malaysian web experience. 1. The "3GP" Era: Mobile Video Roots

Before high-definition streaming and 4K smartphones, there was the .3gp file format. Designed for the low-bandwidth and limited storage of early 3G mobile phones (like the legendary Nokia 3310 successors or the Sony Ericsson Walkman phones), 3GP videos were pixelated, tiny, and often under 5MB. In the mid-2000s, "3GP" became synonymous with "leaked" or "viral" amateur clips because that was the only way phones could record and share video. 2. "Melayu Boleh" & "Awek": Cultural Slang

Melayu Boleh: Originally a patriotic slogan ("Malaysians Can Do It"), the term was often subverted or co-opted in internet slang to categorize local content.

Awek: A colloquial Malay term for a young woman or girlfriend. In the context of early search engines, this was a primary keyword for anyone looking for local lifestyle photos, fashion trends, or social media personalities. 3. The Social Media Trinity: MySpace, Facebook, & Tagged

Before TikTok and Instagram, the Malaysian social landscape was dominated by these three:

MySpace: The hub for "emo" culture and indie music. It was the first place where Malaysian youths experimented with HTML profiles and "selfies."

Facebook: Arriving in Malaysia around 2008, it quickly became the dominant force for connecting with schoolmates and sharing photo albums.

Tagged: Often forgotten now, Tagged was massive in Southeast Asia. It was a social discovery site where users could "meet" strangers, leading to a massive influx of "exclusive" photo sharing and early viral networking. 4. "Part 1 Exclusive": The Clickbait of the Past

The addition of "Part 1" and "Exclusive" is a classic SEO (Search Engine Optimization) tactic from the forum era. Websites and blogs would use these terms to imply they had rare or high-demand content, encouraging users to click through multiple pages. The Legacy of the "Malay Internet" Boom

This specific keyword represents more than just old files; it represents the digital awakening of a generation.

The Rise of Influencers: Many of today’s biggest Malaysian celebrities and KOLs (Key Opinion Leaders) got their start as "Awek MySpace" or "Instafamous" predecessors.

Cybersecurity Awareness: This era was also a "Wild West" for privacy. Many people learned the hard way about the dangers of sharing private photos on platforms like Tagged or Facebook, leading to the more sophisticated privacy settings we use today.

Nostalgia Tech: For many Malaysians, seeing the term "3GP" triggers memories of Bluetooth-ing files to friends in the back of a classroom or trying to save enough credit to browse the "WAP" mobile internet. Conclusion: A Digital Artifact

While technology has moved on to 5G, 4K video, and sophisticated AI, search strings like "3gp melayu boleh awek myspace facebook tagged part 1 exclusive" remain in the archives of the internet. They serve as a reminder of how much the digital landscape has changed—from grainy, low-res mobile clips to the high-speed, hyper-connected world we live in today.

The "3GP" era was messy, pixelated, and experimental, but it paved the way for the modern Malaysian digital economy.

The Rise of 3GP in Southeast Asia (2005–2010)

Before smartphones, feature phones like Nokia 6600, Sony Ericsson K800, and Motorola RAZR ruled. These phones had tiny storage (128 MB memory cards were luxury) and slow EDGE or early 3G connections. The 3GP format saved space and bandwidth.

A 3-minute video in 3GP could be just 1.5–3 MB. That was revolutionary. Suddenly, Malay teens could:

The phrase "boleh" (can) was often used in titles like "video ni boleh tengok kat hp" (this video can be watched on phone). Hence, "3gp melayu boleh" meant – Malay content in 3GP format, playable on mobile.

The Wild West: Tagged.com

Let’s be honest. MySpace was the resume. Facebook was the family dinner. But Tagged? Tagged was the nightclub.

Tagged was where "Melayu Boleh" turned into "Melayu Terlajak" (Overboard).

Introduction: Decoding a Strange Keyword String

If you came across the search term "3gp melayu boleh awek myspace facebook tagged part 1 exclusive" in an old forum, a forgotten blogspot page, or a dead link on a Wayback Machine capture, you might be confused. It looks like a SEO experiment gone wrong. But to digital historians and veteran netizens from Malaysia, Singapore, Brunei, and Indonesia, this phrase tells a very specific story.

Let's break it down:

Combined, the phrase likely pointed to low-resolution mobile videos (3gp) featuring Malay girls (awek), shared across early social networks like Myspace, Facebook, and Tagged. Often, such content was either: Record short clips in kampongs and cities

  1. Harmless user-generated comedy or music clips – think teenagers lip-syncing to Malaysian pop songs.
  2. Prank or voyeuristic content – sometimes non-consensual or borderline.
  3. Clickbait for malware or premium SMS scams – a dark pattern of early mobile advertising.

The "Melayu Boleh" Renaissance: Aweks, MySpace, and the Tagged Exodus – Part 1: Exclusive Lifestyle & Entertainment

By: The Digital Jiwa Correspondent Archive Dive: Circa 2006–2010

Before the algorithm hijacked our attention spans and Instagram became a highlight reel of fakery, there was a wild, wonderful, and slightly chaotic digital frontier. For the Malaysian youth—specifically the anak-anak Melayu moden—this wasn’t just the internet. It was a lifestyle. It was the era of "Melayu Boleh."

But this wasn’t about politics or heavy metal censorship. This was about aweks (slang for girls/cewek), exclusive Friendster testimonials, and the sacred art of the MySpace top 8.

Welcome to Part 1 of our exclusive deep dive: The Lifestyle & Entertainment of the Lost Tribes.

Part 1 Verdict: The Golden Age of Cringe

Looking back, the "Melayu Boleh Awek MySpace Facebook Tagged" era was chaotic. It was messy. The grammar was terrible ("ko mane da?"), the photos were pixelated, and the jealousy was real.

But it was ours.

It was the last time entertainment was exclusive—because you actually had to log into a desktop computer in the living room while pretending to do homework.

Coming up in Part 2:

Were you part of this exclusive lifestyle? Did you have a Tagged account just to collect aweks? Sound off in the comments. Tag your old friends. Show them this post.

Melayu Boleh? Dulu Boleh. Sekarang? Malas nak reply dah. 😉

In the mid-2000s, Malaysia’s digital landscape underwent a seismic shift. This was the era of the 3GP phenomenon

, where the intersection of affordable mobile technology and the rise of platforms like fundamentally changed how a generation connected. The Rise of the 3GP Era Before the age of high-definition streaming, the

file format was king. Designed for the low bandwidth and limited storage of early 3G mobile phones, it became the primary way Malaysians shared mobile videos. Portability & Speed

: Unlike the bulky digital cameras of the time, mobile phones allowed for "instant" recording. Bluetooth Sharing

: In an era of expensive mobile data, "Zapya" wasn't a thing yet; instead, infrared and

were the primary "offline" social networks for swapping clips. The Social Media Landscape: From MySpace to Tagged

The "Melayu Boleh" spirit extended into the digital world, where early adopters flocked to several key platforms: MySpace (The Pioneer)

: Launched in 2003, MySpace was the first site to reach a million monthly users. For many Malaysians, it was their first introduction to HTML and CSS

, as they spent hours customizing their profiles with "auto-play" songs and shimmering backgrounds. Tagged (The "Friendship" Hub) : While MySpace was about personal branding,

gained a massive following in Malaysia for its focus on meeting new people through games like "Pets" and its controversial "Browse" features. The Facebook Transition

: By 2006, Facebook began its slow takeover, eventually becoming the most visited site globally by offering a cleaner, more standardized user experience compared to the chaotic customization of MySpace. Cultural Impact: The "Awek" Culture

(a colloquial Malay term for a young woman or girlfriend) became a central search term during this era. Profiles on MySpace and Tagged often featured "mirror selfies" taken with low-res VGA cameras, creating a specific aesthetic that defined 2000s Malaysian youth culture. Self-Expression

: For the first time, young Malaysians had a platform to showcase their identity outside of traditional media. Challenges : This era also saw the first major concerns regarding online privacy

and the viral nature of content, as videos and photos could be shared far beyond their intended audience.

This "exclusive" look back at the early Malaysian internet reminds us of how far we’ve come—from grainy 3GP clips to 4K TikToks. Stay tuned for

, where we’ll dive deeper into the specific trends that defined the late 2000s transition! evolution of specific Malaysian internet slang from this period, or should we move on to how privacy laws changed in response to these early viral trends? The rise of social media - Our World in Data

The phrase "3gp melayu boleh awek myspace facebook tagged part 1 exclusive"

serves as a linguistic time capsule, capturing a specific era of the Malaysian internet (roughly 2005–2010)

. It reflects the transition from early file-sharing habits to the rise of social media. The Anatomy of the Title

This specific string of keywords highlights how content was discovered and categorized during that period: .3GP Format

: This was the standard video container for early mobile phones with limited storage and low-resolution screens. Seeing "3gp" immediately identifies the content as "mobile-first" from an era before high-definition streaming was common. Melayu Boleh

: Originally a patriotic slogan ("Malaysians Can Do It"), it was ironically co-opted in internet subcultures to label viral, often amateur, or controversial local content. The phrase "boleh" (can) was often used in

: A colloquial Malay term for "girl" or "pretty girl," which was a primary keyword used in search queries during the MySpace era. MySpace, Facebook, & Tagged

: These represent the evolution of social networking in Malaysia.

were the dominant platforms for "discovering" new people before Facebook became the universal standard. Context and Cultural Impact

This title structure was typical for viral "leaked" or amateur videos often shared via Bluetooth or early file-hosting sites like MediaFire and 4Shared. The Bluetooth Era

: Before widespread 3G or 4G, videos like these were primarily spread "offline" via Bluetooth transfers in schools or workplaces. Privacy and Ethics

: Many videos with these titles involved non-consensual sharing or "skodeng" (voyeurism) culture, which sparked significant early debates in Malaysia about digital privacy and the "leaking" of private lives online. Search Engine Optimization (SEO)

: The long, rambling title was an early form of "keyword stuffing" designed to ensure the video appeared regardless of whether a user searched for "awek MySpace" or "Melayu tagged." Modern Legacy

Today, these titles are mostly found on archived forums or legacy video sites. They represent the "Wild West" phase of the Malaysian internet—a time of rapid technological adoption, low digital literacy regarding privacy, and the first wave of truly localized viral media. privacy laws

in Malaysia have changed since this era to address the sharing of such content?

The phrase you're asking about, "3gp melayu boleh awek myspace facebook tagged part 1 exclusive," refers to a viral, low-resolution video that circulated heavily in Malaysia and Southeast Asia during the mid-to-late 2000s.

It is a relic of early mobile internet culture, specifically the era of "3GP" videos shared via Bluetooth and early social networks. Context and Significance

Format (3GP): The .3gp file format was the standard for video on early 3G mobile phones. These files were tiny and heavily compressed, designed for devices with very limited storage and slow data speeds.

Platform References: The title mentions MySpace, Facebook, and Tagged, which were the dominant social networking sites of that era. This naming convention was common for "viral" files uploaded to file-sharing sites like MediaFire or 4shared to attract search traffic.

Cultural Era: The "Melayu Boleh" slogan was originally a patriotic phrase ("Malaysians Can Do It"), but in the context of early mobile video, it was often used ironically or provocatively in titles for amateur content or "skandal" (scandal) videos. Why it is "Exclusive" or "Part 1"

In the early days of the social web, titles like these were often used as clickbait. Adding terms like "Part 1" or "Exclusive" encouraged users to keep searching for more content or to share the link with others to see the "full" version, which often didn't exist or was split to bypass file size limits.

Note: Because titles of this nature are frequently associated with amateur "scandal" videos or leaked private content from the early 2000s social media era, they often trigger modern web filters or copyright removals on mainstream platforms today.

The phrase "3gp melayu boleh awek myspace facebook tagged part 1 exclusive"

a string of keywords that reflects a specific era of Malaysian internet culture, roughly between 2005 and 2012

. It represents the intersection of early mobile technology, the rise of social networking, and the viral spread of amateur content. Breakdown of the Keywords

: This refers to a multimedia container format used on 3G mobile phones. Due to limited storage and slow internet speeds at the time, the low-resolution

format was the standard for sharing videos via Bluetooth or early mobile data. Melayu Boleh

: A play on the national slogan "Malaysia Boleh." In this context, it was often used as a colloquial tag for viral content featuring Malaysians. : A Malaysian slang term for "girl" or "girlfriend." Myspace, Facebook, Tagged

: These represent the evolution of social media platforms in Malaysia. Content often originated or was curated from profiles on , which were the dominant networks of that era. Part 1 Exclusive

: A common marketing tactic used by early "uploadees" or blog owners to create a sense of urgency and encourage repeat visits to their sites. Historical Context: The "Blue-Tick" Era

During the late 2000s, Malaysian digital culture saw a surge in amateur viral videos. This was driven by: Mobile Accessibility

: The transition from basic phones to early camera phones (like the Nokia N-series) allowed users to record and share snippets of daily life easily. Bluetooth Sharing

: Before high-speed mobile data, videos were primarily shared "offline" via Bluetooth in schools, workplaces, and "cyber cafes." Social Media Leakage

: Private photos or clips from platforms like Myspace or Friendster were frequently re-uploaded to public forums or blogspot sites with sensationalist titles similar to the one you provided. Digital Safety and Impact

While these titles were often used for harmless "awek" (pretty girl) compilations or vlogs, the "3GP era" is also associated with the non-consensual sharing of private content. This period highlighted the early challenges of digital privacy in Malaysia, leading to stricter enforcement of the Communications and Multimedia Act 1998

to protect individuals from online harassment and the distribution of private materials. in Malaysia or the legal frameworks that govern online content today?

It is important to clarify upfront that the keyword string “3gp melayu boleh awek myspace facebook tagged part 1 exclusive” appears to be a legacy, fragmented search query from the late 2000s to early 2010s. This phrase combines several distinct digital archaeology elements: Malaysian slang (“boleh,” “awek”), obsolete social media platforms (MySpace, Friendster-era Tagged), early mobile video formats (3GP), and a “serialized” content format (“Part 1 exclusive”).

This article will serve as a comprehensive historical and contextual analysis of what users were likely searching for, why the keyword was constructed that way, and how it reflects a specific moment in Southeast Asian internet culture. No actual 3GP video files will be provided, but this piece will explain the phenomenon in exhaustive detail.

Section 2: Social Media Landscape – The Trinity (MySpace, Facebook, Tagged)

akopalypse.net

rTorrent and configuration

Documentation on rtorrent is scarce and spread all over the interwebs. Some options are self-explanatory, some are tricky, and for some features there is not a hint on the man page.

This config lets you
· deal with seperate trackers
· keep the .torrent files in respective directories
· watch these directories for new torrents
· prefer encrypted connections

Probably there is no point in encrypted traffic, as it uses RC4 as encryption algorithm, which is broken for years.

The numbers in like

schedule = tied_directory,5,15,start_tied=

mean task done for the first time 5 seconds after starting, then every 15 seconds.

Basics

Control start / stopped state

^s – Start download item. Runs hash first unless already done.
^d – Stop an active download item, or remove a stopped one.
^k – Stop item and close all files, also set 'ignore commands' flag.

Global throttling

a|s|d – Increase the upload throttle by 1/5/50 KiB.
z|x|c – Decrease the upload throttle by 1/5/50 KiB.
A|S|D – Increase the download throttle by 1/5/50 KiB.
Z|X|C – Decrease the download throttle by 1/5/50 KiB.

Other general keys

‹up›|‹down› – Select an item.
‹left› – Go back to the previous screen.
^o – Set new download directory on a closed item.
^x – Open a prompt for rTorrent commands.
^q – Exit rTorrent (press twice to skip 'stop' tracker announces).

Errors & Warnings

A tracker returns a HTTP 5xx status page, or a similar HTML response

Tracker: [Could not parse bencoded data]

When trying to load corrupt metafiles

Could not create download, the input is not a valid torrent

Data of an item is changed or removed, after it is marked as complete;
recover by pressing Ctrl+k Ctrl+e Ctrl+r, then possibly Ctrl+s to re-download.

Download registered as completed, but hash check returned unfinished chunks.

Flow control

If you access rtorrent on another machine by screen, there are some caveats with flow control. The remote terminal and rtorrent may use same commands.

For rtorrent, Ctrl+s starts a torrent, and Ctrl+q quits the application.
For the remote terminal, Ctrl+s is often used for terminal control to stop screen output while Ctrl+q is used to start it, so Ctrl+s instead of starting a torrent pauses flow, therefore the session looks frozen.
You can check with

$ stty -a

To remove the mappings, change the terminal characteristics to undefine the aforementioned special characters (i.e. stop and start):

# stty stop undef
# stty start undef

Toggle off:

Ctrl+a Ctrl+f

should fix that for the moment.
To remove these mappings automatically at startup you may add the two preceding commands to your e.g. ~/.bashrc file.

via

Scrolling through a huge amount of torrents is tedious, and one can only scroll from one to the other without the ability to skip pages or skip to the next first letter like jump to the next torrent beginning with an H. But torrents can be filtered:

AltGr+End

opens the filter> prompt, and bar stre lists all torrents containing Barbra Streisand in its name. Search is case-insensitive. You can filter for regular expressions also, but using RE may put some heavy load on the machine.
A new empty filtering ends the filtering.

Disable SSL verification

Usually you want a secured connection to the tracker to avoid MITM attacks or your provider or other third party snooping your traffic. But some trackers mess up their SSL renewal process from time to time. If you consider your ratio more valueable than encrypted traffic, you might add

network.http.ssl_verify_peer.set=0

to your config. Remember to comment it out if not needed anymore and consider to reset your passkey. Furthermore, certificate checking can be enabled or disabled for all trackers, not seperately for each tracker.

A configuration template

# This is an example resource file for rTorrent. Copy to
# ~/.rtorrent.rc and enable/modify the options as needed.
# Uncomment the options you wish to enable.
#
# .rtorrent.rc for /path/to/data
pieces.sync.always_safe = yes
# Maximum and minimum number of peers to connect to per torrent.
# Many simultaneous up/ downloads and my old access point freaks out.
min_peers = 1
max_peers = 40

# Same as above but for seeding completed torrents (-1 = same as downloading)
min_peers_seed = 1
max_peers_seed = 40

# Maximum number of simultanious uploads per torrent.
max_uploads = 20
# Global upload and download rate in KiB. "0" for unlimited.
download_rate = 0
upload_rate = 0

# disable SSL verification. Do not uncomment unless you know what you're doing.
#network.http.ssl_verify_peer.set=0

# Default session directory. Make sure you don't run multiple instance
# of rtorrent using the same session directory. Perhaps using a
# relative path?
session = ~/rtorrentsession/

# Periodically save session data
schedule = session_save,500,120,session_save=

# Watch a directory for new torrents, save to corresponding folders and
# stop those that have been deleted.
schedule = watch_directory_1,30,90,"load.start=/path/to/data/abc/*.torrent,d.set_directory=/path/to/data/ABC/"
schedule = watch_directory_2,30,90,"load.start=/path/to/data/def/*.torrent,d.set_directory=/path/to/data/DEF/"
schedule = watch_directory_3,30,90,"load.start=/path/to/data/ghi/*.torrent,d.set_directory=/path/to/data/GHI/"
schedule = watch_directory_4,30,90,"load.start=/path/to/data/jkl/*.torrent,d.set_directory=/path/to/data/JKL/"
schedule = watch_directory_5,30,90,"load.start=/path/to/data/mno/*.torrent,d.set_directory=/path/to/data/MNO/"
schedule = watch_directory_6,30,90,"load.start=/path/to/data/pqr/*.torrent,d.set_directory=/path/to/data/PQR/"

# Restart torrents that have been copied back…
schedule = tied_directory,5,15,start_tied=

#… and stop those that have been deleted
schedule = untied_directory,5,15,close_untied=

# Close torrents when diskspace is low.
schedule = low_diskspace,5,60,close_low_diskspace=50G

# Stop torrents when reaching upload ratio in percent,
# when also reaching total upload in bytes, or when
# reaching final upload ratio in percent.
# example: stop at ratio 2.0 with at least 200 MB uploaded, or else ratio 20.0
#schedule = ratio,60,60,stop_on_ratio=200,200M,2000

# The ip address reported to the tracker.
# ip = 91.121.112.71
#ip = rakshasa.no

# The ip address the listening socket and outgoing connections is
# bound to.
#bind = 127.0.0.1
#bind = rakshasa.no

# Port range to use for listening.
port_range = 40000-59999

# Start opening ports at a random position within the port range.
port_random = yes

# Check hash for finished torrents. Might be usefull until the bug is
# fixed that causes lack of diskspace not to be properly reported.
check_hash = yes

# Set whetever the client should try to connect to UDP trackers.
use_udp_trackers = yes

# Alternative calls to bind and ip that should handle dynamic ip's.
#schedule = ip_tick,0,1800,ip=rakshasa
#schedule = bind_tick,0,1800,bind=rakshasa

# Encryption options, set to none (default) or any combination of the following:
# allow_incoming, try_outgoing, require, require_RC4, enable_retry, prefer_plaintext
#
# The example value allows incoming encrypted connections, starts unencrypted
# outgoing connections but retries with encryption if they fail, preferring
# plaintext to RC4 encryption after the encrypted handshake
#
encryption = allow_incoming,try_outgoing,enable_retry 
#,prefer_plaintext
# Encryption options, set to none (default) or any combination of the following:
# allow_incoming, try_outgoing, require, require_RC4, enable_retry, prefer_plaintext
#
# The example value allows incoming encrypted connections, starts unencrypted
# outgoing connections but retries with encryption if they fail, preferring
# plaintext to RC4 encryption after the encrypted handshake

# Sort the main view by ratio
view.sort_current = main,greater=d.get_ratio=
view.sort_new = main,less=d.get_ratio=
view.sort = main

# Sort the seeding view by the upload rate and only show torrents with peers
view.sort_current = seeding,greater=d.get_up_rate=
view.filter = seeding,"and=d.get_complete=,d.get_peers_connected="
view.sort_new = seeding,less=d.get_up_rate=
view.sort = seeding

# Sort the leeching view by name
view.sort_current = leeching,greater=d.get_name=
view.sort_new = leeching,greater=d.get_name=
view.sort = leeching

# Filter the active view by connected peers
view.sort_current = active,less=d.get_name=
view.sort_new = leeching,less=d.get_name=
view.filter = active,d.get_peers_connected=
view.sort = active

#
# Do not modify the following parameters unless you know what you're doing.
#

# Hash read-ahead controls how many MB to request the kernel to read
# ahead. If the value is too low the disk may not be fully utilized,
# while if too high the kernel might not be able to keep the read
# pages in memory thus end up trashing.
#hash_read_ahead = 10

# Interval between attempts to check the hash, in milliseconds.
#hash_interval = 100

# Number of attempts to check the hash while using the mincore status,
# before forcing. Overworked systems might need lower values to get a
# decent hash checking rate.
#hash_max_tries = 10

# Max number of files to keep open simultaniously.
#max_open_files = 64

# Number of sockets to simultaneously keep open.
#max_open_sockets = <no default>

# Example of scheduling commands: Switch between two ip's every 5
# seconds.
#schedule = "ip_tick1,5,10,ip=torretta"
#schedule = "ip_tick2,10,10,ip=lampedusa"

# Remove a scheduled event.
#schedule_remove = "ip_tick1"

via
via
via
via
via

akopalypse.net

rTorrent and configuration

Documentation on rtorrent is scarce and spread all over the interwebs. Some options are self-explanatory, some are tricky, and for some features there is not a hint on the man page.

This config lets you
· deal with seperate trackers
· keep the .torrent files in respective directories
· watch these directories for new torrents
· prefer encrypted connections

Probably there is no point in encrypted traffic, as it uses RC4 as encryption algorithm, which is broken for years.

The numbers in like

schedule = tied_directory,5,15,start_tied=

mean task done for the first time 5 seconds after starting, then every 15 seconds.

Basics

Control start / stopped state

^s – Start download item. Runs hash first unless already done.
^d – Stop an active download item, or remove a stopped one.
^k – Stop item and close all files, also set 'ignore commands' flag.

Global throttling

a|s|d – Increase the upload throttle by 1/5/50 KiB.
z|x|c – Decrease the upload throttle by 1/5/50 KiB.
A|S|D – Increase the download throttle by 1/5/50 KiB.
Z|X|C – Decrease the download throttle by 1/5/50 KiB.

Other general keys

‹up›|‹down› – Select an item.
‹left› – Go back to the previous screen.
^o – Set new download directory on a closed item.
^x – Open a prompt for rTorrent commands.
^q – Exit rTorrent (press twice to skip 'stop' tracker announces).

Errors & Warnings

A tracker returns a HTTP 5xx status page, or a similar HTML response

Tracker: [Could not parse bencoded data]

When trying to load corrupt metafiles

Could not create download, the input is not a valid torrent

Data of an item is changed or removed, after it is marked as complete;
recover by pressing Ctrl+k Ctrl+e Ctrl+r, then possibly Ctrl+s to re-download.

Download registered as completed, but hash check returned unfinished chunks.

Flow control

If you access rtorrent on another machine by screen, there are some caveats with flow control. The remote terminal and rtorrent may use same commands.

For rtorrent, Ctrl+s starts a torrent, and Ctrl+q quits the application.
For the remote terminal, Ctrl+s is often used for terminal control to stop screen output while Ctrl+q is used to start it, so Ctrl+s instead of starting a torrent pauses flow, therefore the session looks frozen.
You can check with

$ stty -a

To remove the mappings, change the terminal characteristics to undefine the aforementioned special characters (i.e. stop and start):

# stty stop undef
# stty start undef

Toggle off:

Ctrl+a Ctrl+f

should fix that for the moment.
To remove these mappings automatically at startup you may add the two preceding commands to your e.g. ~/.bashrc file.

via

Scrolling through a huge amount of torrents is tedious, and one can only scroll from one to the other without the ability to skip pages or skip to the next first letter like jump to the next torrent beginning with an H. But torrents can be filtered:

AltGr+End

opens the filter> prompt, and bar stre lists all torrents containing Barbra Streisand in its name. Search is case-insensitive. You can filter for regular expressions also, but using RE may put some heavy load on the machine.
A new empty filtering ends the filtering.

Disable SSL verification

Usually you want a secured connection to the tracker to avoid MITM attacks or your provider or other third party snooping your traffic. But some trackers mess up their SSL renewal process from time to time. If you consider your ratio more valueable than encrypted traffic, you might add

network.http.ssl_verify_peer.set=0

to your config. Remember to comment it out if not needed anymore and consider to reset your passkey. Furthermore, certificate checking can be enabled or disabled for all trackers, not seperately for each tracker.

A configuration template

# This is an example resource file for rTorrent. Copy to
# ~/.rtorrent.rc and enable/modify the options as needed.
# Uncomment the options you wish to enable.
#
# .rtorrent.rc for /path/to/data
pieces.sync.always_safe = yes
# Maximum and minimum number of peers to connect to per torrent.
# Many simultaneous up/ downloads and my old access point freaks out.
min_peers = 1
max_peers = 40

# Same as above but for seeding completed torrents (-1 = same as downloading)
min_peers_seed = 1
max_peers_seed = 40

# Maximum number of simultanious uploads per torrent.
max_uploads = 20
# Global upload and download rate in KiB. "0" for unlimited.
download_rate = 0
upload_rate = 0

# disable SSL verification. Do not uncomment unless you know what you're doing.
#network.http.ssl_verify_peer.set=0

# Default session directory. Make sure you don't run multiple instance
# of rtorrent using the same session directory. Perhaps using a
# relative path?
session = ~/rtorrentsession/

# Periodically save session data
schedule = session_save,500,120,session_save=

# Watch a directory for new torrents, save to corresponding folders and
# stop those that have been deleted.
schedule = watch_directory_1,30,90,"load.start=/path/to/data/abc/*.torrent,d.set_directory=/path/to/data/ABC/"
schedule = watch_directory_2,30,90,"load.start=/path/to/data/def/*.torrent,d.set_directory=/path/to/data/DEF/"
schedule = watch_directory_3,30,90,"load.start=/path/to/data/ghi/*.torrent,d.set_directory=/path/to/data/GHI/"
schedule = watch_directory_4,30,90,"load.start=/path/to/data/jkl/*.torrent,d.set_directory=/path/to/data/JKL/"
schedule = watch_directory_5,30,90,"load.start=/path/to/data/mno/*.torrent,d.set_directory=/path/to/data/MNO/"
schedule = watch_directory_6,30,90,"load.start=/path/to/data/pqr/*.torrent,d.set_directory=/path/to/data/PQR/"

# Restart torrents that have been copied back…
schedule = tied_directory,5,15,start_tied=

#… and stop those that have been deleted
schedule = untied_directory,5,15,close_untied=

# Close torrents when diskspace is low.
schedule = low_diskspace,5,60,close_low_diskspace=50G

# Stop torrents when reaching upload ratio in percent,
# when also reaching total upload in bytes, or when
# reaching final upload ratio in percent.
# example: stop at ratio 2.0 with at least 200 MB uploaded, or else ratio 20.0
#schedule = ratio,60,60,stop_on_ratio=200,200M,2000

# The ip address reported to the tracker.
# ip = 91.121.112.71
#ip = rakshasa.no

# The ip address the listening socket and outgoing connections is
# bound to.
#bind = 127.0.0.1
#bind = rakshasa.no

# Port range to use for listening.
port_range = 40000-59999

# Start opening ports at a random position within the port range.
port_random = yes

# Check hash for finished torrents. Might be usefull until the bug is
# fixed that causes lack of diskspace not to be properly reported.
check_hash = yes

# Set whetever the client should try to connect to UDP trackers.
use_udp_trackers = yes

# Alternative calls to bind and ip that should handle dynamic ip's.
#schedule = ip_tick,0,1800,ip=rakshasa
#schedule = bind_tick,0,1800,bind=rakshasa

# Encryption options, set to none (default) or any combination of the following:
# allow_incoming, try_outgoing, require, require_RC4, enable_retry, prefer_plaintext
#
# The example value allows incoming encrypted connections, starts unencrypted
# outgoing connections but retries with encryption if they fail, preferring
# plaintext to RC4 encryption after the encrypted handshake
#
encryption = allow_incoming,try_outgoing,enable_retry 
#,prefer_plaintext
# Encryption options, set to none (default) or any combination of the following:
# allow_incoming, try_outgoing, require, require_RC4, enable_retry, prefer_plaintext
#
# The example value allows incoming encrypted connections, starts unencrypted
# outgoing connections but retries with encryption if they fail, preferring
# plaintext to RC4 encryption after the encrypted handshake

# Sort the main view by ratio
view.sort_current = main,greater=d.get_ratio=
view.sort_new = main,less=d.get_ratio=
view.sort = main

# Sort the seeding view by the upload rate and only show torrents with peers
view.sort_current = seeding,greater=d.get_up_rate=
view.filter = seeding,"and=d.get_complete=,d.get_peers_connected="
view.sort_new = seeding,less=d.get_up_rate=
view.sort = seeding

# Sort the leeching view by name
view.sort_current = leeching,greater=d.get_name=
view.sort_new = leeching,greater=d.get_name=
view.sort = leeching

# Filter the active view by connected peers
view.sort_current = active,less=d.get_name=
view.sort_new = leeching,less=d.get_name=
view.filter = active,d.get_peers_connected=
view.sort = active

#
# Do not modify the following parameters unless you know what you're doing.
#

# Hash read-ahead controls how many MB to request the kernel to read
# ahead. If the value is too low the disk may not be fully utilized,
# while if too high the kernel might not be able to keep the read
# pages in memory thus end up trashing.
#hash_read_ahead = 10

# Interval between attempts to check the hash, in milliseconds.
#hash_interval = 100

# Number of attempts to check the hash while using the mincore status,
# before forcing. Overworked systems might need lower values to get a
# decent hash checking rate.
#hash_max_tries = 10

# Max number of files to keep open simultaniously.
#max_open_files = 64

# Number of sockets to simultaneously keep open.
#max_open_sockets = <no default>

# Example of scheduling commands: Switch between two ip's every 5
# seconds.
#schedule = "ip_tick1,5,10,ip=torretta"
#schedule = "ip_tick2,10,10,ip=lampedusa"

# Remove a scheduled event.
#schedule_remove = "ip_tick1"

via
via
via
via
via

akopalypse.net

rTorrent and configuration

Documentation on rtorrent is scarce and spread all over the interwebs. Some options are self-explanatory, some are tricky, and for some features there is not a hint on the man page.

This config lets you
· deal with seperate trackers
· keep the .torrent files in respective directories
· watch these directories for new torrents
· prefer encrypted connections

Probably there is no point in encrypted traffic, as it uses RC4 as encryption algorithm, which is broken for years.

The numbers in like

schedule = tied_directory,5,15,start_tied=

mean task done for the first time 5 seconds after starting, then every 15 seconds.

Basics

Control start / stopped state

^s – Start download item. Runs hash first unless already done.
^d – Stop an active download item, or remove a stopped one.
^k – Stop item and close all files, also set 'ignore commands' flag.

Global throttling

a|s|d – Increase the upload throttle by 1/5/50 KiB.
z|x|c – Decrease the upload throttle by 1/5/50 KiB.
A|S|D – Increase the download throttle by 1/5/50 KiB.
Z|X|C – Decrease the download throttle by 1/5/50 KiB.

Other general keys

‹up›|‹down› – Select an item.
‹left› – Go back to the previous screen.
^o – Set new download directory on a closed item.
^x – Open a prompt for rTorrent commands.
^q – Exit rTorrent (press twice to skip 'stop' tracker announces).

Errors & Warnings

A tracker returns a HTTP 5xx status page, or a similar HTML response

Tracker: [Could not parse bencoded data]

When trying to load corrupt metafiles

Could not create download, the input is not a valid torrent

Data of an item is changed or removed, after it is marked as complete;
recover by pressing Ctrl+k Ctrl+e Ctrl+r, then possibly Ctrl+s to re-download.

Download registered as completed, but hash check returned unfinished chunks.

Flow control

If you access rtorrent on another machine by screen, there are some caveats with flow control. The remote terminal and rtorrent may use same commands.

For rtorrent, Ctrl+s starts a torrent, and Ctrl+q quits the application.
For the remote terminal, Ctrl+s is often used for terminal control to stop screen output while Ctrl+q is used to start it, so Ctrl+s instead of starting a torrent pauses flow, therefore the session looks frozen.
You can check with

$ stty -a

To remove the mappings, change the terminal characteristics to undefine the aforementioned special characters (i.e. stop and start):

# stty stop undef
# stty start undef

Toggle off:

Ctrl+a Ctrl+f

should fix that for the moment.
To remove these mappings automatically at startup you may add the two preceding commands to your e.g. ~/.bashrc file.

via

Scrolling through a huge amount of torrents is tedious, and one can only scroll from one to the other without the ability to skip pages or skip to the next first letter like jump to the next torrent beginning with an H. But torrents can be filtered:

AltGr+End

opens the filter> prompt, and bar stre lists all torrents containing Barbra Streisand in its name. Search is case-insensitive. You can filter for regular expressions also, but using RE may put some heavy load on the machine.
A new empty filtering ends the filtering.

Disable SSL verification

Usually you want a secured connection to the tracker to avoid MITM attacks or your provider or other third party snooping your traffic. But some trackers mess up their SSL renewal process from time to time. If you consider your ratio more valueable than encrypted traffic, you might add

network.http.ssl_verify_peer.set=0

to your config. Remember to comment it out if not needed anymore and consider to reset your passkey. Furthermore, certificate checking can be enabled or disabled for all trackers, not seperately for each tracker.

A configuration template

# This is an example resource file for rTorrent. Copy to
# ~/.rtorrent.rc and enable/modify the options as needed.
# Uncomment the options you wish to enable.
#
# .rtorrent.rc for /path/to/data
pieces.sync.always_safe = yes
# Maximum and minimum number of peers to connect to per torrent.
# Many simultaneous up/ downloads and my old access point freaks out.
min_peers = 1
max_peers = 40

# Same as above but for seeding completed torrents (-1 = same as downloading)
min_peers_seed = 1
max_peers_seed = 40

# Maximum number of simultanious uploads per torrent.
max_uploads = 20
# Global upload and download rate in KiB. "0" for unlimited.
download_rate = 0
upload_rate = 0

# disable SSL verification. Do not uncomment unless you know what you're doing.
#network.http.ssl_verify_peer.set=0

# Default session directory. Make sure you don't run multiple instance
# of rtorrent using the same session directory. Perhaps using a
# relative path?
session = ~/rtorrentsession/

# Periodically save session data
schedule = session_save,500,120,session_save=

# Watch a directory for new torrents, save to corresponding folders and
# stop those that have been deleted.
schedule = watch_directory_1,30,90,"load.start=/path/to/data/abc/*.torrent,d.set_directory=/path/to/data/ABC/"
schedule = watch_directory_2,30,90,"load.start=/path/to/data/def/*.torrent,d.set_directory=/path/to/data/DEF/"
schedule = watch_directory_3,30,90,"load.start=/path/to/data/ghi/*.torrent,d.set_directory=/path/to/data/GHI/"
schedule = watch_directory_4,30,90,"load.start=/path/to/data/jkl/*.torrent,d.set_directory=/path/to/data/JKL/"
schedule = watch_directory_5,30,90,"load.start=/path/to/data/mno/*.torrent,d.set_directory=/path/to/data/MNO/"
schedule = watch_directory_6,30,90,"load.start=/path/to/data/pqr/*.torrent,d.set_directory=/path/to/data/PQR/"

# Restart torrents that have been copied back…
schedule = tied_directory,5,15,start_tied=

#… and stop those that have been deleted
schedule = untied_directory,5,15,close_untied=

# Close torrents when diskspace is low.
schedule = low_diskspace,5,60,close_low_diskspace=50G

# Stop torrents when reaching upload ratio in percent,
# when also reaching total upload in bytes, or when
# reaching final upload ratio in percent.
# example: stop at ratio 2.0 with at least 200 MB uploaded, or else ratio 20.0
#schedule = ratio,60,60,stop_on_ratio=200,200M,2000

# The ip address reported to the tracker.
# ip = 91.121.112.71
#ip = rakshasa.no

# The ip address the listening socket and outgoing connections is
# bound to.
#bind = 127.0.0.1
#bind = rakshasa.no

# Port range to use for listening.
port_range = 40000-59999

# Start opening ports at a random position within the port range.
port_random = yes

# Check hash for finished torrents. Might be usefull until the bug is
# fixed that causes lack of diskspace not to be properly reported.
check_hash = yes

# Set whetever the client should try to connect to UDP trackers.
use_udp_trackers = yes

# Alternative calls to bind and ip that should handle dynamic ip's.
#schedule = ip_tick,0,1800,ip=rakshasa
#schedule = bind_tick,0,1800,bind=rakshasa

# Encryption options, set to none (default) or any combination of the following:
# allow_incoming, try_outgoing, require, require_RC4, enable_retry, prefer_plaintext
#
# The example value allows incoming encrypted connections, starts unencrypted
# outgoing connections but retries with encryption if they fail, preferring
# plaintext to RC4 encryption after the encrypted handshake
#
encryption = allow_incoming,try_outgoing,enable_retry 
#,prefer_plaintext
# Encryption options, set to none (default) or any combination of the following:
# allow_incoming, try_outgoing, require, require_RC4, enable_retry, prefer_plaintext
#
# The example value allows incoming encrypted connections, starts unencrypted
# outgoing connections but retries with encryption if they fail, preferring
# plaintext to RC4 encryption after the encrypted handshake

# Sort the main view by ratio
view.sort_current = main,greater=d.get_ratio=
view.sort_new = main,less=d.get_ratio=
view.sort = main

# Sort the seeding view by the upload rate and only show torrents with peers
view.sort_current = seeding,greater=d.get_up_rate=
view.filter = seeding,"and=d.get_complete=,d.get_peers_connected="
view.sort_new = seeding,less=d.get_up_rate=
view.sort = seeding

# Sort the leeching view by name
view.sort_current = leeching,greater=d.get_name=
view.sort_new = leeching,greater=d.get_name=
view.sort = leeching

# Filter the active view by connected peers
view.sort_current = active,less=d.get_name=
view.sort_new = leeching,less=d.get_name=
view.filter = active,d.get_peers_connected=
view.sort = active

#
# Do not modify the following parameters unless you know what you're doing.
#

# Hash read-ahead controls how many MB to request the kernel to read
# ahead. If the value is too low the disk may not be fully utilized,
# while if too high the kernel might not be able to keep the read
# pages in memory thus end up trashing.
#hash_read_ahead = 10

# Interval between attempts to check the hash, in milliseconds.
#hash_interval = 100

# Number of attempts to check the hash while using the mincore status,
# before forcing. Overworked systems might need lower values to get a
# decent hash checking rate.
#hash_max_tries = 10

# Max number of files to keep open simultaniously.
#max_open_files = 64

# Number of sockets to simultaneously keep open.
#max_open_sockets = <no default>

# Example of scheduling commands: Switch between two ip's every 5
# seconds.
#schedule = "ip_tick1,5,10,ip=torretta"
#schedule = "ip_tick2,10,10,ip=lampedusa"

# Remove a scheduled event.
#schedule_remove = "ip_tick1"

via
via
via
via
via

akopalypse.net

rTorrent and configuration

Documentation on rtorrent is scarce and spread all over the interwebs. Some options are self-explanatory, some are tricky, and for some features there is not a hint on the man page.

This config lets you
· deal with seperate trackers
· keep the .torrent files in respective directories
· watch these directories for new torrents
· prefer encrypted connections

Probably there is no point in encrypted traffic, as it uses RC4 as encryption algorithm, which is broken for years.

The numbers in like

schedule = tied_directory,5,15,start_tied=

mean task done for the first time 5 seconds after starting, then every 15 seconds.

Basics

Control start / stopped state

^s – Start download item. Runs hash first unless already done.
^d – Stop an active download item, or remove a stopped one.
^k – Stop item and close all files, also set 'ignore commands' flag.

Global throttling

a|s|d – Increase the upload throttle by 1/5/50 KiB.
z|x|c – Decrease the upload throttle by 1/5/50 KiB.
A|S|D – Increase the download throttle by 1/5/50 KiB.
Z|X|C – Decrease the download throttle by 1/5/50 KiB.

Other general keys

‹up›|‹down› – Select an item.
‹left› – Go back to the previous screen.
^o – Set new download directory on a closed item.
^x – Open a prompt for rTorrent commands.
^q – Exit rTorrent (press twice to skip 'stop' tracker announces).

Errors & Warnings

A tracker returns a HTTP 5xx status page, or a similar HTML response

Tracker: [Could not parse bencoded data]

When trying to load corrupt metafiles

Could not create download, the input is not a valid torrent

Data of an item is changed or removed, after it is marked as complete;
recover by pressing Ctrl+k Ctrl+e Ctrl+r, then possibly Ctrl+s to re-download.

Download registered as completed, but hash check returned unfinished chunks.

Flow control

If you access rtorrent on another machine by screen, there are some caveats with flow control. The remote terminal and rtorrent may use same commands.

For rtorrent, Ctrl+s starts a torrent, and Ctrl+q quits the application.
For the remote terminal, Ctrl+s is often used for terminal control to stop screen output while Ctrl+q is used to start it, so Ctrl+s instead of starting a torrent pauses flow, therefore the session looks frozen.
You can check with

$ stty -a

To remove the mappings, change the terminal characteristics to undefine the aforementioned special characters (i.e. stop and start):

# stty stop undef
# stty start undef

Toggle off:

Ctrl+a Ctrl+f

should fix that for the moment.
To remove these mappings automatically at startup you may add the two preceding commands to your e.g. ~/.bashrc file.

via

Scrolling through a huge amount of torrents is tedious, and one can only scroll from one to the other without the ability to skip pages or skip to the next first letter like jump to the next torrent beginning with an H. But torrents can be filtered:

AltGr+End

opens the filter> prompt, and bar stre lists all torrents containing Barbra Streisand in its name. Search is case-insensitive. You can filter for regular expressions also, but using RE may put some heavy load on the machine.
A new empty filtering ends the filtering.

Disable SSL verification

Usually you want a secured connection to the tracker to avoid MITM attacks or your provider or other third party snooping your traffic. But some trackers mess up their SSL renewal process from time to time. If you consider your ratio more valueable than encrypted traffic, you might add

network.http.ssl_verify_peer.set=0

to your config. Remember to comment it out if not needed anymore and consider to reset your passkey. Furthermore, certificate checking can be enabled or disabled for all trackers, not seperately for each tracker.

A configuration template

# This is an example resource file for rTorrent. Copy to
# ~/.rtorrent.rc and enable/modify the options as needed.
# Uncomment the options you wish to enable.
#
# .rtorrent.rc for /path/to/data
pieces.sync.always_safe = yes
# Maximum and minimum number of peers to connect to per torrent.
# Many simultaneous up/ downloads and my old access point freaks out.
min_peers = 1
max_peers = 40

# Same as above but for seeding completed torrents (-1 = same as downloading)
min_peers_seed = 1
max_peers_seed = 40

# Maximum number of simultanious uploads per torrent.
max_uploads = 20
# Global upload and download rate in KiB. "0" for unlimited.
download_rate = 0
upload_rate = 0

# disable SSL verification. Do not uncomment unless you know what you're doing.
#network.http.ssl_verify_peer.set=0

# Default session directory. Make sure you don't run multiple instance
# of rtorrent using the same session directory. Perhaps using a
# relative path?
session = ~/rtorrentsession/

# Periodically save session data
schedule = session_save,500,120,session_save=

# Watch a directory for new torrents, save to corresponding folders and
# stop those that have been deleted.
schedule = watch_directory_1,30,90,"load.start=/path/to/data/abc/*.torrent,d.set_directory=/path/to/data/ABC/"
schedule = watch_directory_2,30,90,"load.start=/path/to/data/def/*.torrent,d.set_directory=/path/to/data/DEF/"
schedule = watch_directory_3,30,90,"load.start=/path/to/data/ghi/*.torrent,d.set_directory=/path/to/data/GHI/"
schedule = watch_directory_4,30,90,"load.start=/path/to/data/jkl/*.torrent,d.set_directory=/path/to/data/JKL/"
schedule = watch_directory_5,30,90,"load.start=/path/to/data/mno/*.torrent,d.set_directory=/path/to/data/MNO/"
schedule = watch_directory_6,30,90,"load.start=/path/to/data/pqr/*.torrent,d.set_directory=/path/to/data/PQR/"

# Restart torrents that have been copied back…
schedule = tied_directory,5,15,start_tied=

#… and stop those that have been deleted
schedule = untied_directory,5,15,close_untied=

# Close torrents when diskspace is low.
schedule = low_diskspace,5,60,close_low_diskspace=50G

# Stop torrents when reaching upload ratio in percent,
# when also reaching total upload in bytes, or when
# reaching final upload ratio in percent.
# example: stop at ratio 2.0 with at least 200 MB uploaded, or else ratio 20.0
#schedule = ratio,60,60,stop_on_ratio=200,200M,2000

# The ip address reported to the tracker.
# ip = 91.121.112.71
#ip = rakshasa.no

# The ip address the listening socket and outgoing connections is
# bound to.
#bind = 127.0.0.1
#bind = rakshasa.no

# Port range to use for listening.
port_range = 40000-59999

# Start opening ports at a random position within the port range.
port_random = yes

# Check hash for finished torrents. Might be usefull until the bug is
# fixed that causes lack of diskspace not to be properly reported.
check_hash = yes

# Set whetever the client should try to connect to UDP trackers.
use_udp_trackers = yes

# Alternative calls to bind and ip that should handle dynamic ip's.
#schedule = ip_tick,0,1800,ip=rakshasa
#schedule = bind_tick,0,1800,bind=rakshasa

# Encryption options, set to none (default) or any combination of the following:
# allow_incoming, try_outgoing, require, require_RC4, enable_retry, prefer_plaintext
#
# The example value allows incoming encrypted connections, starts unencrypted
# outgoing connections but retries with encryption if they fail, preferring
# plaintext to RC4 encryption after the encrypted handshake
#
encryption = allow_incoming,try_outgoing,enable_retry 
#,prefer_plaintext
# Encryption options, set to none (default) or any combination of the following:
# allow_incoming, try_outgoing, require, require_RC4, enable_retry, prefer_plaintext
#
# The example value allows incoming encrypted connections, starts unencrypted
# outgoing connections but retries with encryption if they fail, preferring
# plaintext to RC4 encryption after the encrypted handshake

# Sort the main view by ratio
view.sort_current = main,greater=d.get_ratio=
view.sort_new = main,less=d.get_ratio=
view.sort = main

# Sort the seeding view by the upload rate and only show torrents with peers
view.sort_current = seeding,greater=d.get_up_rate=
view.filter = seeding,"and=d.get_complete=,d.get_peers_connected="
view.sort_new = seeding,less=d.get_up_rate=
view.sort = seeding

# Sort the leeching view by name
view.sort_current = leeching,greater=d.get_name=
view.sort_new = leeching,greater=d.get_name=
view.sort = leeching

# Filter the active view by connected peers
view.sort_current = active,less=d.get_name=
view.sort_new = leeching,less=d.get_name=
view.filter = active,d.get_peers_connected=
view.sort = active

#
# Do not modify the following parameters unless you know what you're doing.
#

# Hash read-ahead controls how many MB to request the kernel to read
# ahead. If the value is too low the disk may not be fully utilized,
# while if too high the kernel might not be able to keep the read
# pages in memory thus end up trashing.
#hash_read_ahead = 10

# Interval between attempts to check the hash, in milliseconds.
#hash_interval = 100

# Number of attempts to check the hash while using the mincore status,
# before forcing. Overworked systems might need lower values to get a
# decent hash checking rate.
#hash_max_tries = 10

# Max number of files to keep open simultaniously.
#max_open_files = 64

# Number of sockets to simultaneously keep open.
#max_open_sockets = <no default>

# Example of scheduling commands: Switch between two ip's every 5
# seconds.
#schedule = "ip_tick1,5,10,ip=torretta"
#schedule = "ip_tick2,10,10,ip=lampedusa"

# Remove a scheduled event.
#schedule_remove = "ip_tick1"

via
via
via
via
via