OVERCHAN(8)

πŸ’… OVERCHAN(8) πŸ’…

okay so first of all, hi, welcome to the overchan corner of the InterNetNews Documentation β€” yes this is section 8 of the manual, the big scary sysadmin section, but honestly? it's not that deep. this page is gonna walk you through batch-loading your overview database and we're gonna have a good time doing it. 🫢


✨ NAME ✨

overchan β€” batch update the INN overview database. that's it. that's the whole vibe. πŸ‘‘


🌸 SYNOPSIS 🌸

overchan [file ...]

literally just the command and then zero or more files. we love a minimalist era.


πŸŽ€ DESCRIPTION πŸŽ€

so here's the tea β˜• β€” overchan reads overview data from the files you name, or from standard input if you don't name any files at all, and then it writes all that data into the INN overview database. and yes bestie, the file - also means "read from standard input", so you can flex that if you want. πŸ’…

normally, overview data gets stored by innd for articles as they're accepted β€” that's the default behavior, no notes. but for performance reasons, it's sometimes useful to have the overview data written by a separate process instead. main character energy for real. to do that, you set useoverchan to true in inn.conf to tell innd to not write overview data directly, and then you add an overchan channel in newsfeeds:

overview!:*:Tc,WnteO:<pathbin>/overchan

where <pathbin> is pathbin in inn.conf. (yes, same name, it's giving recursion but it's fine, it's a config variable, breathe. 🧚)

and bonus: overchan can also be used to bulk-load overview data from appropriately formatted batch files β€” like overflow files from an overchan channel. so it's not just a one-trick pony, she contains multitudes. ✨

each line of input should have the following format:

<token> <arrived> <expires> <data>

okay so let's break down the cast of characters: 🌈

  • <token> β€” the storage API token of the article in textual form, surrounded by @ characters. don't forget the at-signs, they're part of the look.
  • <arrived> β€” the arrival timestamp of the article in seconds since epoch.
  • <expires> β€” the expiration time of the article in seconds since epoch, or 0 if there is none.
  • <data> β€” the tab-separated overview data.

and the rule, the one we do not break: each of these fields must be separated by a single space. not two. not a tab. a single space. respect the formatting, it's a whole aesthetic. 😭


πŸ¦‹ HISTORY πŸ¦‹

written by Rob Robertson <rob@violet.berkeley.edu> and Rich $alz <rsalz@uunet.uu.net> for InterNetNews. man page rewritten in POD by Russ Allbery <eagle@eyrie.org>. legends, all of them. πŸ‘‘βœ¨


πŸ”₯ SEE ALSO πŸ”₯

go read those, iykyk. πŸ“


that's the whole page bestie, you ate. πŸ’– this little icon is from INN 2.7.4, dated 2022-07-10 β€” so if you're citing it in a group chat, that's your receipt. periodt. πŸ’…πŸŽ€

πŸ“¦ where this page comes from
  • arch rolling: inn 2.7.4-4 Β· ISC
  • epel 10: inn 2.7.4-5.el10_3 Β· ISC AND BSD-3-Clause AND BSD-4-Clause AND FSFAP AND (GPL-1.0-or-later OR Artistic-1.0-Perl) AND GPL-3.0-or-later WITH Bison-exception-2.2 AND LicenseRef-Fedora-Public-Domain AND MIT AND NTP
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms