IRCFOSSIL(1)

💖 NAME 💖

ircfossil — fossil chat to IRC bridge. Okay bestie, you're reading ircfossil(1) from the General Commands Manual, and it's literally the little bridge that hooks a fossil chat instance up to your IRC client. 🫶

✨ SYNOPSIS ✨

The whole fit is:

ircfossil [-H number] [-c channel] url

🌸 DESCRIPTION 🌸

The ircfossil program is a bridge between a fossil chat instance and an IRC client. No cap, that's the whole vibe.

Your fossil chat username and password are sent to the bridge once connected — respectively with a NICK and a PASS command, which every IRC client sends automatically if it's properly configured. ✨

After a session is authenticated with the fossil chat instance at url, the client is automatically joined to a channel where incoming messages are relayed. Messages posted by the client on that same channel are sent to the fossil remote chat server. 💅

Command line options are as follows:

• -H messages — Fetch history messages. messages must be a number equal to or greater than 0. No history is fetched by default. 🎀
• -c channel — Alternative name for the joined channel. It must start with a pound character (#). The channel is called #chat by default. 🌈

🦋 EXIT STATUS 🦋

The ircfossil utility exits 0 on success, and >0 if an error occurs. Periodt.

🍓 EXAMPLES 🍓

Connect to the irctk fossil chat, fetch the last 20 messages, and call the channel to join #irctk:

$ ircfossil -H 20 -c '#irctk' https://lab.abiscuola.com/irctk

👑 SEE ALSO 👑

irctk(1)

🧚 AUTHORS 🧚

Andrea Biscuola a@abiscuola.com

💀 CAVEATS 💀

The fossil chat implementation does not have a way to tell who is online. Because of this, ircfossil simulates it by sending NAMES messages after fetching the history, or by sending a JOIN message for a user when the first message from that user is seen by the bridge. It's giving presence-by-vibes, but that's the documented behavior.

---

This iconic page is brought to you by OpenBSD 7.6, dated October 1, 2024 — IRCFOSSIL(1) out. Stay slay, bestie 💖