Meta tags:

Headings (most frequently used words):

-

Text of the page (most frequently used words):
the (145), irc (49), that (37), and (36), ircd (35), synchronet (29), this (27), for (25), with (21), you (21), server (21), network (18), net (17), use (17), can (16), bbs (15), synchro (13), from (13), command (13), your (12), qwk (12), will (11), but (11), have (11), would (11), are (10), like (10), still (10), able (10), when (10), vert (9), should (9), not (8), flags (8), password (8), there (8), way (7), only (7), any (7), they (7), two (7), decades (7), could (7), software (7), services (7), configuration (6), chat (6), sysops (6), jsexec (6), was (6), these (6), its (6), mrc (6), future (5), many (5), users (5), their (5), servers (5), first (5), want (5), then (5), about (5), ini (5), has (5), most (5), all (5), old (5), send (5), people (5), user (5), noise (5), back (4), cyan (4), author (4), service (4), might (4), take (4), used (4), file (4), ircdcfg (4), need (4), make (4), since (4), operator (4), master (4), passwords (4), dove (4), same (4), happens (4), port (4), hub (4), srvc (4), 0008 (4), messages (4), started (4), writing (4), been (4), over (4), written (4), digitalman (4), rbl (4), lookups (4), ssl (4), netsplit (4), split (4), introduction (3), known (3), issues (3), ideas (3), protocol (3), own (3), familiar (3), know (3), point (3), look (3), org (3), line (3), both (3), configure (3), out (3), conf (3), run (3), whenever (3), does (3), single (3), using (3), locally (3), globally (3), through (3), txt (3), hostname (3), address (3), features (3), become (3), routing (3), connected (3), join (3), across (3), some (3), between (3), one (3), thing (3), than (3), more (3), much (3), now (3), something (3), authors (3), nickserv (3), related (3), above (3), method (3), lot (3), support (3), example (3), account (3), easy (3), host (3), cloaking (3), ircv3 (3), channel (3), sent (3), linking (2), word (2), compatible (2), rfc1459 (2), internet (2), connect (2), client (2), around (2), www (2), original (2), irc2 (2), versions (2), style (2), files (2), based (2), help (2), won (2), anything (2), various (2), looks (2), save (2), either (2), case (2), standalone (2), keep (2), running (2), following (2), character (2), what (2), after (2), very (2), rehash (2), restart (2), squit (2), kill (2), global (2), notices (2), aggregate (2), behaviour (2), upstream (2), authentication (2), received (2), established (2), required (2), member (2), process (2), http (2), mybbs (2), try (2), resolve (2), anyone (2), offers (2), section (2), add (2), new (2), tcp (2), 6667 (2), class (2), true (2), may (2), left (2), cvs (2), other (2), see (2), message (2), link (2), those (2), create (2), meaningful (2), idea (2), experience (2), don (2), basis (2), even (2), dalnet (2), because (2), despite (2), development (2), really (2), ways (2), set (2), time (2), different (2), were (2), deuce (2), particular (2), exists (2), design (2), integration (2), few (2), unmaintained (2), consider (2), migrating (2), maintained (2), open (2), source (2), whole (2), current (2), church (2), instead (2), opportunity (2), currently (2), say (2), lookup (2), until (2), dns (2), allows (2), spoke (2), model (2), where (2), days (2), cryptographically (2), secure (2), code (2), 005 (2), numeric (2), identify (2), possible (2), compatibility (2), seems (2), hash (2), making (2), comes (2), quit (2), part (2), pgdn, pgup, home, end, raw, randy, sommerfeld, 100, standard, defines, helpful, learn, basics, document, assume, terminology, favourite, also, https, irchelp, nostalgic, trip, past, feature, wise, par, late, dreamforge, full, anachronisms, era, prior, later, equally, supported, preferred, easiest, tui, uifc, online, hints, assumes, fair, bit, technical, knowledge, pre, configured, box, conversion, format, load, into, path, menus, sure, data, config, imported, correctly, well, main, menu, inspect, resulting, which, start, stop, prefer, affected, restarts, choice, yours, determine, permissions, operators, inherit, oper, get, granular, die, globops, wallops, locops, chatops, eval, kline, unkline, administrator, system, rgwlckbbn, rgwlckbbnckns, alter, mostly, controlling, check, against, database, ensure, node, although, aren, least, automatic, registration, obtain, instructions, obtaining, found, here, docs, setup, dyndns, module, appropriate, information, towards, correct, who, reach, wishes, specifically, faster, closer, interesting, launch, navigate, details, outbound, actual, inbound, servername, note, differ, changed, defaults, intentionally, blank, another, strictly, necessary, location, offer, little, redundancy, each, how, simply, similar, console, auto, connecting, sending, info, 0018, accepted, connection, 196, ago, intention, integrated, hosting, obvious, flip, provide, seamless, wouldn, backend, hasn, materialized, considering, expect, being, said, surprised, daily, ten, years, remarkable, milestones, 2021, ircstats, reported, accounted, ipv4, 2022, rose, larger, share, charybdis, libera, spiritual, ancestor, bahamut, course, happened, riding, coat, tails, statement, install, base, noteworthy, unfortunate, reality, doesn, centric, stand, peers, difference, sysop, achieved, goals, originally, accomplish, definitely, give, step, aside, forties, priorities, thank, without, never, helped, carry, figured, influx, interested, discussing, decisions, operations, etc, passions, mine, twenty, self, excited, contributing, older, niche, hobby, passion, january, 2024, hope, someone, torch, finally, wanted, express, appreciation, linus, torvalds, immense, amount, pressure, made, tougher, stuff, version, runs, chanserv, ircservices, andy, 2009, website, achurch, disclaimer, state, reads, assistance, patches, provided, accept, liability, damage, caused, security, bugs, move, relying, integrate, things, memoserv, blocking, operation, unable, else, completes, check_dnsbl, function, handles, migrated, resolve_ip, asynchronous, block, follows, major, hubs, creates, failure, rendered, useless, sometimes, house, stable, platform, such, multi, homed, datacenter, control, forward, uplinks, passing, under, pass, disabled, altered, perhaps, hashing, added, authenticated, offline, incomplete, evolved, longer, complete, targmax, needs, fixed, hard, coded, present, ports, 994, 6697, groundwork, laid, allow, specify, flipped, off, per, unique, creating, specific, every, special, non, colliding, nicks, msg, conflicts, override, just, joined, serving, via, fileserv, dcc, rely, whoever, collaborating, happen, win, require, collaboration, stakeholders, achieve, goal, obscuring, real, cryptographic, whois, output, e21e, 3e5a, 1440, d392, 7fe2, 7001, 80b, 2602, constructed, reveals, portion, useful, hostmasks, bans, fairly, rare, almost, expectation, already, parses, tags, irc_parse, irc_parse_tags, functions, irclib, form, work, reducing, kind, acceptable, raspberry, unplugged, wall, cause, visible, dozens, machines, starts, annoying, frequent, complaint, solution, implement, mode, squelch, accomplished, hold, channels, notice, informing, sender, timeout, minutes, reasonable, before, facing, queued, resync, display, unless, talked, sends, privmsg, place, eof, 339,

Text of the page (random words):
ircd txt ircd txt 12 13 23 19 13 line 1 339 ircd js the synchronet ircd by randy sommerfeld cyan synchro net 1 introduction 2 configuration 3 linking to the synchronet irc network irc synchro net 4 a word from the author 5 known issues ideas for the future 1 introduction the synchronet ircd is a synchronet service that is 100 compatible with rfc1459 the internet standard that defines the irc protocol many bbs users use it to chat on the synchronet irc network and many sysops connect their own irc servers to the network if you re not familiar with irc it will be helpful to learn the basics first this document will assume that you know irc terminology if you re not familiar with the synchronet irc network you might want to point your favourite irc client at irc synchro net and take a look around you might also want to take a look at https www irchelp org if you are familiar with irc then the synchronet ircd might be a nostalgic trip to the past for you feature wise it s about on par with a late 90 s irc server like the original irc2 server or dreamforge and it s full of anachronisms from that era 2 configuration 2 1 introduction versions of the ircd prior to 2 0 used an irc2 style line configuration file versions 2 0 and later use synchronet style ini files both are still equally supported but the ini file is preferred the easiest way to configure the synchronet ircd is to use ircdcfg js with jsexec this is a configuration tui based on synchronet s uifc it has online help hints but still assumes a fair bit of irc technical knowledge most sysops won t need to configure anything at all the ircd is pre configured out of the box 2 2 conversion from old conf format load the old conf based configuration into ircdcfg js like this jsexec ircdcfg js f path to old conf look around the various menus to make sure the data from the old config was imported correctly if all looks well save as from the main menu and inspect the resulting ini file 2 3 service or jsexec the ircd can run either as a synchronet service in which case it will start and stop whenever synchronet does or standalone with jsexec many sysops prefer to keep their ircd running with jsexec since then it is not affected by bbs restarts the choice is yours 2 4 operator flags the following single character flags determine what permissions irc operators inherit after using the oper command these get very granular but most sysops will want to use only o r can use the rehash command r can use the restart command d can use the die command g can use the globops command w can use the wallops command l can use the locops command s can use the chatops command x can use the eval command c able to squit locally c able to squit globally k able to kill locally k able to kill globally b can use the kline command b can use the unkline command n only able send global notices locally n able to send global notices globally a operator is server administrator s operator password is the synchronet system password o an aggregate of rgwlckbbn flags o an aggregate of rgwlckbbnckns flags 2 5 server flags these single character flags alter server behaviour most sysops won t have any use for these they re mostly for controlling the qwk master behaviour q check password against qwk database w send qwk passwords to this server for upstream authentication k passwords received from this server go to the qwk master 3 linking to the synchronet irc network irc synchro net 1 ensure that you have a dove net node established although you aren t required to be a member of dove net to be a member of the synchronet irc network you need to at least go through the same automatic registration process to obtain and configure your qwk id instructions about obtaining your qwk id can be found here http www synchro net docs dove net txt 2 setup the dyndns js module with your appropriate qwk id information so that the hostname mybbs synchro net will point towards your correct ip address this is required so that users who try to reach your irc server will be able to resolve the hostname used on the irc network that way if anyone wishes to connect to your server bbs specifically they ll be able to use mybbs synchro net i e if your server happens to be faster closer or offers interesting bbs features 3 launch ircdcfg js with jsexec and navigate to the servers section there add a new server and save the ircd ini with these details tcp ip address vert synchro net tcp ip port 6667 outbound password your actual dove net qwk password inbound password servername vert synchro net irc class 10 flags hub true note that irc class may differ if you ve changed the defaults the flags are intentionally left blank you might want to add another server for cvs synchro net but it s not strictly necessary since both of these servers are in the same location and offer little redundancy from each other 4 restart your bbs or if you know how to become an irc operator simply use the rehash command and you should see a message similar to the following in your synchronet console srvc 0008 irc routing auto connecting to vert synchro net srvc 0008 irc routing connected sending info srvc 0008 irc 0018 accepted new connection 71 95 196 34 port 6667 srvc 0008 irc routing link with vert synchro net established 5 if you have received those messages then you re connected you should be able to join synchronet and chat with people across the network 4 a word from the author when i first started writing this two decades ago the intention was to create an irc server that would be integrated with the hosting synchronet bbs in some meaningful way the most obvious way would be to have the bbs chat the same as irc so a user could flip between the two and still chat with the same people on either one the idea would be to provide a seamless experience to the user so that they wouldn t know they re using irc on the backend this hasn t materialized and considering it s been over two decades i don t expect it to with that being said i m still surprised two decades on that people are still using this thing on a daily basis when i first started writing the ircd rfc1459 was only ten years old there have been some remarkable milestones in 2021 ircstats org reported that synchronet ircd accounted for 2 2 of all irc servers on the ipv4 internet in 2022 that rose to 2 7 a larger share than charybdis used by libera or even the ircd s spiritual ancestor bahamut used by dalnet of course this only happened because the ircd is riding synchronet s coat tails it s more a statement about synchronet s install base but it s still noteworthy the unfortunate reality of the ircd is that despite two decades of development it really doesn t have any bbs centric features that make it stand out from its peers what s the difference between a sysop running the synchronet ircd and a standalone ircd written in c not much really in many ways mrc has achieved many of the goals that the ircd originally set out to accomplish if you want a more bbs like experience in your chat you should definitely give mrc a try as for me after two decades of development it s time to step aside i m now in my forties and my priorities now are much different than they were when i started this thing i d like to thank digitalman and deuce in particular without their help the ircd would never have been written and it only exists because they helped carry me across the line when i first started writing the ircd i figured there d be an influx of people interested in discussing the irc protocol design decisions bbs integration operations etc those are all passions of mine and my twenty something self was excited about contributing now that i m two decades older i can see that this is a niche hobby that very few have a passion for as of january 2024 the ircd will become unmaintained software i hope that someone can take up the torch sysops should consider migrating their chat to mrc a maintained irc network or a maintained ircd finally i wanted to express my appreciation for authors of open source software as a whole people like digitalman deuce linus torvalds and other open source authors are able to keep writing despite an immense amount of pressure and noise they re made of much tougher stuff than i am cyan 5 known issues ideas for the future 5 1 known issues 5 1 1 irc services the current version of irc services that is the software that runs chanserv nickserv et al on the synchronet irc network is ircservices 5 1 24 written by andy church in 2009 on church s website http achurch org services there is a disclaimer about the current state of the software that reads no assistance or patches will be provided for this software and the author does not accept any liability for any damage caused by this software even in the case of security bugs synchronet should move to its own irc services instead of relying on unmaintained software this is an opportunity to integrate things like nickserv or memoserv with the bbs 5 1 2 rbl lookups currently rbl lookups are a blocking operation that is to say when an rbl lookup happens the ircd is unable to process anything else until the lookup completes the check_dnsbl function that handles rbl lookups in the ircd should be migrated to dns js instead of resolve_ip since dns js allows for asynchronous lookups that do not block 5 1 3 irc network hub and spoke model the synchronet irc network follows a hub and spoke model where vert and cvs are major hubs this creates a single point of failure and the whole network is rendered useless sometimes for days at a time whenever something happens at digitalman s house the network should consider migrating its irc hub to a stable platform such as a server in a multi homed datacenter this server could still be left in control of digitalman and forward its qwk passwords up to vert in a cryptographically secure way 5 1 4 qwk uplinks related to the above there exists code in the ircd for passing passwords upstream to a qwk master for authentication most of the code is under the pass command in server js but is currently disabled this should be altered to send the password in a cryptographically secure way and perhaps have a hashing method added so that servers can still be authenticated when the qwk master is offline 5 1 5 005 numeric is incomplete the 005 numeric has evolved a lot over the decades and it s no longer complete on the synchronet ircd in particular targmax needs to be fixed 5 1 6 ssl support the ircd does support ssl but it is hard coded to be present on ports 994 and 6697 only the groundwork has been laid in the ini configuration to allow a port section to specify ssl true so that ssl support can be flipped on or off per port 5 2 ideas for the future 5 2 1 irc services related to 5 1 1 above there s an opportunity to make the irc network unique by creating irc services that have bbs specific features one idea is that every server should run its own set of services with special non colliding nicks for example if you have an account on vert you could then identify to it with something like this msg nickserv vert synchro net identify password there would need to be a method to resolve conflicts i e an account on vert will override an account from a bbs that just joined the network 5 2 2 file serving via irc related to the above it could be possible to create a fileserv service that offers bbs files over irc and dcc 5 2 3 mrc compatibility this is an easy one but it will rely more on the future ircd author whoever that may be collaborating with the mrc authors to make it happen but it seems like an easy win for both irc and mrc 5 2 4 meaningful bbs integration this would require a lot of collaboration between the various stakeholders but it s still possible to achieve the ircd s original design goal 5 2 5 host cloaking host cloaking is a method of obscuring a user s real hostname or ip address through a cryptographic hash for example my whois output on dalnet looks like this cyan cyan e21e 3e5a 1440 d392 7fe2 7001 80b 2602 ip the hash is constructed in a way where it reveals some portion of the ip but not all of it so it s still useful for making hostmasks like for bans when the synchronet ircd was written host cloaking on irc was a fairly rare thing these days it s almost an expectation 5 2 6 ircv3 compatibility the ircd already parses ircv3 tags from the irc protocol through the irc_parse and irc_parse_tags functions in irclib js this would form the basis of any future work on making the ircd compatible with ircv3 5 2 7 reducing netsplit noise since the synchronet irc network allows anyone to link any kind of irc server to it there is a lot of noise on the network for example it s easy and acceptable to run synchronet and its ircd on a raspberry pi so whenever the pi is unplugged from the wall it could cause a visible netsplit when this happens across dozens of connected machines the noise starts to become annoying and it s a frequent complaint from users a solution to this would be to implement a channel mode that would squelch netsplit noise this could be accomplished in a few different ways 1 hold the netsplit users in their channels until the server comes back if a message is sent to the split users the server could send a notice back informing the sender of the split this would need a timeout 15 minutes seems reasonable before the client facing quit messages were sent for the split when the split server comes back any messages queued up would be sent over as part of the resync 2 don t display join part quit messages in a channel unless a user has talked first that is to say when a user sends privmsg to a channel only then will the join take place eof pgdn pgup home end q back raw 0