MICRODC(1)

💅 MICRODC — okay bestie, let's talk Direct Connect

so like, microdc is a command-line based Direct Connect client and honestly? she's that girl. this is the manual page for her, and I'm gonna walk you through every single flag because you deserve the full picture, no gatekeeping here 💖

---

✨ SYNOPSIS ✨

microdc [OPTION]...

that's it. that's the whole vibe. options in, magic out 🦋

---

🌸 DESCRIPTION 🌸

okay so microdc is a command-line based Direct Connect client that uses the GNU Readline library for user interaction. she was developed from the ground up — like, completely from scratch — and does not depend on any other program. no cap. zero external program dependencies. she's self-made 👑

and the way that she's command-line based but still designed to be user friendly and simple to use? it's giving accessible queen. don't let the terminal scare you, bestie, she's nice 💜

---

🎀 OPTIONS 🎀

this program follows the usual GNU command line syntax, with long options starting with two dashes (--). so you know the drill, short option or long option, pick your fighter ✨

• -c, --config=FILE — read the configuration script from FILE instead of the usual ~/.microdc/config. you want a different config? say less, she'll take it from there 🫶
• -n, --no-config — do not read the config file on startup. just raw-dogging the defaults, periodt 💅
• --help — show a summary of options. when you're lost, she's got you 😌
• --version — output version information and exit. quick little hello and then she's gone 👋
• --filelist_refresh_interval=NUMBER — local filelist refresh interval, measured in seconds. okay so this one has lore:

if you set it to zero, the program runs in a special slave mode: it never updates the file list, it just checks every minute if the filelist changes, and if so — it reads it. this is pretty useful if you connect to several hubs and use the same filelist. multi-hub besties, this one's for you 🌈

---

🦋 FILES 🦋

the following files are used by microdc (~ represents the current user's home directory, obviously 💁):

• ~/.microdc/config — this file is loaded on startup. it contains commands, one per line, that will be executed on startup. you can override loading of this file with --config and --no-config. your little startup ritual, if you will 🕯️
• ~/.microdc/history — this is the command history file. it contains a list of commands that were typed and executed from the microdc prompt. it can safely be removed. no emotional attachment required, she won't be mad 🍓

---

😭 REPORTING BUGS 😭

found a bug? report bugs to <oskar@osk.mine.nu>. please be nice to him, he made all this 💖

---

👑 AUTHOR 👑

the author of microdc and this manual page is Oskar Liljeblad <oskar@osk.mine.nu>. legend behavior, honestly.

---

⭐ COPYRIGHT ⭐

Copyright © 2004, 2005 Oskar Liljeblad

this is free software; see the source for copying conditions. there is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

like, fr fr, no warranty. not even the implied ones. she said what she said 💀

---

so yeah, that's the whole page. microdc, version from September 17, 2005, general commands manual, section 1 — and this rewrite was brought to you with love, glitter, and absolutely zero missing details 🌸✨

now go connect to some hubs, bestie. slay 💅🦋💜